Docs

Using Slashcode

Everything happens in the chat: one per session, the same on the iPhone, the iPad and the web app. These pictures are drawn from the app's own interface.

Sessions

The list shows the sessions of every paired computer, grouped by computer, and the sessions of one repository together under its name. A ring turns around a session while its agent works, pulses when it waits for you, and a dot marks what you have not read yet. A session in a repository shows its branch.

New session asks for a computer, a harness and a folder and, in a git repository, a Branch: This folder, or a branch, existing or new, in its own copy. Long-press or right-click a session to rename it, give it a colour, or delete it. A session idle for 5 minutes has its harness stopped on the computer; the next message starts it again, with its history.

MacBook Pro · Claude, Codex, OpenCode

The chat

What you send sits on the right. The agent's answer arrives whole, once it is written, rather than token by token. Its tool calls fold into one pill per run, speaking for the latest call, with how many there were; open it to see each call and its output. Under the last row, a line says what the agent is doing: thinking, the file it reads, the command it runs.

The composer takes text, files of any kind (up to 8 per message) and, when the harness can see, pictures: paste, drop or the paperclip. Files land on the computer, where the agent opens them. Its model button switches the model, the effort and the mode the harness offers, even mid-session. While the agent works, the send button turns into stop; a message sent meanwhile waits for the end of the turn, or reaches Claude at once.

API · Claude Code

/ commands and @ mentions

Type / at the start of a message for the commands: the app's own (/model, /effort, /mode, /permissions) and the ones the harness brings, its skills and MCP prompts included.

Type @ to name another session, on this computer or another one. The message goes to the agent as written, and the agent is told which session that is and how to reach it: it can read its state and send it a message, as below.

Permissions

When an agent wants to edit a file or run a command, every paired device shows the question with the agent's own options, usually Allow, Always and Reject. The first answer wins, from any device; the card then folds away, and a refusal marks the tool it stopped.

To be asked less, let a harness accept edits or everything on a computer: harness permissions.

Relay · Codex

Subagents

When an agent launches subagents, they show as one row of faces, with how many are still working and for how long. Open it for a line each, then each one's own steps. Those still running also wait in a panel above the composer, whose Stop stops the turn and everything it started.

Sessions that talk

Every session knows the others: their name, their harness, their folder. Tell one agent to pass something on and it sends a message to the sessions you named; the row Message sent to … shows where it went, and each of them gets it as a prompt of its own, marked with who sent it.

This works across computers too: a session on your Mac Studio can write to one on your MacBook, through the relay, sealed end to end. A computer that should not take messages from the others turns it off:

$ slashcode peers off

An agent can also start sessions of its own, wait for them and notify you: see agent tools.

API → iOS app, Web

Changes and git

When the session's folder is a git repository, the panel button opens the git panel. Its Changes show what the last turn changed, what is not committed yet, or everything since the branch left its base, file by file with its diff. A finished turn also leaves a files changed row in the chat that opens on its own changes.

From the panel you commit, push and open a pull request, switch branches, and follow the repository's pull requests, their checks and reviews, and its issues, with gh installed and signed in on the computer. See Git and GitHub.

Web · fix/token-refresh

Shell commands

A message that starts with ! is not sent to the agent: the daemon runs it in the session's folder with your login shell, and shows it as an Execute tool with the end of its output. It is off by default, on each computer:

$ slashcode shell onShell commands are on: paired devices can run `!command` on this machine.