Skip to content

Tracer: Retain model usage after Session deletion #502

Closed

Description

@DoodleBears

Parent

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

What to build

Daily PersonaBot model usage remains visible after an ordinary Session is deleted or the Bot is archived, while a thorough PersonaBot purge removes its identifiable statistics; restart and reconciliation do not erase or double-count retained usage.

Acceptance criteria

  • Once an ordinary Orchestrator or Assignment Session history is deleted or unavailable, its daily Bot × execution role × provider/model totals remain visible in Profile.
  • The retained statistic contains no prompt, response, credential, or deleted-Session identifier; archiving the PersonaBot leaves totals inspectable.
  • A thorough PersonaBot purge removes its identifiable usage and does not leave Profile totals attributable to that Bot.
  • Duplicate or late event delivery, Host restart, and reconciliation preserve correct totals without clearing retained history or recounting surviving Session logs.
  • Automated coverage exercises public usage, source loss and purge behavior; an isolated DSH path lets a Human observe totals before and after source-history loss and restart.

Blocked by

Human clarification — 2026-10-01

Ordinary Session deletion must not clean up token statistics. This issue owns retained statistics independently of source-history availability; it does not require building a Session deletion feature first. A controlled source-unavailability experiment on real isolated DSH histories is valid E2E evidence and must be labeled honestly rather than described as a native deletion UI.

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: Retain daily exact-route usage through ordinary Session deletion and archive; purge identifiable totals; reconcile without replay duplication.
    • Branch: codex/502-retained-model-usage
    • Started: 2026-09-30 18:10 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 preflight finding

    Task: codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21.

    The pinned DSH 0.2.0-rc.1 SessionPersistence definition provides create/open/flush/stat/list; its Session Remote controller provides cancellation, cold reads and execution controls, but no durable Session deletion operation. session/disposed releases a live object and preserves history. BotHarness also has no public ordinary Session deletion command.

    The current Usage full-table rebuild does need replacement. However, the public deletion E2E promised here first needs a production Session history deletion capability. Cancelling a Turn or manually removing JSONL files would not demonstrate that contract.

    No code changed or PR created. Human has been asked whether to record the prerequisite and advance independent #503, or deliver Session deletion first. This claim remains active while resolving that delivery order.

  6. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent outcome

  7. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 2026
  8. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim — Retained usage statistic

    • Agent: Codex
    • Task: codex/local/01a0e445-0c0f-70e1-bad4-fd99c8cfaa21 (not a DSH Session)
    • Issue scope: Human clarified that ordinary Session deletion must not clean up token records. Persist idempotent usage independently of source-log availability; retain totals across reconciliation, restart and archive; remove Bot-identifiable usage on thorough PersonaBot purge. No new Session deletion feature.
    • Branch: codex/502-retained-usage-statistic
    • Started: 2026-10-01 03:20 UTC
    • State: active; continuing this task's earlier paused Tracer: Retain model usage after Session deletion #502 claim after Human clarification.
  9. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  10. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome — awaiting Human QA

  11. 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 Oct 1, 2026
  12. DoodleBears commented on Oct 1, 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