Notes on working long hours with Claude
Two kinds of writing. What happens to people over a long agentic session — and how the machinery underneath Claude Code actually works, since that is what Tempo is built out of. No newsletter, no popup; if something here is useful, it is useful on its own.
AI coding fatigue: why hour six with Claude feels different
Agentic coding removed the compiles, the waits and the walls that used to break up a working day, and shifted the work from producing to judging. Why a productive day can leave you emptier than an unproductive one, and what to do at hour six.
patternThe retry spiral, and how to notice you're in one
Three retries on the same test in nine minutes is not persistence. It is a recognisable state with a measurable signature and an exit that feels like losing — which is why nobody takes it.
practiceWhat a 40-second nervous-system reset actually is
Not meditation, not a wellness break, no streaks. The five families of practice, three you can do at your desk right now, and why the length is the entire design.
guideBuilding a Claude Code statusline worth looking at
How the statusLine setting works, what the payload on stdin gives you,
what earns a place on one line, and how to compose with a statusline you already have
instead of clobbering it.
Claude Code hooks: the ones that actually matter
Every event and what it is good for, why exit code 2 will ruin your afternoon, why plain stdout is not a way to talk to the user, and the pattern for observing a session without interrupting it.
The product these came out of
Tempo is a load-aware companion for people who work long hours with Claude. It reads the shape of your session — never your words — warms a glyph in your statusline as load rises, and at the top of the scale offers one 40-second reset in a seam, citing the signal that earned it. Fully local: no account, no telemetry, no network calls anywhere in the codebase.
free while in betamacOS · Linux · WSLno account