Docs
CLI reference
Every slashcode command and option. On the computer, slashcode --help and slashcode <command> --help print the same.
Global options
| Option | What it does |
|---|---|
-V, --version | Prints the version. |
-h, --help | Prints help, for slashcode or any command. |
| Environment | What it does |
|---|---|
SLASHCODE_HOME | Where the daemon keeps its files. ~/.slashcode by default. |
RUST_LOG | How much the daemon logs: info by default, debug for more. |
$ RUST_LOG=debug slashcode daemonRun the daemon
| Command | What it does |
|---|---|
slashcode daemon | Runs the daemon in this terminal until you stop it. Also what slashcode alone does. |
slashcode service install | Installs the LaunchAgent and starts the daemon now and at every login; run it again to pick up a new binary or PATH. Restarts the daemon. |
slashcode service uninstall | Stops the daemon and removes the LaunchAgent. |
slashcode service status | Says whether the LaunchAgent is installed and the daemon running. |
service uses launchd, so it is macOS only; on Linux, run slashcode daemon.
$ slashcode service statusRunning (pid 4242).
Pair and manage devices
| Command | What it does |
|---|---|
slashcode pair | Shows a pairing code and its QR, valid 15 minutes for one device, and waits until it joins. |
slashcode devices | Lists the paired devices, online, offline or waiting for approval, with the account and the plan. |
slashcode devices approve <device-id> | Lets a device of your account use this computer. |
slashcode revoke <device-id> | Removes a paired device; it comes back only by pairing again. |
pair and devices approve need the daemon running. devices and revoke also work without it; a device revoked then is unlinked at the relay when the daemon next connects.
$ slashcode devices$ slashcode revoke 3f9a0c1d2e4b5a6978f0
Agents
| Command | What it does |
|---|---|
slashcode agents | Lists known harnesses and whether they are installed. Same as slashcode agent list and slashcode agent. |
slashcode agent add <id> [--name <name>] -- <command…> | Adds an ACP agent, or replaces a built-in one with the same id. The id is 1 to 32 lowercase letters, digits, - or _; the name defaults to the id. |
slashcode agent remove <id> | Removes an agent you added. Built-in ones cannot be removed. |
slashcode agent permissions <id> <ask|edits|all> | What this computer accepts without asking, for that agent's sessions. See permissions. |
Changes take effect in a running daemon at once.
$ slashcode agent add kimi --name "Kimi" -- kimi --acp$ slashcode agent permissions kimi edits
Switches
Each takes on or off, and prints the current state when given neither. The running daemon reads them without a restart.
| Command | What it does | Default |
|---|---|---|
slashcode shell [on|off] | Allows or forbids !command from paired devices. | off |
slashcode peers [on|off] | Takes or refuses messages from sessions on your other computers. | on |
slashcode incidents [on|off] | Sends this computer's errors and crashes to Slashcode. | on |
$ slashcode shellShell commands are off. `slashcode shell on` lets paired devices run `!command`.
One turn, and editors
| Command | What it does |
|---|---|
slashcode run [--agent <id>] [--cwd <dir>] <prompt> | Runs one turn on this computer and prints its events as JSON lines. A permission request waits for an option id on stdin. --agent defaults to claude. |
slashcode claude-acp | Serves the installed Claude Code as an ACP agent on stdin and stdout, for editors. |
$ slashcode run --agent codex --cwd ~/code/api "Run the tests and summarise"Files
Everything a computer keeps is in ~/.slashcode (or SLASHCODE_HOME), readable by you alone:
| File | What it holds |
|---|---|
key | The computer's identity key. |
slashcode.sqlite | Sessions and their history, devices, account and plan. |
logs/daemon.log | The daemon's log, capped at 10 MB with daemon.log.1. |
agents.json | The agents you added. |
permissions.json | Each agent's permission mode. |
keys/ | API keys given to agents from a device. |
automations.json | This computer's automations. |
worktrees/ | The copies sessions work in, one per session on a branch. |
uploads/ | Files sent in the chat, one folder per session, removed with it. |
shell-enabled, peers-off, incidents-off | The switches above: present or absent. |
control.sock | How these commands reach the running daemon. |
On macOS the service is ~/Library/LaunchAgents/dev.slashcode.daemon.plist, and what it prints before the log opens goes to daemon.log.