Skip to content

orchestrate: GPT-6 Sol replaces Astra as the bundled Codex executor - #508

Merged
Tryanks merged 3 commits into
mainfrom
orchestrate/sol-executor
Sep 22, 2026
Merged

Tryanks merged 3 commits into
mainfrom
orchestrate/sol-executor

Conversation

@Tryanks

@Tryanks Tryanks commented Sep 22, 2026 •

Copy link
Copy Markdown
Owner

The execution layer's bundled Codex profile is now gpt-6-sol; Astra
stays a bundled collaboration peer and can still be added as an executor
by hand. Sol's guidance chooses effort per task (low for small clear
briefs, medium for routine work, higher as constraints grow) instead of
Astra's low-only rule, and the workflow prompt and settings copy follow.

Migration: an untouched bundled Codex executor row, whether the old
Sol 5.6 default or either Astra default text, becomes the Sol 6 built-in
unless the user already added Sol 6; rows with custom text, an endpoint
profile, or changed switches stay as they are.

Sol's profile now follows OpenAI's model guidance rather than Astra's
low-only rule: built for complex coding and agentic workflows, about half
the factual errors of GPT-5.6 Sol, Astra-level reliability at a fraction
of the cost, Opus-class computer use at far lower cost per task, and
medium as the recommended starting effort. It is named the primary
executor so ordinary work goes there first.

Opus 5.5's profile is reworded as the secondary executor: a Claude Code
perspective, a cross-provider second implementation or review, or a
fallback when Sol is unavailable or stalls. The previous Opus text is
kept as a constant so untouched rows migrate to the new wording and
customised ones are left alone. The workflow prompt and settings copy
say the same.

Sources

Checks

  • cargo fmt --all --check, cargo clippy --workspace --all-targets --locked -- -D warnings, cargo nextest run --workspace --locked (929 passed, 5 skipped)

The execution layer's bundled Codex profile is now `gpt-6-sol`; Astra
stays a bundled collaboration peer and can still be added as an executor
by hand. Sol's guidance chooses effort per task (low for small clear
briefs, medium for routine work, higher as constraints grow) instead of
Astra's low-only rule, and the workflow prompt and settings copy follow.

Migration: an untouched bundled Codex executor row, whether the old
Sol 5.6 default or either Astra default text, becomes the Sol 6 built-in
unless the user already added Sol 6; rows with custom text, an endpoint
profile, or changed switches stay as they are.
… is the second opinion

Sol's profile now follows OpenAI's model guidance rather than Astra's
low-only rule: built for complex coding and agentic workflows, about half
the factual errors of GPT-5.6 Sol, Astra-level reliability at a fraction
of the cost, Opus-class computer use at far lower cost per task, and
medium as the recommended starting effort. It is named the primary
executor so ordinary work goes there first.

Opus 5.5's profile is reworded as the secondary executor: a Claude Code
perspective, a cross-provider second implementation or review, or a
fallback when Sol is unavailable or stalls. The previous Opus text is
kept as a constant so untouched rows migrate to the new wording and
customised ones are left alone. The workflow prompt and settings copy
say the same.
…py, and research

Sol: close instruction following, reliable goal completion, computer use,
lower cost. Opus 5.5: first choice for UI design, copywriting, creative and
open-ended research work, and a cross-provider second implementation or
review. Workflow prompt and settings copy say the same.
@Tryanks
Tryanks merged commit bffc4a0 into main Sep 22, 2026
7 checks passed
@Tryanks
Tryanks deleted the orchestrate/sol-executor branch September 22, 2026 19:11
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