You open Claude Code in several projects, launch subagents, leave tasks running… and lose track of who's doing
what. Habblaud turns all of that into an office you can take in at a glance: who's typing, who raised a hand
because they need you, who delivered their work and left, who went for a coffee while waiting for the next
instruction — and how much of each account you've already used in the 5-hour session and in the week.
And when two or more agents have nothing to do, the office gets a social life: each one has its own personality,
and they watch soccer together in the lounge, play video games and ping-pong, gossip in the kitchen, freshen up at the
mirror and bet coins on rock-paper-scissors. See Social life.
Everything runs on your machine, reading the files Claude Code itself already writes (plus only the alias lines in
your shell, to give each account its letter). Nothing leaves the computer: Habblaud doesn't read credentials or make
external calls.
Contents
What it looks like
Overview. The building has a lobby with elevators, a kitchen, restrooms and a lounge; each project with an open
session gets its own room along the hallway. At the top, the counters and each account's usage; on the left, the rooms
and agents; at the bottom, the activity feed.
The lights go out. When you close a project's last session, the last character walks to the light switch,
turns off the lights and leaves by elevator — and the room is taken apart, becoming a garden until a new project
arrives. If the garden ended up between two rooms, the farthest room moves there: it's set up in the empty spot,
everyone walks over to it, and the old address goes dark and is taken apart. That way the building has no gaps and
shrinks on its own.
| 1. The room is set up, still dark | 2. Someone turns on the lights and everyone works | 3. The last one leaves and turns off the lights | 4. The room becomes a garden |
|---|
| | | |
The images above use demo mode (made-up projects, people and accounts).
Installation
Requirements
- macOS (tested) or Linux.
- Claude Code installed, with one or more accounts (2.1.287 or newer for the mod).
- Node.js 22.12+ and npm (developed with Node 24; Docker already uses Node 24).
- Docker Desktop (or Docker Engine with Compose v2), if you're going to run it in a container.
1. Get the project
git clone https://github.com/marmottajr/habblaud.git
cd habblaud
npm install
npm install only downloads build tools (Vite, TypeScript, tsx…). The Habblaud server has no
runtime dependencies: it only uses Node's built-in modules.
2. Start Habblaud
Option A — Docker (recommended for keeping it always on)
npm run docker:up
The script detects your Claude Code accounts, mounts only the folders it needs (read-only), builds
the image and starts the container — which restarts on its own along with Docker. Open http://localhost:4747.
Option B — Node, without Docker
npm run build
npm start
Open http://localhost:4747. For development, use npm run dev (server + Vite with hot reload).
Now open Claude Code in any project and watch your agent arrive by elevator. 🎉
3. Install the Habblaud mod in Claude Code (recommended)
npm run mod:install # o mod e os plugins de permissões e de mensagens, em cada conta
npm run mod:install -- --sem-permissoes # sem responder permissões e perguntas pelo escritório
npm run mod:install -- --sem-mensagens # sem mandar mensagens aos agentes pelo escritório
Habblaud ships a mod (a plugin that runs inside
Claude Code) and installs it in each account, through claude plugin itself, from this folder. With it:
- each account's 5-hour and weekly usage shows up live in Habblaud;
- the terminal shows a line when another session needs you (permission or answer);
- the
/habblaud command becomes available in Claude Code;
- you can approve or deny permission requests from the office ("Do you want to…") and answer the agent's
questions, with the
habblaud-permissoes plugin (see Answering from the office);
- you can send messages to the agent from the office, as if you were typing in its terminal, with the
habblaud-mensagens plugin (see Sending messages).
This is the beginning of the README. Read the rest at the original. Read the full README ↗
