golem15/msd-core
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs(#3530): correct model/effort precedence claims in model-profiles.md (#3536)

Browse Source 
* docs(#3530): correct model/effort precedence claims in model-profiles.md

* chore(#3530): backfill changeset pr number

---------

Co-authored-by: sim <sim@local>
This commit is contained in:
Tom Boucher
2026-08-15 07:15:32 -04:00
committed by GitHub
parent 59e7a677fe
commit bc9a22868f
2 changed files with 17 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/agile-tigers-cheer.md Normal file
View File

@@ -0,0 +1,5 @@
---
type: Fixed
pr: 3536
---
**Corrected `model-profiles.md`: `model` and `effort` do not resolve through one shared precedence ladder** — the reference previously claimed a `models[phase_type]` or `dynamic_routing` override flips both, and that an effort config change takes effect like a model change. In reality effort (claude runtime) is baked into agent frontmatter at install time and requires `node gsd-tools.cjs effort sync --apply` to change; Codex agents pin `model_reasoning_effort` in generated `.toml` files. (#3530)

16
gsd-core/references/model-profiles.md
View File

@@ -219,10 +219,18 @@ is (highest → lowest):
6. Pass model parameter to Task call
```
The same precedence applies to `reasoning_effort` resolution on runtimes
that support it (Codex), so `model` and `reasoning_effort` always derive
from the same tier source — a `models[phase_type]` or
`dynamic_routing` override flips both.
`model` and `effort` resolve through different mechanisms at different
times — they do not share the ladder above. `model` resolves at runtime,
per spawn, from `.planning/config.json`; a config change takes effect on
the next spawn. `effort` (claude runtime) has its own cascade
(`agent_overrides` → `routing_tier_defaults` → `default`; see
`docs/CONFIGURATION.md` § "Where effort actually reaches") and is baked at
install time into the `effort:` frontmatter key of
`~/.claude/agents/gsd-*.md` — Claude Code's Agent tool has no per-spawn
effort parameter, so per-agent frontmatter is the only channel. An effort
config change has no effect until `node gsd-tools.cjs effort sync --apply`
re-syncs the agent files. Codex agents instead pin
`model_reasoning_effort` in `~/.codex/agents/*.toml` at install time.
## Per-Agent Overrides