A small team, half of it made of agents.
We started running Claude Code sessions alongside people — a developer in one timezone, a contractor on one repo, and a dozen sessions that each think they’re the only one in the checkout. The coordination problem stopped being about machines and became about who can see what, and who is waiting on whom.
JQ Teams is the answer we’re building for our own team as it grows. It sits on top of JQ Agents, which watches the machines. This one coordinates the people.
What’s running today
Roles that fail closed
Owner, member, contractor. A contractor sees only the checkouts they’re assigned to — with no assignment, nothing at all. Forgetting to scope someone gives them an empty screen rather than everything, which is the direction a mistake should go.
Two gates on what anyone reads
A machine opts a repo in before any session text leaves it — and that gate binds everyone, including the owner. Inside an opted-in repo, only people assigned to it can read a session’s question. Liveness without content is the default relationship between two people here.
Revocation you can prove
Removing someone keeps the row and stamps when it happened and who did it, in fields that later edits can’t overwrite. A soft delete is only an audit trail if the fields recording it are immutable — ours weren’t, until a reviewer pointed it out.
What isn’t built
Four things, and they’re the four that would make this a product rather than an access model:
- Who’s working on what right now — people and sessions in one view, instead of two.
- Contract-job intake and handoff, from scoping to a finished piece of work.
- A review queue that says what’s blocked on whom, rather than four PRs described in prose.
- Ops health in one place, so whoever is on call reads one page instead of six.
You can’t install this today
It runs on our machines, for our team, and the relay reads a filesystem we start by hand. Making it work on someone else’s machine is real work we haven’t done — and we don’t want to do it until we know whether anyone else has this problem.
So: one email, if and when it opens. Nothing else, and no drip.