Notices when you're cooked before you do.

Tempo is a load-aware companion for people who work long hours with Claude — chat, Cowork, or Claude Code. It reads the shape of your session — never your words — and when the pattern says your nervous system has left the building, it offers exactly one thing: a 40-second reset, at a pause, never interrupting your work.

the whole product, in one late night
claude — ~/projects/app
tempo ● steady 9:40 pm
steady — nothing, ever elevated — glyph warms, still silent depleted — one line, at a seam, max 2/day
why it's different

On from minute one. Keeps receipts.

Tempo works immediately — retry spirals, marathon stretches, and late-night urgency are visible with zero training. And in Claude Code it also keeps measuring in the background, so every day it runs, analyze.py shows a richer picture from your own logs: what actually happens to your prompts and error rates after hour three. If your data ever says it isn't helping, it will show you that too — and you delete one folder. In chat and Cowork, the same rules ride along as a skill Claude applies itself.

Never interrupts

Hooks always exit 0. No modals, no stolen turns. Interventions exist only in seams — after a turn completes, never mid-agent.

Evidence, not vibes

Every offer cites the signal that earned it: "3 retries on the same test in 9 minutes." Max two a day. Declines silence it.

Resets that fit a terminal

20 nervous-system practices from The 40-Second Reset — breathwork, grounding, movement, fuel, reframes — rotated so it's never the same reset twice in a row. Compact card, breath-paced countdown, no streaks, no praise.

try it

Free beta. Two minutes. Every Claude surface.

Claude chat & Cowork

The Tempo skill teaches Claude itself to notice load signals — retry loops, terse rapid-fire messages, late hours — and offer a reset at a pause. Works in any conversation.

↓ download tempo.skill

Then in Claude: open Settings → Capabilities/Skills and add the file — or just attach it in a chat and ask Claude to save it as a skill. From then on: type /tempo, or let it notice on its own.

Claude Code (measured)

The full version, live from minute one: a statusline that warms as your session degrades, reset offers when the signals earn one, and silent local measurement that turns into your own data story over time.

↓ download tempo-beta.zip

Install steps below.

  1. Unzip, then: bash tempo/install.sh — that's the whole install. It backs up your Claude settings before touching them.
  2. Open your next Claude Code session. The tempo ● statusline is live immediately.
  3. Any time after: python3 ~/.tempo/week.py — your week in tempo: best hour, worst hour, and whether resets measurably helped, from your own logs. Pause everything with rm ~/.tempo/enabled.

Want a preview first? python3 tempo/demo.py plays the whole product in a sandbox on synthetic data, right now.

privacy

What it never stores

No prompt text. No file contents. No paths. No command strings. No tool outputs. Tempo logs derived shapes only — word counts, error flags, salted hashes — to a plain-text file you can read (~/.tempo/events.jsonl). There is no network call anywhere in the codebase, no account, no telemetry. rm -rf ~/.tempo is a complete erasure. Open the source; it's short on purpose.

shape the roadmap

Tell us what you think

Two minutes. Every submission gets read by a human (Pen).