Skip to content

Tracer: Migrate and repair PersonaBot model routes #500

Closed

Description

@DoodleBears

Parent

#488 — PersonaBot model presets and per-Session model routing.

What to build

An upgraded PersonaBot with a legacy single-model choice either gains an unambiguous exact route or waits for Human repair; unavailable routes and credentials stop new requests visibly without choosing another provider.

Acceptance criteria

  • A legacy model that maps to exactly one available provider is migrated to a valid Bot plan without changing its DSH Agent preset for tools and prompts.
  • An ambiguous or missing legacy provider leaves the Bot requiring Human selection; no new model request runs on a guessed route.
  • If a selected provider/model/effort or its credential becomes unavailable, the next request stops with a repairable Human-facing explanation and no silent fallback.
  • After the Human selects a valid route, a real Orchestrator request succeeds and Profile shows the repaired effective plan.
  • Automated migration and Host-boundary tests cover unique, ambiguous, missing, and unavailable cases; an isolated DSH repair path is Human-testable with screenshots where UI changes.

Blocked by

Activity

  1. added this to the v1.0 milestone on Sep 29, 2026
  2. added
    ready-for-agentFully specified, ready for an AFK agent
    area:fullstackEnd-to-end Host and Client implementation
    scope:tracerHuman-testable implementation slice
    feature:profilePersonaBot Profile surface (popover, view, cards)
    on Sep 29, 2026
  3. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21 (not a DSH Session)
    • Issue scope: Tracer: Migrate and repair PersonaBot model routes #500 legacy PersonaBot model-route migration and repairable unavailable-route handling
    • Branch: codex/500-model-route-repair
    • Started: 2026-09-30 10:57 UTC
    • State: active
  4. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 2026
  5. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

  6. added and removed
    ready-for-agentFully specified, ready for an AFK agent
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 2026
  7. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fullstackEnd-to-end Host and Client implementationfeature:profilePersonaBot Profile surface (popover, view, cards)scope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions