Codex Weekly Usage — August 24–30, 2026
Executive summary
Rock Paper Scissors operations led the available August 24–27 evidence; August 28–30 remain uncovered.
The four verified source days contain 149 active public summaries across four work arcs. Review and quality assurance is the strongest observed work-mode signal, followed by operations and fulfillment. Two outcome or decision signals and two follow-up categories remained open. The three uncovered days are unknown and are not represented as zero activity.
Codex execution telemetry is supporting evidence, not a measure of productivity, duration, or the week's value.
Distinct public work threads supported by retained Skysight summaries.
Public-safe outcomes or decisions supported by observed context.
Follow-ups the observed record does not show as resolved.
Top-level Codex tasks recorded in local execution logs; not a productivity score.
What shaped the week
Major work arcs
Rock Paper Scissors operations and Other observed work are the two largest observed arcs by retained summary mentions. Counts can overlap and do not represent duration.
Observed evidence by work arc
Retained structured-summary mentions; overlapping evidence, not time allocation.
Rock Paper Scissors operations
92 observedCatalog quality review and wholesale or fulfillment preparation.
Other observed work
40 observedObserved work that did not match a named public reporting arc.
Research and administration
29 observedResearch, purchasing, and administrative follow-through.
1 additional work arcLower-volume observed threads remain available without competing with the primary arcs.
Hyphenomenon product and reporting
16 observedProduct-system review, reporting strategy, and project sequencing.
Outcomes and decisions
Delivery and implementation progress
AdvancedRetained summaries indicate implementation, publication, deployment, or other delivery progress.
Review and verification decision
AdvancedRetained summaries indicate an approval, acceptance, verification, or passed review gate.
Next steps and open loops
Outstanding follow-through
OpenRetained summaries identify work that remained pending or still needed follow-through.
Unresolved quality or reliability issue
OpenRetained summaries identify an unresolved issue, defect, failure, or remediation need.
How the observed week unfolded4 day summaries
Aug 24
Rock Paper Scissors operations + Hyphenomenon product and reporting
36 active summaries, led by operations and fulfillment signals. 14 additional observed summaries were protected.
Aug 25
Rock Paper Scissors operations + Other observed work
43 active summaries, led by review and quality assurance signals. 17 additional observed summaries were protected.
Aug 26
Rock Paper Scissors operations + Other observed work
35 active summaries, led by review and quality assurance signals. 4 additional observed summaries were protected.
Aug 27
Rock Paper Scissors operations + Research and administration
35 active summaries, led by research and administration signals.
How to read this evaluationWork-mode signals, protected context, and evidence limits
Observed work-mode signals
Overlapping summary-level signals, not duration or a complete time sheet.
Privacy and evidence boundary
35 observed summaries were excluded from public topic analysis. Their time positions remain visible so the report does not mislabel protected context as missing or inactive.
This evaluation uses 197 summaries from four isolated Skysight source-contract v2 restores, each hash-verified with zero conflicts or disappeared records. Coverage is available for August 24–27; August 28–30 are missing and unverified, and capture completeness is not asserted. Protected topics remain excluded. Counts are overlapping evidence signals rather than duration, productivity, value, or unique task totals, and uncovered intervals remain unknown rather than zero activity.
Evidence appendix
Repository activity, delivery records, source evidence, and technical diagnostics support the evaluation without competing with its first read.
Explore supporting evidenceExecution, delivery, Skysight source context, and technical telemetry
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.
Output Shape
Compare the rollouts carrying the largest patches with the mix of file categories touched.
File Touch Mix
File touches grouped by category; exact counts and share of retained touches.
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.
Skysight Evidence Across The Week
This evidence view locates the public work arcs and protected-context positions that support the synthesis. The calendar grid is not expected computer activity, and values are not duration.
Rock Paper Scissors operations
Other observed work
Research and administration
Hyphenomenon product and reporting
Protected context
| Work domain | 12–4a | 4–8a | 8a–12p | 12–4p | 4–8p | 8p–12a |
|---|---|---|---|---|---|---|
| Rock Paper Scissors operations | Rock Paper Scissors operations, 12–4a: zero matches within retained summaries | Rock Paper Scissors operations, 4–8a: 41 summary mentions | Rock Paper Scissors operations, 8a–12p: 25 summary mentions | Rock Paper Scissors operations, 12–4p: 19 summary mentions | Rock Paper Scissors operations, 4–8p: 6 summary mentions | Rock Paper Scissors operations, 8p–12a: 1 summary mention |
| Other observed work | Other observed work, 12–4a: zero matches within retained summaries | Other observed work, 4–8a: 7 summary mentions | Other observed work, 8a–12p: 9 summary mentions | Other observed work, 12–4p: 14 summary mentions | Other observed work, 4–8p: 10 summary mentions | Other observed work, 8p–12a: zero matches within retained summaries |
| Research and administration | Research and administration, 12–4a: 1 summary mention | Research and administration, 4–8a: 15 summary mentions | Research and administration, 8a–12p: 5 summary mentions | Research and administration, 12–4p: 8 summary mentions | Research and administration, 4–8p: zero matches within retained summaries | Research and administration, 8p–12a: zero matches within retained summaries |
| Hyphenomenon product and reporting | Hyphenomenon product and reporting, 12–4a: zero matches within retained summaries | Hyphenomenon product and reporting, 4–8a: 8 summary mentions | Hyphenomenon product and reporting, 8a–12p: 8 summary mentions | Hyphenomenon product and reporting, 12–4p: zero matches within retained summaries | Hyphenomenon product and reporting, 4–8p: zero matches within retained summaries | Hyphenomenon product and reporting, 8p–12a: zero matches within retained summaries |
| Protected context | Protected context, 12–4a: 1 withheld summary mention | Protected context, 4–8a: 7 withheld summary mentions | Protected context, 8a–12p: 12 withheld summary mentions | Protected context, 12–4p: 12 withheld summary mentions | Protected context, 4–8p: 3 withheld summary mentions | Protected context, 8p–12a: zero matches within retained summaries |
Structured Evidence Coverage
Codex Execution Activity
Token and hourly activity describe the agent execution layer. They are supporting diagnostics, not a measure of the week's value, duration, or human productivity.
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
- 992,102,279
- Cached input
- 942,761,472
- Non-cached input
- 49,340,807
- Output
- 2,472,303
- Reasoning output
- 806,536
Cached input is 95% 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 2411
- Tue Aug 258
- Wed Aug 263
- Thu Aug 273
- Fri Aug 280
- Sat Aug 290
- Sun Aug 300
Each count is a de-duplicated session start assigned to that local calendar day.
Total: 6,512 tool calls. “c” marks successful commit operations in that hour.
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.