Codex Weekly Usage — August 10–16, 2026
An orchestration-heavy week spread 39 de-duplicated sessions across Hyphenomenon, Shopify Headless, multi-mailbox operations, and projectless work, while execution concentrated sharply in Shopify: 161 active rollouts included 122 delegated runs, Tuesday carried 83.0% of processed model context, and terminal evidence named five repositories with delivery traces.
Template-generated · Analyzer: codex-usage-report-v6 · Model: gpt-5.6-sol · high
Input plus output tokens in retained local Codex telemetry; includes cached input and is not a cost or productivity score.
Top-level rollout files active in the window; delegated rollouts are counted separately.
Subagent or spawned-thread rollout files with timestamped activity in the window.
Recorded turn contexts across top-level and delegated rollouts; not elapsed work time.
Token Usage
Cumulative runtime counters are differenced per rollout. Repeated snapshots are ignored; cached input stays visible instead of being mistaken for fresh context.
Token Usage
Retained local Codex telemetry only; not an account-wide usage or billing statement.
- Input
- 23,617,947,530
- Cached input
- 23,134,567,168
- Non-cached input
- 483,380,362
- Output
- 47,947,822
- Reasoning output
- 12,474,725
Cached input is 98% of input. Reasoning output is included within output tokens.
Tokens By Day
Processed input plus output assigned to the local day of each positive cumulative-counter increment.
Activity By Day And Clock Hour
The day row shows each date in the report window. The hour chart below combines the same clock hour across all seven days; it is not a single-day timeline.
- Mon Aug 108
- Tue Aug 1110
- Wed Aug 125
- Thu Aug 133
- Fri Aug 141
- Sat Aug 156
- Sun Aug 166
Each count is a de-duplicated session start assigned to that local calendar day.
Total: 24,639 tool calls. “c” marks successful commit operations in that hour.
Where The Work Landed
Repository activity and changed lines show which codebases received attention during the report window.
Tool Calls By Repository
Working repository resolved from tool workdir or turn context.
Patch Churn By Repository
Added plus removed lines recorded in patch inputs.
Output Shape
Compare the rollouts carrying the largest patches with the mix of file categories touched.
Patch Churn By Rollout
Top-level | Outside git metadata
File Touch Mix
Verified Delivery Ledger
Outcomes come from terminal return records. Intent-only command counts remain in the technical appendix.
Command Outcomes
Repositories In Successful Push Output
Agent Stack Used
Observed runtime evidence only; the available catalog is excluded. Status chips distinguish completed calls, skill loads, and explicit requests.
- Invoked means a completed runtime call was recorded.
- Loaded means a skill file was read or discovered.
- Requested marks an explicit skill request in the source.
- The logs do not preserve a reliable causal chain between every layer, so the diagram shows observed layers rather than inventing one.
Apps and Connectors
Completed connector calls recorded by the runtime.
Tool Providers
Completed MCP provider calls, grouped by server namespace.
Skills
Explicitly requested or loaded skills; application is not inferred.
Chronicle Context Across The Week
These panels are calculated directly from persisted Chronicle summaries. Lane counts overlap and are not duration.
Work Lane Mentions
Evidence Coverage
Technical Telemetry
Raw tool, event, workspace, and patch diagnostics used to audit the analyzer. These counts are intentionally secondary to outcomes.
Tool Surfaces
Function Calls
Custom Tool Calls
Specific custom calls and their share of all recorded tool events.