fix: pin background:false on the remaining context:fork skills; bump CURRENT.opus to claude-opus-5 - #1656
Open
elhoim wants to merge 2 commits into
Open
Conversation
Claude Code 2.1.218 changed skills declaring `context: fork` to dispatch as detached background agents by default, opt-out via `background: false`. Research, Council, Ideate, Evals, SystemsThinking, RootCauseAnalysis and Knowledge all declare `context: fork` and their workflows return results inline to the calling thread. Under the new default their output arrives as a task notification instead, so the invoking turn sees nothing. Pin the previous behaviour explicitly rather than inheriting a default that changed underneath the skill. (cherry picked from commit 36c4540)
Claude Opus 5 shipped 2026-07-24 and is the default Opus model. The
registry still pinned claude-opus-4-8 — the exact drift this file exists
to prevent, and the one its own header cites as the cautionary example.
Applied via `UpdateModels.ts --apply opus claude-opus-5`. Blast radius is
small: consumers that take the tier ALIAS were already auto-resolving, so
only pinnedModelForEffort() and the drift scanner change behaviour.
Left alone deliberately: the dated probe records in the architecture doc
and ALGORITHM/changelog.md are history and should keep naming the model
that actually ran, and cost-aggregator's includes("opus") fallback already
returns correct pricing since Opus 5 holds Opus 4.8's $5/$25 rate.
(cherry picked from commit c6f6185)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two places where the harness or the model lineup moved and the payload didn't.
context: forkskills were silently detached2.1.218 changed skills declaring
context: forkto dispatch as detached background agents by default, opt-out viabackground: false.Seven skills declare
context: fork— Research, Council, Ideate, Evals, SystemsThinking, RootCauseAnalysis, Knowledge — and their workflows all return results inline to the calling thread. Under the new default their output arrives as a task notification instead, so the invoking turn sees nothing. Pins the previous behaviour explicitly rather than inheriting a default that changed underneath the skill.Note on overlap with #1570: that PR opted Knowledge out and you ported the documentation half into
SkillSystem.md. This is the same reasoning applied to the other six skills, which have the same inline-return shape. If the portedSkillSystem.mdguidance intends some of them to stay backgrounded, say which and I'll trim the set.Verified — all seven
SKILL.mdfiles re-parsed after the edit;backgroundlands inside the frontmatter block in each, withcontextandbackgroundboth present.CURRENT.opusstill pinnedclaude-opus-4-8Claude Opus 5 shipped 2026-07-24 and is the default Opus model.
models.tscalls itself the single edit point on a model release, and its header cites exactly this drift as the cautionary example (ContextAuditchecking forclaude-opus-4-7long afterclaude-opus-4-8shipped).Applied via the repo's own
UpdateModels.ts --apply opus claude-opus-5.Blast radius is small — consumers taking the tier ALIAS were already auto-resolving, so only
pinnedModelForEffort()and the drift scanner change behaviour.Verified —
pinnedModelForEffort("high")→claude-opus-5;isCurrent("claude-opus-4-8")→ false.Deliberately left alone: the dated probe records in
LifeosSystemArchitecture.mdandALGORITHM/changelog.mdare history and should keep naming the model that actually ran, andcost-aggregator'sincludes("opus")fallback already returns correct pricing since Opus 5 holds Opus 4.8's $5/$25 rate.