Getting started
Introduction
voodoo runs Claude Code, Codex and shells from one terminal, keeps them running when you close it, and tells you which of them needs you.
Start three agents in three tabs and within five minutes you don’t know which one is waiting on a permission prompt, which one finished, and which is still thinking. So you tab through all three and read the screens, every time. voodoo replaces the reading with a list and a colour.
How it fits together
One binary, voodoo. It plays three parts.
- The terminal UI. Plain
voodoo. Your projects, the sessions in them, and the live terminal of the one under the cursor. See the terminal UI. - The daemon. It owns every session’s terminal, so closing a window ends nothing.
voodoostarts it when it needs it. See the daemon. - The commands.
voodoo add,voodoo statusand the rest, for a shell or a script. See commands.
What you need
| Need | Why |
|---|---|
| macOS or Linux | The two systems voodoo is built and tested on. |
| claude or codex | On your PATH, for agent sessions. A shell session needs neither. |
| git | For worktrees. A project that isn’t a git checkout still works, without them. |
Start here
Build it, then run your first session. Keep the leader’s keys close. Before you lean on it, read what it doesn’t do yet.
Credit
The process model, the numbered scrollback, and hook-driven status follow ideas from Nebula. The code here is its own. Charted by tin0d0.