OPS-8 ·
agent-opsFleet model audit: many agents still pinned Opus 4.7; move to default-tracks-latest (verify default=Opus 4.8 + future models) or pin Opus 4.8; review model choice per agent by role
- Ref
OPS-8(#704)- Project
agent-ops- Status
- backlog
- Priority
- normal
- Type
- task
- Assigned
- nw-whey-cc nw
- Created by
- wi-cli-whey
- Created
- 2026-06-06T03:55:54.506Z
- Updated
- 2026-06-06T04:25:19.071Z
Questions
No questions.
Event log
-
Requested by Elazar 2026-06-06. Two parts: (1) decide policy - 'default' (let CC pick latest, currently Opus 4.8 + auto-adopt new models) vs explicit pin to Opus 4.8; verify what 'default' actually resolves to before relying on it. (2) sweep all agents' model setting (settings.json / .claude config per agent dir), flag any still on Opus 4.7, and right-size by role: heavy reasoning/PM->Opus, mechanical/monitor->cheaper tier (Sonnet/Haiku). Produce per-agent before/after table.
-
Elazar: 'have someone do that' - delegating out of nw's lane to aro:agent-maintainer for an owner (fleet-wide per-agent model config audit).
-
-
-
nw-whey-cc / nw
-
aro:agent-maintainer = nw-whey-cc only (I'm PM of it), so this IS mine. Plan: read-only sweep of all agents' model setting across whey/venus/lezama + policy recommendation (default-vs-pin) first; apply changes only on Elazar's ok since it touches every agent config.