Skip to content

fix(reporting): Include auxiliary model costs#854

Draft
dcramer wants to merge 1 commit into
mainfrom
codex/include-auxiliary-model-costs
Draft

fix(reporting): Include auxiliary model costs#854
dcramer wants to merge 1 commit into
mainfrom
codex/include-auxiliary-model-costs

Conversation

@dcramer

@dcramer dcramer commented Jul 12, 2026

Copy link
Copy Markdown
Member

Conversation cost reports now include model calls made on behalf of the root conversation outside the main agent loop: advisor runs, compaction, vision summaries, title generation, image-prompt enrichment, and structured reply classification. Child conversations remain excluded from top-level reporting while their model usage rolls into the parent.

Auxiliary contributions are stored in junior_conversation_usage_events with a unique call ID, making persistence retries idempotent while the conversation row remains the reporting read model. Legacy Drizzle adoption now distinguishes baseline, metrics-only, and usage-event schemas so older deployments apply only the missing migrations. Image-generation media charges remain outside this text-model estimate because the raw image endpoint does not expose normalized model cost; prompt enrichment is included.

Conversation cost totals only included the main agent loop, so advisor, compaction, vision, title, prompt-enrichment, and classifier calls were omitted.

Persist idempotent auxiliary usage events on the root conversation and preserve them across execution summary replacement. Extend legacy migration adoption for the new table.

Co-Authored-By: GPT-5 Codex <noreply@openai.com>
@vercel

vercel Bot commented Jul 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
junior-docs Ready Ready Preview Jul 12, 2026 3:30pm

Request Review

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant