Codex Weekly Usage — July 13–19, 2026
A concentrated Hyphenomenon delivery week: 29 de-duplicated Codex sessions across 57 rollout logs, an early-week push, a two-day evidence gap, and a weekend return with verified delivery to two repositories.
Analyzer: codex-usage-report-v5
De-duplicated by session_meta.session_id; 57 active rollout log files are tracked separately.
Verified from terminal outcomes; operations are not independent feature units.
Unique paths in successful patch-application records.
codex-skills and hyphenomenon
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 Jul 137
- Tue Jul 142
- Wed Jul 159
- Thu Jul 160
- Fri Jul 170
- Sat Jul 186
- Sun Jul 195
Each count is a de-duplicated session start assigned to that local calendar day.
Total: 12,251 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.
Delivery Extended Beyond One Repository
Hyphenomenon dominated resolved tool activity, but it was not the whole operating surface. Another 1,352 tool calls (11%) occurred outside resolved git metadata, and smaller command-level traces resolved to shopify-headless, bpe-marketing-lp, codex-skills, and shopify-ai-product-optimizer. Only Hyphenomenon and codex-skills appear in successful push output, so the other repository labels are activity evidence rather than delivery claims.
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
Top-level | hyphenomenon
Top-level | hyphenomenon
Top-level | hyphenomenon
Top-level | hyphenomenon
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
Verification Was Part Of The Work
Terminal outcomes record 90 successful commit operations, 66 successful content pushes, 61 successful pull-request operations, and 6 successful branch-cleanup pushes. The evidence also retains 12 content pushes with unknown outcomes, 3 pending pushes, 28 pull-request operations with unknown outcomes, 9 pending pull-request operations, and 4 failures. Successful operations are verified outcomes, but the unresolved tail prevents a claim that every attempted delivery completed cleanly.
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.