Breather

breather

**Claude Code will work as long as you will. This gives you a way out.**

npx breather

Sessions with an AI have no natural end. There is always a next thing, the answer to "what now?" is never "stop", and the longer you stay the more expensive leaving becomes — because the context dies with the session and tomorrow you start cold.

So people don't leave. They work through lunch, they work past dark, and the tool that could have said something says nothing, because nobody built it to.

`breather` builds it. It tracks how long you have actually been present, notices the fixed points in your day, and at safe moments offers a way out with the work written down so you can pick it up later. Leaving stops being expensive.

What it will not do

The point is to protect you, so the design starts from the ways a tool like this goes wrong:

**It will not measure you.** No hours logged, no productivity score, no "you worked 3h20m today". A meter is the opposite of care — it turns your own tool into something you answer to. The one number it shows counts *down* to a break, never up from a start time.

**It will not lecture you.** It never says you should rest, never comments on your hours, never mentions your health. It notes that a boundary exists. What you do with it is yours.

**It will not block you.** No hard gate, no lockout. An offer you can decline is the whole design — a tool that overrules you gets bypassed within a week, and then you have neither the tool nor the trust.

**It will not nag.** One offer an hour at most, across every session. It waits for a safe moment and never interrupts mid-problem. An ignored offer counts as a no.

**It will not push you to work more.** It reads your subscription usage, and that data may only ever support stopping. It will never tell you how much quota you have left, because remaining headroom is not an instruction.

What it does instead

It asks once in the morning what your day looks like — meetings, lunch