Skip to content

The swarmed command

The command drives the same core as the app, on the same data, from a terminal or a script. swarmed help <command> has every argument; this page is the map.

Command What it does
project add, list and remove repositories; project config prints the path of a project’s config file
task create and remove tasks, rerun setup, run the start command, see changes, commit, push, open a pull request
session run, continue, list, show, fork, rename, mark, close, reopen and delete sessions; change a session’s model or supervision
environment list a project’s environments
snapshot keep the files git ignores in a set-up task, for new tasks to start from
agents, agent list the agents sessions can run on; install and configure the others
key store, remove or list API keys for agents other than Claude Code
mcp, skills list the MCP servers and skills agents are given
rules print or replace the rules every agent is given
note print or replace the note on a project or a task
action manage the buttons of your own that send a prompt or run a command
cloud hand a prompt to a Codex cloud agent or a Claude Code cloud session and list what was handed over; print or apply a Codex task’s changes
search find the sessions where something was said
costs, analytics, usage what agents report their work cost, turns by day and model, what Swarmed takes up
editor, auto-title, layout, terminal settings: the editor, naming sessions by a model, the custom layout, the terminal

session run and session send print the conversation as it happens and ask on the terminal when the agent wants permission ([y/N]). Ctrl-C stops the turn, not the session. They exit non-zero when the turn is stopped or fails, so a script can tell.

A session runs on Claude Code unless --agent names another (swarmed agents lists them). --ask, --auto and --plan choose how it is supervised; without one, the settings’ default applies.

Commands that take a secret or a long text, key set, note --set and rules --set, read it from standard input, so it stays out of the shell’s history.

The command and the app can run on the same data at once. Stacks the command starts are ended by it again: swarmed task new and swarmed task setup end the stack when they exit, and swarmed task start keeps one running in the foreground.

SWARMED_FAKE_AGENT=1 swaps in a scripted agent that spends no tokens, for trying a command or a script out.