Skip to content

feat(opencode): build variants from configured reasoning options - #55854

Merged
vimtor merged 2 commits into
v1from
v1-config-reasoning-options
Oct 16, 2026
Merged

vimtor merged 2 commits into
v1from
v1-config-reasoning-options

Conversation

@vimtor

@vimtor vimtor commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Why

Org admins can now set which reasoning controls a model accepts in the OpenCode Console (anomalyco/opencode-console#3690). The Console sends them as reasoning_options in the pulled config, but 1.x ignored that key in config, so the edits had no effect for 1.x users.

What changes

  • Config: adds provider.*.models.*.reasoning_options, in the same format models.dev uses.
  • Variants:
    • When reasoning_options is set, OpenCode builds the model's variants from it with ProviderTransform.reasoningVariants, the same path catalog models use. These replace the catalog variants.
    • An empty list means no variants.
    • Configured variants still merge on top.
  • SDK: regenerated the SDK types.

Verification

  • Typecheck passes for opencode and core.
  • Added a provider test for replaced, overlaid, and empty reasoning options. Tests run in CI.

@vimtor

vimtor commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator Author

Closing: we're not targeting 1.x for Console reasoning edits. 1.x keeps building variants from its own models.dev data, and ignores the reasoning_options the Console sends.

@vimtor vimtor closed this Oct 16, 2026
@vimtor

vimtor commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator Author

Reopening: we do want 1.x to build variants from the reasoning options the Console sends.

@vimtor vimtor reopened this Oct 16, 2026
@vimtor
vimtor merged commit d12161e into v1 Oct 16, 2026
10 checks passed
@vimtor
vimtor deleted the v1-config-reasoning-options branch October 16, 2026 11:36
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