Overview

Why Swarm

Swarm started as a side project, inspired by online poker, video games, technology, and consciousness.

When Claude Code came out, it teleported me back to when I used to play multiple tables of online poker: microdecision making under pressure, with real stakes.

I was inspired, but managing AI across my real day-to-day work exposed the problems Swarm was built to solve.

Problem 01

Fragmentation

Every project, terminal, machine, and session became another place to check.

The work was parallel, but my attention was still stuck in serial mode.

I had multiple devices, multiple projects, Git branches, markdown files, todos, and agent sessions spread everywhere. Each one had a piece of the truth, but none of them had the whole picture.

Each session had partial memory. Each machine had partial state. Each branch had partial progress.

With one machine and one agent, that is manageable.

With an army of agents, it becomes the bottleneck.

Problem 02

Concurrency

While it may seem simple on the surface, the depth of an agentic harness is incredible.

Just one session and you're already dealing with multiple state types, before you even factor in TUI or desktop.

Multiple agents are possible today, but real concurrency is not. The sessions are disconnected, the backend is not unified, and the burden of coordination falls back on the user.

I envision a future where thousands of agents are used daily, managed by AI, with a human in the loop. Current tools are too limited to allow real concurrency without forcing you to manage it yourself.

Problem 03

Vendor lock-in

Most AI tools keep the work inside their system.

You cannot fully control the prompts, tools, models, runtime, memory, or where the sessions live.

You are most powerful when you can use all of the AI vendors, not when you are locked into one platform.

The Missing Layer

Swarm's Answer

Agents need a shared place to work.

Swarm starts local. Your desktop, TUI, projects, workspaces, and sessions can all live together on the machine you already use.

Then your swarm can grow.

Add containers. Add more agents. Add more projects. Keep long-running sessions alive. Move from one local machine into a real agent runtime that can scale with efficient compute.

Your sessions, background agents, tools, permissions, workspaces, Git worktrees, and flows stay in one coherent place as the swarm grows.

Start local.

Grow into containers.

Run always-on.

Scale with efficient compute.