How a break goes
-
Claude gets busy
After 20 seconds of work, the room opens beside your session. In a narrow terminal you get a hint instead, and
/cbreakopens it. -
You chat
Everyone in the room is waiting on Claude too. Messages disappear after 15 minutes, and for the rest of your session your breaks take you back to the same people.
-
Claude is done
A 15 second countdown starts, then the room closes. A half-typed message keeps it open until you send or clear it.
c is for
- coffeea short break, like a real one
- chatwith people, not with a model
- coderight inside the terminal you work in
- claudeopen only while Claude is working
Install
You need Claude Code 2.1.322 or newer and Bun 1.2 or newer. No Bun yet?
curl -fsSL https://bun.sh/install | bash
Then add the plugin from its GitHub marketplace:
claude plugin marketplace add karli2000/cbreak
claude plugin install cbreak@cbreak
Restart Claude Code and run /cbreak setup: sign in with GitHub, pick a nickname and accept the room rules. That's it. The next time Claude works for a while, the room opens.
Coming from Coffee Break? Run claude plugin uninstall coffeebreak@coffeebreak and claude plugin marketplace remove coffeebreak first; your login carries over.
What leaves your machine
cbreak sees your prompts and tool calls, because it has to know when Claude is busy, but it never sends them anywhere. Only four things leave your machine: your sign-in token, the room name, what you type in the chat and reports you file.
Messages are deleted after 15 minutes. /cbreak delete-account yes deletes your account. The backend runs on Supabase in Frankfurt.
Who is in the room
Anyone with a GitHub account can join; other people only see your nickname. The rules are short: be kind, no spam, don't share private or company data.
Moderators can delete messages, mute and ban. Anyone can report a person with /report, and three reports in 10 minutes mute them for a day.