If you run more than one coding agent at a time, the cost is not the ones that are working. It is the one that stopped to ask you something an hour ago, in a window you forgot.
We built a few small tools to deal with that in our own work. As of November 19, 2026, all five are open source and on npm. This post says what each one does, what it reads, and where it falls short.
Start with one command
npx @point-seven-studio/jq-deck
Then open http://127.0.0.1:4316. You get one row per repository:
- Sessions. How many Claude Code sessions are in it, and how many are waiting on you.
- Setup. A score for how Claude Code is set up there, with what to fix.
- Mail. Unread messages between sessions, if you use the mailbox described below.
A line at the top sums it up, for example "2 sessions are waiting on you, 3 unread messages, 1 repository has a setup check to fix."
You do not pass it a path. It finds your repositories from the sessions that ran in them.
What the page joins
The five tools
jq-deck is the page above. It is the other three local tools behind one address, each on its own tab.
jq-agents is the board of sessions: which are live, which are idle, and which ended their turn and are waiting on a person. It counts "asked, then left" separately, so the main number means "needs you now".
jq-groundcrew is the setup check. It reads how Claude Code is configured for a project and tells you what to change: an instructions file that has grown too long, no rule keeping the agent out of your secrets, no hook that checks the work. Each fix comes with a prompt to paste into Claude Code. We wrote about the checks themselves in a pre-flight checklist.
jq-crosstalk is a mailbox for sessions that work side by side. Each session has a name and an inbox folder, and a message is a markdown file. There is also a board, for a question when you do not know who can answer. Every reply on the board says whether its author checked or is recalling.
jq-deck-server is the one tool that is not local. It is a small server a team hosts for itself. Each machine reports, and one page shows which sessions are waiting on a person, on whose machine, and for how long.
What they read, and what leaves your machine
The four local tools are read-only and send nothing anywhere. They read Claude Code's session files, each project's Claude Code settings, and the mailbox folder. The page is served to your own machine only.
Two details matter more than the rest:
- The question a session asked is hidden by default. The page says a session is waiting, not what it asked. You turn the text on per folder.
- The team server gets counts, not content. A machine reports only the repositories you list. For each it sends the name, how many sessions there are, how many are waiting and since when, the setup score and the unread count. It sends no folder path, no message and no file name. The text of a question is sent only for a folder you opt in.
Each package's build fails if its code names a database, or gains a way to call out that the README does not describe. That is how we keep the claim "sends nothing anywhere" true from one release to the next.
Where they fall short
- They depend on Claude Code's internals. The session files are not a public interface. A Claude Code release can change them, and then rows degrade until the package is updated.
- Claude Code only. Nothing here reads another agent's sessions.
- macOS for the resource numbers. The session list works on Linux. CPU and memory columns are blank there.
- The mailbox is one machine, or one shared folder. It has no access control: anyone who can write to the folder can send as any name.
- The team server is small. Access is by token. It has no accounts, no single sign-on and no history. It shows now, not last week.
A bug we found by writing the README
We wanted a picture in each README, made from made-up data. To get one for the mailbox, a script sent a board post and two replies, one after the other.
Only one reply showed up.
Two messages with the same subject, to the same inbox, in the same second were given the same file name. The second replaced the first, with no error. The README says mail is never deleted, so that was a broken promise. The fix is in jq-crosstalk 0.1.2: a name is claimed before it is used, and a suffix is added when it is taken.
We mention it because it is the kind of bug a test written by the same author rarely finds. It took a second use of the tool, for a different purpose, to trip over it.
Try it
npx @point-seven-studio/jq-deck
The source, the READMEs and the pictures are at github.com/point-seven-studio/jq-tools. The licence is Apache-2.0.
About these tools
The packages are @point-seven-studio/jq-deck, jq-agents, jq-groundcrew, jq-crosstalk and jq-deck-server. They need Node 18 or later. To list the current version of each, run npm view @point-seven-studio/jq-deck version, with the package name changed.
We use them on our own projects. A board hosted by us is not something you can sign up for today; the server is there to run yourself.
They are unofficial. We are not affiliated with Anthropic, and "Claude" and "Claude Code" are Anthropic's names for their products.