Guide
How to run multiple Claude Code sessions at once and keep track of them
Two or three Claude Code sessions at once is a real speed-up: one refactors, one writes tests, one explores. The cost is attention. Each window might be waiting on you, and you only find out when you look. The fix is one place that shows them all.
What goes wrong with several sessions
- You do not know which window is waiting, so you check them all.
- A permission request sits unanswered while you work in another chat.
- You forget which chat is for which project.
Keeping track with Herdbell
The Sessions page has a Live tab and a History tab, with search and a filter per agent, so older chats are easy to find again.
- Open Herdbell with your shortcut. Every chat is listed with its agent, project, status and how long it has been working.
- The status is a colour: working, needs permission, has a question, finished, or error. The pointer glows the same colour when something needs you.
- Pick a chat to see everything it did, answer it, or press Open to jump to its window or app.
Habits that make several sessions easier
- Give each session its own project folder (or a separate git worktree) so changes do not collide.
- Name the job in your first message, so the chat title tells you what it is.
- Answer permission requests as they glow instead of letting them pile up.
Common questions
How many Claude Code sessions can Herdbell track?
Herdbell lists every chat your connected agents report, so you can run as many sessions as your machine and plan allow.
Does it work if the sessions are in different terminals?
Yes. Herdbell listens through the agent's own hooks, not through a terminal, so it does not matter which terminal or app each chat runs in.