Skip to content

fix(agent): add missing BytePlus ModelArk catalog entries - #50

Open
leksautomate wants to merge 1 commit into
0xsline:mainfrom
leksautomate:fix/byteplus-model-capabilities
Open

fix(agent): add missing BytePlus ModelArk catalog entries#50
leksautomate wants to merge 1 commit into
0xsline:mainfrom
leksautomate:fix/byteplus-model-capabilities

Conversation

@leksautomate

@leksautomate leksautomate commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • deepseek-v3-2-251201 and seed-2-0-pro-260328 (BytePlus ModelArk) were missing from the hand-vendored BYTEPLUS_MODELS catalog in scripts/update-llm-model-capabilities.mjs / assets/model-capabilities/models-dev.json (BytePlus has no models.dev provider, so these entries are hand-maintained).
  • Missing entries meant resolveModelCapabilities() fell back to the unknown-model defaults (8,192 context / 2,048 output). That fallback context window is smaller than OpenChatCut's own system prompt + tool schemas, so context-compaction.ts correctly refused to send the request at all ("The current request is too large for this model context window...") on every single turn, regardless of conversation length.
  • Verified the real limits directly against the account's live ModelArk endpoint (GET /api/v3/models, which returns per-model token_limits): deepseek-v3-2-251201 → 131,072 context / 32,768 max output; seed-2-0-pro-260328 → 262,144 context / 131,072 max output. Added both to the catalog JSON and to the generator script so they survive the next models.dev resync.

Test plan

  • npx tsc --noEmit — clean
  • npx oxlint scripts/update-llm-model-capabilities.mjs — clean
  • node -e "JSON.parse(...)" — catalog JSON still valid
  • Ran resolveModelCapabilities({ backend: 'api', provider: 'byteplus', modelId }) for both new model IDs — resolves to the real vendor values with source: 'catalog', estimated: false; a genuinely unknown model id still correctly falls back to the conservative defaults
  • tsx src/agent/ai-sdk.verify.ts, tsx src/agent/context-compaction.verify.ts, tsx src/agent/model-selection.verify.ts, tsx src/agent/local-models.verify.ts, tsx src/agent/vision.verify.ts, tsx server/keystore.verify.ts — all pass

deepseek-v3-2-251201 and seed-2-0-pro-260328 were absent from the
hand-vendored BYTEPLUS_MODELS catalog (BytePlus has no models.dev
provider), so resolveModelCapabilities() fell back to the
unknown-model defaults: an 8,192-token context window and a
2,048-token output cap. That fallback context window is far below
what OpenChatCut's own system prompt and tool schemas need, so
context-compaction.ts's own trigger correctly refused to send the
request at all ("The current request is too large for this model
context window"), on every turn, regardless of conversation size.

Verified the real limits directly against the account's ModelArk
endpoint (GET /api/v3/models, which returns per-model token_limits):
deepseek-v3-2-251201 supports a 131,072-token context window with a
32,768-token output cap, and seed-2-0-pro-260328 supports 262,144
context with a 131,072 output cap. Added both to the catalog and to
the generator script that rebuilds it, matching the existing
hand-vendored ModelArk entries.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant