Repository navigation
Swarmed 0.1.0
The first release: a macOS app and a swarmed command over one Rust core. Swarmed is not signed
with an Apple Developer ID yet, so macOS asks before opening it the first time when it comes
through Homebrew or a browser.
Added
- A task is a branch in a worktree of its own. Add a git repository, say what you want done,
and Swarmed creates the branch and a worktree under~/swarmed/<project>/<task>, runs the
repository's setup hook, and starts an agent there. Nothing is written into the repository
itself. - Any agent. Claude Code runs with its own login and configuration; Codex, OpenCode,
Antigravity and any agent that speaks the Agent Client Protocol are set up from Settings →
Agents or inagents.toml. Swarmed never signs you in to an agent and keeps no GitHub token: it
uses each agent's own login and yourgh. A new session's agent can be picked until its first
message, and a conversation can be cloned onto another agent. - The conversation. Replies stream as they are written, with syntax highlighting, and HTML an
agent hands over is shown in a sandbox on an origin of its own. The transcript says what the
agent is doing and how long each turn took. Messages queue while the agent works; files can be
picked or dropped on the window; commands, skills and saved prompts are offered after a slash. - Supervision. Permission requests are answered in the conversation, and an agent's questions
by arrow keys, number or click. Auto mode, plan mode, the model and its effort are set per
session and can change mid-session. - Sessions. Rename them by hand or by a model, fork one from any message into a new session
that holds that message and what followed, close, archive, reopen or delete them, and search
what was said in any of them. Unread answers are marked, and notifications and a count on the
Dock icon say when a session needs you, finishes or fails; ⌘I lists everything that waits. - Sessions working together. Agents get tools to see, read, message, start and close other
sessions, and spawned sessions are listed under the one that started them. Claude Code's
sub-agents appear under their session while they work. One prompt can go to several agents at
once, and work can be handed to a Codex cloud agent or a Claude Code cloud session: from a
session too, as a brief its agent writes or with the whole conversation. - The task panel. Changed files with their diffs, comments on lines sent to a session, a Files
tab, commit with a message the session's agent writes, push, and a pull request whose title and
description are written for you, with its checks summed up in a line that unfolds into the list,
failures first. Two tasks' changes can be compared, and a worktree opened in the editor, the
browser or the terminal application. - A terminal in each session, whose output the agent sees, configured in JSON; processes a
task's agents left running are listed and can be stopped. - Environments. Named environments per repository with their ports and variables, a start
command that keeps running beside the setup hook, and snapshots of the files git ignores, so a
new task starts set up like an earlier one. - One pool of MCP servers and skills. The servers configured for Claude Code (its plugins'
too), Codex and OpenCode, and Swarmed's own, go to every agent that lacks one by that name, read
when a session starts (a repository's own.mcp.jsononly once approved in Claude Code); skills from every agent and from the task's repository likewise. - Your own setup. Rules every agent is given, notes on a repository and on a task, actions of
your own, a status line from built-in pieces or a script, keyboard shortcuts, and API keys kept
in the macOS Keychain for agents that need them. Agents can propose configuration changes;
rules, environments and commands change only after your yes. - Looks. Six colour palettes, Swarm among them with its own words and marks, the classic,
senior and custom layouts, and the text size. - What it costs. What the agents report their work cost, by day and by task; turns by day and
model in charts; and what Swarmed takes up on disk and is using right now. - About, and a menu bar of its own. Swarmed's menu has About, Settings and Keyboard
Shortcuts. The About view, also in Settings and behind the version in the sidebar's top corner,
says what Swarmed is and which version is installed, and links to its source. - The
swarmedcommand for repositories, tasks, sessions, agents, keys and snapshots from a
terminal.SWARMED_FAKE_AGENT=1swaps in a scripted agent that spends no tokens. - Installing: an install script, a Homebrew cask that also puts
swarmedon the PATH, and
cargo install swarmedfor the command alone.