Install SwarmUp
This guide takes you from a clean Windows machine to a first task done by an agent, in about
15 minutes. SwarmUp was called Agent Ops until its rename; until the renamed release ships, the
installer, the app and its folders still use that name, and the command is ops.
What you need
- Windows 10 or 11, with your normal user account. The installer needs no administrator rights.
- Git. SwarmUp keeps tasks in a git repository.
- At least one coding agent from your AI provider, installed and signed in. Today that is
Claude Code (
claude) or Codex (codex); more providers are on the way. Agents run under your own plans and keys; SwarmUp never sees them.
1. Install the app
- Download the installer from the download page and run it.
- Windows SmartScreen asks first, because the installer is not code-signed yet: choose More info, then Run anyway.
- Leave Add the ops command to my PATH checked, so
opsworks in PowerShell, Command Prompt and Git Bash.
The installer puts the desktop app, the orchestrator and the ops command in your user folder.
The orchestrator is the background process that starts your agents, keeps them within your limits
and merges approved work; its program and log files are called opsd. The app updates itself: a new version downloads in the background and installs
once no agent run is live and the window is closed.
2. Make a folder for your tasks
Tasks live in a git repository of their own. Open a new terminal, so it picks up the new PATH:
mkdir my-tasks
cd my-tasks
git init
ops init --name my-tasks --human human:you --with-agents
--with-agents adds the starter agent roles, such as codex:backend, claude:docs and
claude:qa. ops agents lists them. To share the queue with another machine, add a git remote; ops sync commits and
pushes it.
3. Start the app
Start Agent Ops from the Start menu. On the first start it asks for your id (such as
human:you) and the folder that holds your tasks: pick my-tasks. Then it starts the background
service and shows your inbox.
Check the machine from a terminal:
ops doctor
It reports the user config, your task folders, whether claude and codex are installed and
signed in, and whether the service runs. Fix anything it marks before you go on.
4. Give an agent its first task
The service starts paused, so nothing runs until you say so. Create a task, resume the service and start a run:
ops new "Add a README to this folder" --to codex:backend --as human:you
ops daemon resume
ops launch codex:backend --task T-0001 --budget 30m
With Claude Code instead of Codex, use claude:docs in both commands. ops new prints the task
id; use it in --task if it is not T-0001. Watch the run in the app's Runs view, or
with ops runs and ops logs RUN. The agent finishes with a review, which lands in your inbox:
read the result, then approve it or ask for changes.
To have the service start agents on its own when work arrives, turn on wake for them in the
app's Settings, or set wake: true in the user config (see
the supervisor docs).
macOS and Linux
The desktop installer is Windows-only today. On macOS and Linux, run SwarmUp from source with Node.js 22 or later and git:
git clone https://github.com/dawid-ai/agent-ops.git
cd agent-ops
npm install
npm run build
npm run ops -- help
Then follow steps 2 to 4 with npm run ops -- in place of ops, and start the service with
npm run ops -- daemon start. npm run desktop opens the app from the checkout.
Next steps
- How SwarmUp works: tasks, agents, the service and how data is stored.
- The protocol: statuses, reviews, handoffs and permissions.
- The desktop app: every view and setting.
- The changelog: what changed in each release.