Skip to content

[Fix] OpenCode Go context meter shows incorrect limits - #1428

Open
zoomote[bot] wants to merge 3 commits into
mainfrom
fix/opencode-go-model-limits-1126p2a98y80f
Open

[Fix] OpenCode Go context meter shows incorrect limits#1428
zoomote[bot] wants to merge 3 commits into
mainfrom
fix/opencode-go-model-limits-1126p2a98y80f

Conversation

@zoomote

@zoomote zoomote Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

All 33 models currently returned by OpenCode Go now have complete metadata in the single opencodeGoModels registry, including limits, capabilities, pricing, and descriptions. Live endpoint metadata still overrides volatile fields when supplied, and Qwen format routing now includes the additional Messages API models.

Why this change was made

Models without a registry entry inherited a generic 200k context window, causing incorrect context percentages. Keeping a second limits-only table also split curated models across two sources of truth.

Impact

The context meter, model controls, and cost estimates now resolve from one model registry. Exact registry-membership tests cover every current OpenCode Go ID, while unknown future IDs retain the safe generic fallback.

Related PRs

@codecov

codecov Bot commented Aug 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@zoomote

zoomote Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

Consolidated all 33 OpenCode Go model records into opencodeGoModels and removed the separate limits registry/helper. The registry now carries limits, capabilities, pricing, and descriptions for every current live ID, with exact membership and metadata invariants covered by tests. Full workspace tests, lint, and type checks pass.

Commit: db24d2f

@github-actions github-actions Bot added the awaiting-review PR changes are ready and waiting for maintainer re-review label Aug 29, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Review process

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

  1. Required CI checks pass.
  2. The workflow starts CodeRabbit automatically.
  3. CodeRabbit reviews and approves the latest commit.
  4. A human maintainer reviews and approves after CodeRabbit.

Current step: Required CI passed. Wait for CodeRabbit to approve the latest commit.

@github-actions github-actions Bot added coderabbit-review-active Required CI passed; CodeRabbit review is active awaiting-coderabbit Waiting for CodeRabbit to approve the latest commit awaiting-review PR changes are ready and waiting for maintainer re-review and removed awaiting-review PR changes are ready and waiting for maintainer re-review labels Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-coderabbit Waiting for CodeRabbit to approve the latest commit awaiting-review PR changes are ready and waiting for maintainer re-review coderabbit-review-active Required CI passed; CodeRabbit review is active

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants