Skip to content

Tracer: Attribute multi-model usage across owned Sessions #503

Closed

Description

@DoodleBears

Parent

#39 — Usage read model / Typert remote / Profile contract; part of #34.

What to build

The PersonaBot Profile attributes real Orchestrator, Assignment, and DSH Subagent attempts to their owning Bot and execution role; a Turn that uses more than one provider/model contributes to each exact route separately.

Acceptance criteria

  • Trusted Session ownership attributes Orchestrator, Assignment, and DSH Subagent usage to the correct PersonaBot; unowned or ambiguous work never appears under a guessed Bot.
  • A Turn using multiple models appears as separate provider/model contributions rather than one mixed bucket, with the correct execution role for each attempt.
  • Provider-reported usage from retry and failed attempts counts exactly once; a missing provider report is marked unknown rather than zero.
  • Profile shows the role and route breakdown through the Host read model without exposing private DSH logs or deleted-Session detail.
  • Focused tests cover mixed-route, retry, failure, Subagent ownership, and unknown cases; an isolated DSH scenario provides a visible result and screenshots for Human QA.

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
    feature:usageUsage and cost attribution
    scope:tracerHuman-testable implementation slice
    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: Attribute durable model settlements individually to exact provider/model and trusted Orchestrator, Assignment or Subagent ownership; retain reported failure/retry usage and unknown buckets.
    • Branch: codex/503-attempt-model-usage
    • State: active
    • Started: 2026-09-30 17:59 UTC
  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:usageUsage and cost attributionready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions