My AI usage, across every agent
110 days and five kinds of AI agent working for me, counted the same way: 1,454 times an AI was set to work (sessions, tasks and routine runs). Claude Code, the one whose logs show it, wrote 57.6M tokens.
- 1,454times an AI was set to work: Claude Code sessions, Codex tasks and cloud routine runs
- 57.6Mtokens written by Claude Code (the only tool that reports it)
- 5kinds of agent working in KraigOS
- 110days with an AI at work since Jun 13
- 38days in a row, today included
The headline counts one thing every tool has: each time an AI was set to work, a Claude Code session, a Codex task or a cloud routine's run, each counted once. Tokens written are counted only from Claude Code's logs on this Mac, once per reply: Codex keeps no such number, and the cloud routines and the Grok bots report no tokens at all.
What each tool counts
The tools don't agree on what a token is, so they're never added together here. New input is what was sent to the AI fresh. Re-read from cache is the conversation so far, read again on every turn. Written is what the AI wrote back.
| Tool | New input | Re-read from cache | Written by the AI | Days | Sessions |
|---|---|---|---|---|---|
| Claude Codethis Mac | 965M | 50.8B | 57.6M | 75 | 425 |
| Counted by me from its session logs, once per reply, its helpers included. A reply I stopped partway counts what it had used; error notes with no AI behind them are left out. | |||||
| Codexthis Mac | – | – | – | 61 | 974 tasks |
| Its log keeps one figure per task, 18.0B in all, with reading and writing in the same number and nothing per turn, so it can't be split. My Codex profile says 19.9B on every device, counted its own way. | |||||
| Claude's cloud routinesthree desks | – | – | – | – | 55 runs |
| They run in the cloud and report no tokens to me. Each run counts once, when the routine writes its line in KraigOS. The night shift runs as Claude Code on my Mac, so it's in the first row. | |||||
| The Grok botsin KraigOS | – | – | – | – | – |
| No tokens reported anywhere I can read. They count by the changes they write into KraigOS, further down. | |||||
Every day, by tool
One square a day, a column a week. I built with Codex from July and moved to Claude Code around September 22; the orange before that is the Claude Code I'd been trying since June.
- Codex
- Claude Code
- Both that day
- Cloud routines
- Darker: more sessions and tasks
Two eras
The Codex era
July to September 20, my Codex profile page, as of Oct 14, 2026
- Lifetime tokens, its own count
- 19.9B
- Busiest day, its own count
- 1.9B
- Longest task
- 7h 20m
- Longest streak
- 55 days
- Tasks on this Mac
- 974
The Claude era
Claude Code on this Mac, Jun 13 to Oct 29, 2026
- Tokens written
- 57.6M
- Sessions
- 425
- Longest session
- 9 days 15 hours
- Longest streak
- 38 days
- Busiest day
- Oct 27, 3.9M written
- Most used model
- Opus 5.5
- re-read from cache: 50.8B (98.0%)
- written to cache: 965M (1.9%)
- written by Claude: 57.6M (0.1%)
- new input: 539K (0.0%)
All of Claude Code's tokens together come to 51.8B, but 98% of that is Claude re-reading the conversation so far on every turn. That's why the headline counts only what it wrote.
Sessions by week
Both tools on this Mac, by the unit they share: a Claude Code session or a Codex task, each counted on the day it started.
Tallest week: 446 sessions and tasks, week of Aug 24
- Codex (this Mac)
- Claude Code (this Mac)
What the tokens shipped
Tokens are only the input. This counts what went out each week: posts live on every platform, films published, articles, devlog entries and newsletters, builds of KraigOS, its app and my game, and business handled.
- 831things shipped since Aug 3
- 48.1Ktokens written per thing shipped, the last 4 weeks
- 239shipped in the busiest week, week of Oct 19
Tallest week: 239 things shipped · the line is tokens written (tallest 11.7M)
- Posts live
- Films published
- Articles, devlogs and newsletters
- Builds
- Deals and emails
- Tokens written (Claude Code, this Mac)
September was building the rails: the system, the routines, the checks. From October on, it's shipping.
Who does the work in KraigOS
Every agent writes what it did into KraigOS, the system that runs my work. This is each one's share of those changes by week. The Worker is KraigOS's own code: it runs on a timer and calls no AI model.
- Codex and ChatGPT
- Claude
- Grok
- The Worker
- Other agents
| Agent | Changes to records, since Aug 24 | Lines in the log, since Oct 25 |
|---|---|---|
| Codex and ChatGPT | 11,146 | 0 |
| Claude | 3,198 | 1,280 |
| Grok | 266 | 62 |
| The Worker | 557 | 5,670 |
| Other agents | 217 | 89 |
The routines
The jobs that run without me starting them. A run is counted when the routine writes its line in KraigOS.
| Routine | Runs on | Week of Oct 19 | Week of Oct 26 |
|---|---|---|---|
| Inbox and calendar4 times a day, since Oct 21 | Claude in the cloud | 24 | 17 |
| Daily deskevery morning, since Oct 26 | Claude in the cloud | 0 | 5 |
| Content feedback deskevery day, since Oct 22 | Claude in the cloud | 4 | 5 |
| Night shift on the Macevery night, since Oct 26 | Claude on my Mac, overnight | 0 | 12 |
| The KraigOS Workerevery 5 minutes, plus hourly and daily jobs; no AI model | Cloudflare | about 337 a day | |
What all this runs
All of it goes into one thing: KraigOS, the small system I built with AI to run my work as a filmmaker. It keeps my inbox and calendar, plans and posts my short clips, keeps the books tidy and logs every call it makes for me, so I only decide what needs me. How it was built, step by step, is in the KraigOS devlog, and why I built it is in I built my own operating system.