Repository navigation
Tracer: Switch an existing Assignment model on its next request #506
Description
Parent
#488 — PersonaBot model presets and per-Session model routing.
What to build
An Orchestrator can switch an existing Assignment to another currently allowed provider/model/effort for its next request, while a preset change alone leaves that Assignment on its current route.
Acceptance criteria
- Applying a new Model Preset during an existing Assignment does not change that Session's effective route, even when the old route is no longer allowed for new work.
- The Orchestrator can explicitly request another route and effort from the Bot's current Model Plan; the Assignment's next real model request uses the new selection without restarting the Session.
- An explicit switch to a route or effort outside the current plan is rejected and leaves the Assignment on its previous route.
- Profile or Session-visible information distinguishes the current effective Assignment route from the Bot's default for newly created Assignments.
- Focused Host/DSH Session tests and isolated DSH Human QA cover retained-old-route, permitted switch, denied switch, and next-request timing; changed UI includes screenshots.
Blocked by
- Tracer: Edit and switch independent Model Preset snapshots #501 — applying and switching independent Bot snapshots.
- Tracer: Select an allowed model for a new Assignment #504 — Assignment route and effort selection for new Sessions.
Activity
DoodleBears commentedon Sep 30, 2026
Agent work claim
codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21(not a DSH Session)codex/506-assignment-switchKeep Assignment model when request delivery fails
Allow existing Assignments to switch models (#555)
DoodleBears commentedon Sep 30, 2026
Agent work outcome
codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21c742f6df19143dfaaf560c93d5041718cb947009