Concepts
Jobs
A job is one conversation with one agent in one space. Choose how much the agent may do on its own, answer its questions, and fork it to try another way.
Starting a job
Press New job in a space. Choose an agent, a model, a permission mode and a working folder (/work by default), then write your message. You can attach files. The agents listed are the ones installed in this space. If you have not signed in to one, the page shows Sign in to use.
A job belongs to the person who started it, or to the person an automation runs as. Everyone in the space can read it, but only its owner can reply to it. If you want to continue someone else's job, fork it (for now this works on pi jobs only).
What a job is doing
The job list says in words what each job is doing: Queued, Starting, Running, Needs you (it is waiting for your answer), Done (ready for your next message), Interrupted or Failed. By default a space runs up to four jobs at once. The rest wait their turn, and the job says how many are in line.
While an agent is working, you can send another message. pi, Claude Code and Codex take it at once. The other agents take it as the next turn, and the job says so. Stop ends the current turn and leaves the job idle. Archive hides a job. Delete removes it and its files after asking, and only space admins can use it.
If TurnPanel or the space restarts mid-turn, the job is marked interrupted. Send a message to continue it.
Permission modes
Each agent has its own permission modes. Claude Code has Ask first, Accept edits, Plan only and Never ask. Codex has Ask first, Ask when unsure and Never ask. OpenCode and Cursor have Ask first, Plan only and Never ask. Grok Build has Ask first and Auto. Each space chooses the mode its agents start in, and Ask first is the default. When you start a job you can pick another mode, and you can change a running job's mode from its composer. pi, Claude Code and Cursor switch at once. Codex, OpenCode and Grok Build switch from the next turn.
A mode that acts without asking is marked in the warning colour, and TurnPanel asks you once before you switch to it. pi has two modes: Ask first, and Automatic, which acts without asking. Only the job's owner or a space admin can change its mode, and an agent cannot widen its own permissions.
Approvals and questions
When an agent wants to do something its mode does not allow, or needs to ask you something, the job shows Needs you. The space's tile gets a dot, and you get a notification. A job can wait for you as long as it needs to.
For an approval you choose Allow once or Reject. Claude Code also offers Always allow, and Codex offers Allow for this session. pi and the other agents offer only Allow once and Reject. Only the job's owner can answer. For a job that runs as the space, the space's admins answer. An approval that involves your own logins can be answered only by you.
Edit, retry and fork
On a pi job you can edit an earlier message and run again from there, retry a turn, or delete a message and everything after it. History is never rewritten: the transcript just leaves out what you rewound.
Fork starts a new job from an earlier point, or from the whole conversation. It leaves the original untouched and makes you the owner of the new one. Other agents cannot rewind or fork yet, so for them these actions are not offered. Start a new job instead.
Finding jobs
Press Ctrl+K (Cmd+K on a Mac) to search all your jobs across spaces by title and message text. The Recent jobs column on the right lists the newest activity from every space you can reach.