agor

Agor

Multiplayer AI. Work together again.

Agor brings your team and agents together on live spatial boards where you can see the work, collaborate, and learn from each other. Raise AI teammates with memory, shared knowledge, skills, and connections to your tools, then bring them where your team works. What works for one person becomes something the whole team can build on.

Under the hood, Agor is a web workspace for running coding agents (Claude Code, Codex, Gemini, and others) on isolated git branches, each with its own dev environment and conversation history. Install it with npm and start on your own in a few minutes, then bring your team in.

Documentation · Quick Start · Agor Cloud Open Beta · Architecture · Contributing

---

Built on the agent CLIs & SDKs you already use

Agor ships no model of its own. It drives the coding-agent CLIs and SDKs you already run, interchangeable per session. Bring your own provider and subscription, with no vendor lock-in. Compare the harnesses →

The board: your team and agents in one place, with branches as cards, zones as regions, and sessions you can follow live.

▶ Watch the unscripted demo on YouTube (13 min)

---

Why Agor

Most teams are getting better at AI one person at a time. Good prompts sit in private chats, useful workflows live in one person's setup, and running more agents means more to keep track of. Agor makes AI work a team activity.

Bring your team and agents together

• See and join each other's work. Live cursors, comments, and shared sessions let colleagues follow an agent's progress and step in, instead of reconstructing it from screenshots and status messages.
• Learn from each other. See how colleagues prompt, share context, and turn the practices that work into prompts and workflows the whole team can reuse.
• Start solo, expand when ready. One person can install Agor and get value on day one, then bring colleagues in.

See the work and shape it together

• A live spatial board. Organize branches and agent sessions on a 2D canvas. Zones give the work structure, show its stage, and can fire a templated prompt when a branch is dropped in.
• Branches as the anchor. Every piece of work is a git branch with its own working directory, dev environment, conversation history, and PR.
• Shared dev environments. A one-click dev server per branch, with ports assigned automatically so parallel branches never collide and anyone can inspect the result.
• Rich sessions and session trees. Structured tool output, model and effort selectors, and fork/spawn genealogy for exploring alternatives or coordinating specialist agents.
• Multi-runtime. Claude Code, Codex, Gemini, OpenCode, Copilot, and Cursor (beta) are interchangeable per session.

Raise AI teammates

• Memory and shared knowledge. Each teammate gets a Knowledge-base namespace for durable, searchable context that the team and other teammates can build on.
• Skills and MCP. Capture repeatable ways of working as skills, and connect teammates to the tools your team uses. Agor also exposes itself over MCP, so agents can fork, spawn, schedule, and report on their own work.
• Where your team works. Reach teammates through gateway channels such as Slack and GitHub. Nobody has to live on the board to benefit.
• Schedules. Run standups, audits, digests, and other recurring work without a fresh prompt each time.

Know what's running, what it costs, and who can do what

• Governance and observability. Branch-scoped RBAC, per-user credentials and env vars, and per-prompt token and dollar accounting with durable history across sessions.
• Self-hosted or managed. Run Agor on your own infrastructure with your repos and database (LibSQL or Postgres) and explicit execution modes (trusted local, fail-closed sandbox, or delegated external execution). Prefer not to run it yourself? See Agor Cloud Open Beta.

---

Quick Start

Requires Node.js ≥ 22.12 (install) and Git on PATH. HTTPS remotes also require a working system CA trust store; SSH remotes require an SSH client and configured keys or agent access.

npm install -g agor-live

agor init           # creates config/database and installs the tools you select
agor daemon start   # runs the daemon in the background
agor open           # opens the web UI

Use agor install later to change or repair the selected agentic tools; it does not initialize or recreate Agor.

That's it. The onboarding wizard creates your first board and helps you raise your first AI teammate, which takes it from there.

The Getting Started guide walks through the wizard and includes a Docker Compose path if you would rather not install Node. For source builds, Postgres, and team setups, see Extended Installation. For managed hosting, see Agor Cloud Open Beta.

---

Core Concepts

Agor is built on three foundational entities. Everything else builds on these:

• Branches: the unit of work. A first-class git working directory on its own branch, with an isolated dev environment and its own conversations. Conventionally 1 branch = 1 feature/PR.
• Sessions & Trees: agent conversations with genealogy. Fork to explore alternatives (copies context), spawn subsessions for focused subtasks (fresh context window).
• Boards & Zones: a live 2D canvas of branches and sessions. Drop a branch into a zone to fire a templated prompt.

Read the Features Overview →

---

Key Capabilities

Multiplayer & Social	Live cursors, facepiles, spatial comments, and a shared multiplayer terminal, so the team can follow and join agent work.
Boards & Zones	A live spatial board for organizing branches and sessions. Zones show the stage of the work and trigger reusable prompts.
Teammates	Persistent AI teammates, each with its own Knowledge-base namespace for durable, searchable memory. Taught conversationally, then equipped with skills, MCP tools, gateway channels, and schedules.
Knowledge	A shared, searchable markdown knowledge base. One place for decisions, runbooks, prompts, and agent memory.
Message Gateway	Work with teammates from Slack and GitHub, without opening the board.
Scheduler	Cron-style triggers for templated prompts. Powers teammate heartbeats, standups, and automated audits.
Agor MCP Server	Agor exposes itself over MCP. Agents introspect sessions, branches, and boards, and drive the system themselves.
Rich Chat UX	Per-prompt token and dollar accounting, model/effort selectors, structured tool blocks, completion chimes.
Environments	One-click dev servers per branch with automatically managed unique ports, so the team can inspect the same running build.
Artifacts	Live, interactive apps (dashboards, mockups, tools) rendered directly on the board.
Security & RBAC	Branch-scoped permission tiers, per-user credentials and env vars, and explicit execution modes (simple / sandbox / delegated).
Cards (Beta)	Generic workflow entities for non-code workflows.

---

Screenshots

---

Architecture

graph TB
    subgraph Clients
        CLI["CLI (oclif)"]
        UI["Web UI (React)"]
    end

    Client["Feathers Client<br/>REST + WebSocket"]

    subgraph "Agor Daemon"
        Feathers["FeathersJS Server"]
        MCP["MCP HTTP Endpoint<br/>POST /mcp + Bearer auth"]
        Services["Services<br/>Sessions, Tasks, Messages<br/>Boards, Branches, Repos"]
        ORM["Drizzle ORM"]
    end

    subgraph Executor["Executor (process-isolated)"]
        AgentSDKs["Agent SDKs<br/>Claude · Codex · Gemini · OpenCode"]
    end

    subgraph Storage
        DB[("LibSQL / Postgres<br/>~/.agor/agor.db")]
        Git["Git Branches<br/>~/.agor/worktrees/"]
        Config["Config<br/>~/.agor/config.yaml"]
    end

    CLI --> Client
    UI --> Client
    Client <-->|REST + WebSocket| Feathers

    Feathers --> Services
    Feathers --> MCP
    MCP --> Services
    Services --> ORM
    Services --> Executor
    Executor -.->|JSON-RPC 2.0| MCP

    ORM --> DB
    Services --> Git
    Services --> Config

The daemon (apps/agor-daemon, FeathersJS) owns the database, services, WebSocket events, and the MCP HTTP endpoint. The executor (packages/executor) is a process-isolated runtime that spawns agents via their SDKs locally, inside the filesystem sandbox, or through a delegated external substrate. Shared types, the Drizzle schema, and git utilities live in @agor/core (packages/core).

Full Architecture Guide →

Repository layout

agor/
├── apps/
│   ├── agor-daemon/   # FeathersJS backend (REST + WebSocket + MCP)
│   ├── agor-ui/       # React UI (Ant Design + React Flow)
│   ├── agor-cli/      # oclif CLI
│   └── agor-docs/     # Docs site (Nextra), the canonical reference, published at agor.live
├── packages/
│   ├── core/          # @agor/core: types, db (Drizzle), git, api
│   └── executor/      # Process-isolated agent runtime
└── context/           # Agent-oriented cheat sheets and design docs

---

Development

The fastest path to a running dev instance from source:

git clone https://github.com/preset-io/agor
cd agor
docker compose up
# Visit http://localhost:5173 → login: [email protected] / admin

Prefer running locally without Docker? The two-process workflow (daemon in watch mode + UI dev server) and the .agor.yml variants (sqlite / postgres / rich / HA / docs) are documented in the Development Guide. It also covers running Agor inside Agor for dogfooding.

See CONTRIBUTING.md for the contribution workflow, and CLAUDE.md for the agent-oriented map of the codebase.

---

✨ Pledge ✨

⭐️ I pledge to fix a GitHub issue for every star Agor gets :)

---

Community

• Discord: support and discussion
• GitHub Discussions: questions and ideas
• GitHub Issues: bugs and feature requests

License

Business Source License 1.1 (BUSL-1.1). Agor is source-available, not open source, before the Change Date.

The Additional Use Grant permits production use, including internal and self-hosted commercial use. It does not permit commercializing Agor itself by offering its agent-orchestration functionality to third parties as a product or service, whether hosted, managed, or bundled for customers to operate. Consulting, support, integration, modification, use within a broader product or service, and single-customer internal deployments remain permitted subject to the license terms. Contact Preset, Inc. about alternative commercial licensing.

On January 15, 2029, or the fourth anniversary of the first public BSL distribution of a particular version (whichever comes first), that version converts to the Apache License 2.0. The license text controls if this summary differs from it.

About

Heavily prompted by @mistercrunch (Preset, Apache Superset, Apache Airflow), built by an army of Claudes and Codexes.

Read more: Announcing Agor Cloud Open Beta · Agent Modeling 101 · Raise a team helper agent in an afternoon · all posts →