Skip to content

chore(agents): pin implementer subagents to claude-opus-4-7#40

Open
VoidAxiom wants to merge 1 commit into
mainfrom
sk/pin-implementer-model-opus-4-7
Open

chore(agents): pin implementer subagents to claude-opus-4-7#40
VoidAxiom wants to merge 1 commit into
mainfrom
sk/pin-implementer-model-opus-4-7

Conversation

@VoidAxiom

Copy link
Copy Markdown
Owner

Summary

Pin both implementer and ui-implementer subagent definitions to the explicit claude-opus-4-7 model ID instead of the drifting opus alias.

Why

The opus alias auto-upgrades when Anthropic ships a new Opus version (e.g. would land on Opus 4.8 the day it releases). Pinning to claude-opus-4-7 keeps subagent behavior reproducible across model releases — if we want to upgrade, we update the file deliberately.

Source

Claude Code subagent docs (https://code.claude.com/docs/en/sub-agents) — verbatim:

model | … sonnet, opus, haiku, a full model ID (for example, claude-opus-4-8), or inherit. Defaults to inherit

Full model ID: Use a full model ID such as claude-opus-4-8 or claude-sonnet-4-6. Accepts the same values as the --model flag

Test plan

  • YAML frontmatter still parses (no breaking syntax change)
  • Diff is 2 lines, one in each file
  • Next subagent dispatch will use the pinned model (effect is automatic on the next Agent call)

Previously both subagents used the `opus` alias which drifts as
Anthropic ships new Opus versions (e.g. would auto-upgrade to 4.8
when released). Pin to the explicit `claude-opus-4-7` model ID so
subagent behavior stays reproducible across model releases.

Per Claude Code subagent docs (https://code.claude.com/docs/en/sub-agents):
> Full model ID: Use a full model ID such as `claude-opus-4-8` or
> `claude-sonnet-4-6`. Accepts the same values as the `--model` flag.
@VoidAxiom

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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