Skip to content

feat(models): move Sol to gpt-6-sol and Grok to grok-4.7 - #83

Open
rasmushjulskov wants to merge 1 commit into
ericlitman:mainfrom
rasmushjulskov:models/gpt-6-sol-grok-4.7
Open

rasmushjulskov wants to merge 1 commit into
ericlitman:mainfrom
rasmushjulskov:models/gpt-6-sol-grok-4.7

Conversation

@rasmushjulskov

Copy link
Copy Markdown

Summary

Moves two model families in the provider-dispatch matrix to their current releases:

Family Before After
sol codex:gpt-5.6-sol codex:gpt-6-sol
grok grok:grok-4.6 grok:grok-4.7
  • GPT-6 Sol shipped on 2026-09-22. Codex CLI 0.155.1 now describes gpt-5.6-sol as an "Older coding model". OpenAI reports that 6 Sol makes about half as many mistakes as 5.6 Sol.
  • Grok 4.7 shipped on 2026-09-21. It's the default in grok models on Grok CLI 1.0.41, at the same price and speed as 4.6. Cursor upstream also moved its Grok defaults to 4.7 in 70b2dc8.
  • Fable and Opus use rolling aliases, so they already pick up Opus 5.5 and needed no change.

What changed

  • The Model column of the matrix in provider-dispatch.md, plus the note about which Grok CLI model is pinned.
  • The first-run sheet in setup-pstack.
  • Default descriptors in arena, architect, interrogate, how, swarm, the poteto-mode playbooks and codex-tools.md.
  • The same wording in README.md, docs/reference.md, UPSTREAM.md and CHANGES.md.

Left as they were:

  • The Sol "Upstream pstack choice" cell stays gpt-5.6-sol-max, because Cursor upstream hasn't moved yet.
  • Historical changelog prose.
  • Runner test fixtures that use model names only as sample strings.
  • The effort ladder. gpt-6-sol also offers ultra, but that effort delegates work automatically, which conflicts with the runner's no-recursive-agents rule, so it stays excluded.

Verification

  • bun run test: 158 pass, 0 fail.
  • bun run typecheck: clean.
  • PSTACK_STATIC_ONLY=1 bash tests/skill-collision-repro.sh: ok.
  • I have not run the behavioral lanes that UPSTREAM.md asks for (a live /setup-pstack probe of codex:gpt-6-sol@max and grok:grok-4.7@xhigh).

GPT-6 Sol (Sep 22) supersedes GPT-5.6 Sol in Codex, which now labels
5.6 Sol as an older model. Grok 4.7 (Sep 21) is the Grok CLI default and
matches Grok 4.6 on price and speed. Update the provider-dispatch matrix,
first-run sheet, skill and playbook defaults, and docs. Fable and Opus
already use rolling aliases and are unchanged.
@mergify

mergify Bot commented Sep 23, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@greptile-apps

greptile-apps Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 4/5

The PR is not yet safe to merge because existing configured installations are not migrated to the new Sol and Grok matrix entries and can no longer rerun setup without manual repair.

Findings

  1. P1 Existing sheets cannot migrate ▶
  2. P2 New routes remain unverified ▶

Summary

This PR updates the default Sol and Grok families throughout the provider matrix, setup sheet, workflow playbooks, and user documentation.

  • Moves Sol defaults from gpt-5.6-sol to gpt-6-sol.
  • Moves Grok defaults from grok-4.6 to grok-4.7.
  • Keeps the existing provider routes and effort levels.
  • Needs migration handling for descriptors persisted by earlier releases and the repository-required live provider verification.

Reviews (1) · Last reviewed commit: "feat(models): move Sol row to gpt-6-sol ..."

Comment on lines +14 to +15
| sol | gpt-5.6-sol-max | codex | gpt-6-sol | max | low medium high xhigh max | - |
| grok | grok-4.7-xhigh-fast | grok | grok-4.7 | xhigh | low medium high xhigh max | - |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Existing sheets cannot migrate

Changing these matrix keys strands existing installations on the old model descriptors. Runtime normalization only handles versioned Claude aliases, so persisted codex:gpt-5.6-sol and grok:grok-4.6 entries continue dispatching the old versions. When users rerun /setup-pstack, its exact provider/model matching treats those entries as inconsistent state and stops before it can preserve their role assignments on the new releases. Add an explicit migration for the prior Sol and Grok descriptors before matrix matching.

Comment on lines +14 to +15
| sol | gpt-5.6-sol-max | codex | gpt-6-sol | max | low medium high xhigh max | - |
| grok | grok-4.7-xhigh-fast | grok | grok-4.7 | xhigh | low medium high xhigh max | - |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 New routes remain unverified

The repository requires installed Claude Code and Codex behavioral checks for changes to this surface, but these new model routes have not received those live probes. Static consistency tests cannot show that gpt-6-sol@max works through the native and external Codex routes or that Grok CLI lists and executes grok-4.7@xhigh. Run and record the required probes before retaining the documentation’s claim that the frontier panel was verified in fresh sessions.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@openswebot openswebot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open SWE Review found 2 potential issues.

Open in Web

Comment on lines +14 to +15
| sol | gpt-5.6-sol-max | codex | gpt-6-sol | max | low medium high xhigh max | - |
| grok | grok-4.7-xhigh-fast | grok | grok-4.7 | xhigh | low medium high xhigh max | - |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 Existing model sheets fail the version switch

Changing these (provider, model) keys leaves existing sheets seeded from the previous defaults with codex:gpt-5.6-sol and grok:grok-4.6. The only read-time migration handles versioned Fable/Opus, so installed users continue dispatching to the old Sol/Grok models; when they rerun /setup-pstack, step 3 treats those previously generated descriptors as unmatched, stops before probes, and cannot save the new choices without manually replacing each affected lane. Migrate the two previously generated descriptors during read-time routing and setup loading, preserving role, order, and effort, before matching the new matrix.

(Refers to lines 14-15)


Your feedback helps Open SWE learn. React with 👍 or 👎 to tell us if this review comment was useful.

Comment on lines +91 to +93
feature, refactoring: grok:grok-4.7@xhigh
bug-fix: codex:gpt-6-sol@max
perf-issue: codex:gpt-6-sol@max

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Model change lacks required installed-surface verification

This changes the real Sol and Grok probe/dispatch defaults, but the PR explicitly says neither new descriptor has been live-probed through /setup-pstack. The repository's AGENTS.md requires the exact candidate installed and the changed behavior exercised on the real user surface in every affected harness, with version, surface, action, and observed result recorded; a PR without that evidence must remain a draft. This PR is currently non-draft. Keep it in draft until the installed Claude Code and Codex lanes for these descriptors have been observed and the evidence recorded.

(Refers to lines 91-93)


Your feedback helps Open SWE learn. React with 👍 or 👎 to tell us if this review comment was useful.

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