Skip to content

catalog: preserve model capabilities in generated harness configuration - #255

Draft
samaluk wants to merge 4 commits into
router-for-me:mainfrom
samaluk:review/model-capabilities
Draft

samaluk wants to merge 4 commits into
router-for-me:mainfrom
samaluk:review/model-capabilities

Conversation

@samaluk

@samaluk samaluk commented Sep 13, 2026

Copy link
Copy Markdown

Connecting several harnesses to one gateway should not give the same model different limits or reasoning choices. The current export loses capability metadata, can hide reasoning levels using the GUI’s version as the Codex version, and can choose a generic prompt template for a model exposed through an alias.

Carry the declared limits, modalities and effort choices into each harness’s configuration format. Use explicit canonical identity to select trusted local Codex templates while preserving routing IDs and display labels, apply explicit route modalities and visibility after template selection, and disable unsupported OpenCode default variants without removing custom variants.

Validation: 470 Rust tests pass, covering catalog discovery, generation, configuration merging and review regressions. An isolated check with stock OpenCode confirms only advertised reasoning choices and custom variants remain. Frontend and macOS app bundle builds passed before the final review fixes. Local Pi package recognition and Unix symlink test cleanup are isolated in their own commits.

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