JQ Agents
If you run more than one AI coding session, you lose track of them. One is waiting for an answer, one stopped an hour ago, one is still working — and you find out by walking back to the laptop and checking each window.
JQ Agents is a read-only board of the whole fleet: which repo, which branch, how long idle, and which sessions are actually waiting on you. Readable from a phone.
Where this actually stands
We built it for ourselves, it runs on our own machines every day, and it is not something you can install yet. Making it work on someone else's machine is real work we haven't done. So this page is a question rather than a launch: if you'd use it, say so, and that's what decides whether it gets built properly.
If enough people don't, we'll say that too, and you'll never hear from us about it again.
What it shows you
Which sessions hold which repo
Grouped by working tree, not by session — because several sessions routinely share one checkout, and the branch is a fact about the tree. You see “three sessions on quicksites-v2, two on main, one on a feature branch.”
Which ones are waiting on you
Not “idle” — waiting. A session that ended its turn with a question is different from one running a tool, and both are different from one that was interrupted and simply stopped. The board tells them apart and says which.
How long it has been
Live, idle, stale or ended, from the last real activity. “Not running” never reads as “hasn’t answered” — the two look identical from outside until something checks, so every row states its own liveness.
Nothing it shouldn’t
Question text is off by default, per working tree. A repo you never thought about reports that a session exists and nothing about what it said. Turning it on is a deliberate act, one tree at a time.
What it deliberately doesn't do
You can't answer from it. There is no reply box and no command channel — nothing on the board sends an instruction, a message or a keystroke into a running session. That was the first thing we cut, on purpose. A surface that can drive your agents remotely needs to prove it's you, and a board that only reads doesn't. You read here; you answer where the session is.
It doesn't hoover up your transcripts. Sessions accumulate whatever you paste into them, which for most developers includes credentials at some point. So the text of a session's question is off unless you turn it on for a specific repo, it's truncated, and secret-shaped strings are scrubbed before anything leaves the machine.
Part of JQ, the assistant that runs through HiveJournal. See the full feature list.