Tempo

Notices when you're cooked before you do

2 followers

Notices when you're cooked before you do

2 followers

A load-aware companion for Claude — chat, Cowork, Claude in Chrome, and Claude Code. Tracks how long you have actually been in Claude, on from minute one, fully local, never interrupts your work.

Free

Launch tags:Productivity•Developer Tools•Artificial Intelligence

Launch Team

AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building

Promoted

Maker

📌

I built Tempo after one too many 1 am retry spirals where I couldn't tell my code was broken because I was broken. It's a free, local-first companion for people who work long hours with Claude (Code, Chat, Cowork. It reads the shape of your session — retry spirals, hours logged, late-night urgency — never the content of your prompts, code, or files. When the pattern says your nervous system has checked out, it offers exactly one thing: a 40-second reset, at a natural pause, never interrupting mid-task. Max two offers a day, and every offer cites the signal that earned it. Everything is local: no account, no telemetry, no network calls anywhere in the codebase. Free forever for the core. — Pen

Report

2mo ago

Forum Threads

p/tempo-11

•

2mo ago

What would make a break/reset reminder actually useful instead of annoying?

Every break-reminder feature I've tried eventually gets snoozed into oblivion mine included, in early builds. Curious what's actually worked for people, or what's made you turn a feature like this off entirely.

A few specific things I'm weighing right now:

p/tempo-11

•

2mo ago

Why I built Tempo (the 1am retry-spiral story)

A few months ago I was 40 minutes into a retry spiral on a bug that turned out to be three lines. Not because the bug was hard because it was 1am, I'd been at it for six hours straight, and I genuinely could not tell anymore that the thing that was broken was me, not the code.

I built Tempo for that specific moment. It's a free, local-first companion that reads the shape of your Claude session retry loops, hours logged, that particular late-night urgency and never the content of your prompts, code, or files. When the pattern says you've checked out, it offers exactly one thing: a 40-second reset, at a natural pause, never mid-task. Max two offers a day.

p/tempo-11

•

2mo ago

How Tempo tells you're cooked without ever reading your prompts or code

The question I get most from other devs when I describe Tempo is some version of "wait, so it's reading my code?" No and that was a hard constraint from day one, not a privacy-policy afterthought.

Tempo only ever looks at session metadata: how long you've been active, retry/error frequency, time of day, gaps and bursts in activity. It never touches prompt content, file contents, or output. There's no account to create and no network calls in the codebase at all you can check this yourself, it's not a claim you have to take on faith.

View all