Skip to content

Choose a model and a reasoning effort before a Thread starts - #37

Merged
QuintinBotes merged 2 commits into
mainfrom
launch-selectors
Aug 3, 2026
Merged

Choose a model and a reasoning effort before a Thread starts#37
QuintinBotes merged 2 commits into
mainfrom
launch-selectors

Conversation

@QuintinBotes

Copy link
Copy Markdown
Owner

Replaces #34, which GitHub auto-closed when its base branch was deleted on merging #33. Same work, rebased onto main so the diff is only its own.

LaunchConfig.model already existed and already emitted --model. Nothing ever set it, so the plumbing was there and unreachable: every Thread ran whatever the CLI defaulted to, and the single thing that most changes what a Thread costs was the one thing the composer could not express.

What is new

--effort is confirmed present on the shipped 2.1.220 binary, taking low, medium, high, xhigh, max. It had been assumed to be a slash command only, so this was verified against the binary rather than the docs.

The options are declared by the adapter, not listed in the UI

The rule the mode picker already follows: a control offering a choice the runtime would reject is worse than one offering none. AgentRuntime::launch_options() returns empty by default, so a runtime that takes neither draws no controls, and Codex does not get a picker full of Claude aliases.

Models are aliases, not pinned identifiers, because claude --help documents them as tracking whatever is current. A pinned claude-opus-4-1 rots in the worst way: the old name still resolves, so it fails by quietly running last year's model rather than by erroring.

The effort list has to be exact, and a test pins it. An unrecognised --effort value is only a warning — the CLI prints one line, falls back to the default, and runs anyway. A typo there yields a session that appears to run at the requested effort and does not.

Details

  • The alias and the model it resolved to are shown together once the session reports back, since they differ and the difference is the cost.
  • An empty selection means "whatever the profile already chooses" and is never sent as an empty flag value.
  • Switching profile clears both, because a profile can switch runtime.
  • launch_options rides on agents_overview, not agents_discovery: the composer draws before anything is probed.

Verified against the real binary: on this account --model sonnet resolves to claude-sonnet-5.

`LaunchConfig.model` existed and already emitted `--model`. Nothing ever set it,
so the plumbing was there and unreachable: every Thread ran whatever the CLI
happened to default to, and the one thing that most changes what a Thread costs
was the one thing the composer could not express.

`--effort` is now confirmed present on the shipped 2.1.220 binary, taking `low`,
`medium`, `high`, `xhigh` and `max`. It had been assumed to be a slash command
only. `LaunchConfig` carries it alongside the model and the adapter emits it.

The options are declared by the adapter, not listed in the UI. This is the rule
the mode picker already follows: a control offering a choice the runtime would
reject is worse than one offering none. `AgentRuntime::launch_options()` returns
empty by default, so a runtime that takes neither draws no controls, and Codex
does not get a picker full of Claude aliases.

Models are aliases rather than pinned identifiers, because `claude --help`
documents them as tracking whatever is current. A pinned `claude-opus-4-1` would
rot in the worst possible way: the old name still resolves, so it would fail by
quietly running last year's model rather than by erroring.

The effort list, by contrast, has to be exact, and a test pins it. An
unrecognised `--effort` value is only a warning: the CLI prints one line, falls
back to the default and runs anyway. A typo there produces a session that
appears to run at the requested effort and does not, which is the exact class of
silent mismatch this project exists to make visible.

Both are launch flags, so the pickers appear only while nothing is running. The
alias and the model it resolved to are shown together once the session reports
back, since they differ and the difference is the cost.

Two smaller things follow from the same reasoning. An empty selection means
"whatever the profile already chooses" and is never sent as an empty flag value.
And switching profile clears both, because a profile can switch runtime and an
alias one runtime resolves is one another may reject or, worse, misread.

`launch_options` rides on `agents_overview` rather than `agents_discovery`: the
composer draws these before anything is probed, and every adapter declares them
statically, so it costs a lock and a map.

rust 688 to 691, vitest 324 to 328.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@QuintinBotes
QuintinBotes enabled auto-merge (squash) August 3, 2026 15:56
@QuintinBotes
QuintinBotes merged commit 2e6ee24 into main Aug 3, 2026
3 checks passed
@QuintinBotes
QuintinBotes deleted the launch-selectors branch August 3, 2026 16:53
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