Repository navigation
Tracer: Select an allowed model for a new Assignment #504
Description
Parent
#488 — PersonaBot model presets and per-Session model routing.
What to build
A Human configures several exact Assignment routes and per-model reasoning-effort limits in a PersonaBot Model Plan; a new Assignment uses its default or an Orchestrator-selected allowed combination in a real DSH Session.
Acceptance criteria
- The Human can set an Assignment route set, allowed efforts and a default effort for each route, plus one default route; Profile shows the saved effective plan.
- A newly created Assignment with no explicit choice uses the current default provider/model/effort; an explicit permitted choice is used for its first real model request.
- The Host rejects a provider, model, or effort outside the current plan before starting new work, with a readable result for the Orchestrator and Human.
- Selection is scoped to the owned Assignment Session and does not mutate the Orchestrator route or deployment-wide DSH default.
- Automated coverage reaches the public Assignment command and DSH execution seam; isolated DSH Human QA shows the chosen route and real Assignment reply, with screenshots for changed UI.
Blocked by
- Tracer: Apply a Model Preset to a real Orchestrator #498 — Bot-local Model Plan and real Orchestrator route.
Activity
DoodleBears commentedon Sep 29, 2026
Agent work claim
codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21(not a DSH Session)codex/504-assignment-model-selectionfeat(core): select allowed models for new Assignments (#533)
DoodleBears commentedon Sep 30, 2026
Agent work completion