A session, start to finish
Every agent follows the same loop, on any machine.
Step 2 is where most of the savings are. More on that next.
Reading as little as possible
Everything an agent reads costs tokens and time. The repo holds about 1 MB of notes in 135 files. A normal session reads 20 KB of it.
Text read before starting work
KB, network projectThe 20 KB are the two rule files that load automatically. Anything changed since last time adds its diff, usually a few KB.
- Only what changedEach machine stores the last commit it read and reads only the diffs since then. Nothing new means nothing to read.
- Only the files that matterThe diff is filtered to this project and the shared rules. Data the tools write themselves is skipped.
- Short logsNewest 20 entries, 5 lines each, conclusions only. Older ones move to an archive nobody opens by default. 44k → 19k tokens.
- Only your projectAgents never open another project's folder. Side projects (250 KB) stay closed unless the task names them.
- An index firstOne page says which document to open for which job, and which old documents are out of date.
- Short entry docsEach project's entry file is under 150 lines. Details live in documents that are opened only when needed.
What each machine reads
example historyWhere the rules live
Three layers. A lower layer can be stricter, never looser.
CLAUDE.mdRules for every project: syncing, commits, passwords, web design
<project>/CLAUDE.mdOnly what's special about that project: deploy steps, known traps
<side>/WORKFLOW.mdSide projects. Agents skip these unless asked
Handing over
An agent that stops halfway leaves a short log entry and plan items the next one can act on without asking.
Log entry
5 lines max## v2026.11.05-1 · Mac · Claude Opus 5.5 - what changed and why - files touched, what's deployed, what was NOT tested
Plan item
stands on its own- [ ] one-line task - what's already checked - exact commands - do NOT touch: …
Two agents, one website
Before deploying, an agent claims the domain with a small tool, zl. If someone else holds it, the agent stops and tells me.
Try it
same messages as the real tool$ # press a button
Commits per month
Nov through the 20thData table
Rules I added after mistakes
If I had to correct the same thing twice, it became a rule.
- AugA PC held three days of unpushed work that no other machine had.
- AugAn agent copied a panel feature without what it depended on. I reported three bugs with one cause.
- OctAn agent opened in a synced folder and read an old copy of the rules.
- OctTwo lock-tool runs overwrote each other in 3 of 5 tests, and both said "success".
- Push every change right awayNever force-push. A conflict in someone else's folder means stop.
- One feature, one copy of the codeFind the existing one and reuse it.
- Not tested means not doneSay what wasn't checked.
- Missing permission means stopDon't switch to a stronger key.
- Passwords stay in their filesNever in code, logs or chat.
- One name per machine"The old MacBook" means one computer only.