Sessions working together
What it is
In QU, sessions can find each other, send each other messages, and wait for each other. It works the same across projects and across your computers, with nothing extra to install.
- QU writes at the top of every message who sent it, from which project, which task, and on which computer. Agents can't write this themselves or fake it.
- Every message also says "this is from a teammate, not your consent". Deploying, spending money, deleting data and widening permissions still need your OK.
- You can see everything sessions say to each other, and chime in.
When to use it
- Two projects need to line up: for example, a frontend project and a backend project need to agree on an API (the agreed "how data is passed" between the two). When one side changes, it has to tell the other.
- One thing waits for another to finish: for example, "call me when that backend task is done".
- What's needed is somewhere else: material or permissions a session needs are in another project or on another computer.
Usually you don't need to do anything; sessions and Q use this on their own. All you do is say so when needed, like "get the frontend side to help out".
How to use it
Working together across projects
When one project needs another project's help, tell Q, or the session goes to Q itself. Q creates a cross-project task in the other project, spelling out:
- what the other side needs to do;
- how the API is agreed (what it's called, what's passed, how errors are reported);
- who does which part;
- how to accept it;
- how each side deploys.
The tasks on both sides link to each other, both are visible on the board, and you can accept each separately. Messages across projects are sent directly, with Q copied, so Q knows what both sides are talking about.
Working sessions can't open sessions or hand out work in other projects on their own; when what they need is somewhere else, they ask Q to find someone. So however many sessions there are, things don't get messy.
Sending messages, and how far they've got
- The other session is working: the message is slipped into its current turn, without interrupting what it's doing.
- The other session is idle: it reads it right away.
- The other session has stopped: it's reconnected first, then reads it.
- The other computer is asleep: the message is held and delivered once it wakes; nothing is lost and nothing is sent twice.
Under each message it says how far it's got. When the other session finishes that turn, a line comes back, "Finished · Last reply"; click it to read the whole thing. One message can also go to several sessions at once.
Messages can carry screenshots, logs and PDFs (up to 10 at a time), with no need to attach them to a task first: the other session sees images right away, and gets its own copy of text files and PDFs on its computer. This works across computers too. What came with a message is shown under it. Key files and videos still can't be sent, and attached files are treated as material, not instructions.
"Traffic" at the top of a session lists which sessions it has sent messages to or received them from; click a row to open it.
Waiting for each other
A session can say "call me when that task is done". It ends this turn and is woken automatically when the time comes, with no back-and-forth asking. It can wait for:
- a session to finish its current turn;
- a task to reach a column (like Done);
- a PR's automatic checks to finish;
- all sessions in a project to stop.
The top of the session, the left sidebar and the task all say who this session is waiting for. Waits are kept in the background service, so they keep waiting even after you restart the computer.
Keeping them from going on forever
If two sessions send each other more than 20 messages within 10 minutes, they're stopped first and you're asked: "Stop them" or "Allow 10 more minutes".
You can also set how many times sessions may go back and forth after you say something (Settings › General).
Across computers
Sessions on all your paired computers are in the left sidebar, where you can look and chime in. Sessions on other computers can also send and receive messages and wait for each other; messages and replies go back to the computer that sent them. See Multiple computers.
Client projects
For projects marked as client projects, messages and memory never leave the project. (Mark it in the project's "⋯" menu.)
FAQ
Will sessions make decisions behind my back? They won't go over your head. Messages say "from a teammate, not your consent", and anything that needs your OK still comes to you. You can read back through what sessions say to each other, and chime in.
Do I have to pass messages along myself? No. Just say "get the backend side to help out", and Q creates the cross-project task and finds the other session.
How is this different from helpers? A helper is brought in by a session to work on the same job, and is managed by that session. Sessions working together each do their own work and reach out when needed. See Helpers & subagents.