Docs
Agent tools
Every session's agent gets a few tools from Slashcode: it can see your other sessions, write to them, start new ones and wait for them, tell you something, and manage automations. One agent can then run a whole job across several sessions.
The slashcode tools
When a session opens, the computer hands its agent an MCP server named slashcode, over ACP. There is nothing to install or configure.
| Tool | What it does |
|---|---|
list_sessions | Your other sessions, on this computer and on your other computers that are online: id, title, agent, folder, branch, computer, and what each is doing. |
send_message | Sends one or several sessions a message, by id or exact title. Each gets it as a prompt of its own. |
start_session | Starts a new session on this computer with a task: agent, folder, branch, create_branch and title optional. |
wait_for | Waits until the sessions named have finished their turn or need you, then gives each one's status and last answer. |
notify_user | Tells you something now: a banner in the open apps, a notification otherwise. |
list_automations, read_automation, save_automation, delete_automation | Read, create, change and delete this computer's automations: a name, a schedule (days and a time, or every hour at a minute), the sessions to write to and the message. |
You do not call them yourself: ask the agent in plain words, and it picks the tool. Each call shows in the chat as a row of its own, such as Message sent to API, Started Fix #42 or Notified you.
Other sessions
A message arrives in the other session as a prompt, marked with the session and, from another computer, the computer it came from, and waits for the end of a turn in progress. Naming a session with @ in your own message tells the agent which session that is and how to reach it.
- A session sends at most 20 messages per turn, so that two agents answering each other stop. The count starts over at the next turn.
- A message to another computer needs it online and answering within 15 seconds; nothing is kept to be sent later. See sessions across computers.
- A message starting with
!is never run as a shell command: it reaches the agent as words.
Start and wait
start_session creates a session the way New session does and sends it the task. By default it uses the caller's agent and folder and works in the folder itself. With branch, it works in its own copy on that branch, following it when it is checked out elsewhere; with create_branch too, on a new branch made from the folder's current branch. It answers with the new session's id, title, folder and branch. It starts sessions on this computer only, within your plan's sessions.
wait_for waits 10 minutes by default, an hour at most. It answers, for each session, its status and the last message of its agent, up to 20,000 characters. A session still busy when the time is up comes back as still working, and the agent can wait again.
Notify you
notify_user takes a title and a message, for the outcome of a long job or a question only you can answer. An open app shows it as a banner; otherwise your phone gets a notification, whose preview is sealed for it alone. At most 10 per session per hour: past that, the tool fails.
What asks first
Listing, reading and waiting never ask. The rest is a permission request under the harness's mode, like an edit or a command:
| Tool | Request |
|---|---|
send_message | Send a message to other sessions |
start_session | Start a session |
notify_user | Notify you |
save_automation, delete_automation | Change automations |
None of them is a file edit, so edits still asks and only all lets them through. See permission modes.
Example: a master session
Start a session named Master in your repository, with Claude Code or Codex, and send it:
You are Master. Go through the open pull requests of this repository one by one. For each, read its comments and the issues it closes. If something is left to fix, start a session on its branch to fix it and wait for it. Then start a review session on that branch and wait for its report. Notify me with what was done and what is left, and move on to the next one.
For each pull request, it then:
- reads the pull request, its comments and the issues it closes with
gh, in its own shell; - calls
start_sessionwith the pull request'sbranchand what is left to fix: the fix runs in its own copy on that branch, and your folder stays as it is; - calls
wait_foron that session, and reads its answer; - calls
start_sessionagain on the samebranch, which the fix still holds, so the review session follows it in a copy of its own; it asks for a review without changes, and waits for it; - calls
notify_userwith the outcome, then moves on to the next pull request.
Each session it starts shows in your list like any other, grouped under the repository: open one to follow it or step in. Answer Start a session and Notify you as they come, or set the harness to all before you leave. To run it every morning, add an automation that sends Master the prompt each weekday.