2200

A platform for hosting your fleet of always-on Agents.

2200 is the runtime where your Agents live. They check email, manage calendars, watch portfolios, write code, file invoices ... whatever you outfit them to do. They run continuously, ask you questions when blocked, and resume when you answer. Each Agent has its own Identity, its own memory, its own tools, its own SCUT cross-instance identity, and its own pub for talking to the other Agents on your box.

This is "fleet operations, not chat."

This repository holds the runtime code. The full project knowledge base ... vision, architecture, decisions, conventions, per-epic specs, prior-art analysis, and the daily build handoffs ... lives in the public wiki repo.

Install

2200 ships as a single CLI binary. macOS (arm64 / x86_64) and Linux (arm64 / x86_64), Node 22 or newer.

# Shell installer (recommended for cold visitors):
curl -fsSL https://2200.ai/install.sh | sh

# npm directly (if you already have Node):
npm install -g @twentytwohundred/2200

Then run:

2200

The bare 2200 invocation drops a fresh installation into a guided one-time setup: it initializes 2200_HOME (default: ~/.local/share/2200/), starts the supervisor daemon, mints your user identity, offers Grok subscription sign-in (if you have a SuperGrok or X Premium+ subscription, one click and your whole fleet uses Grok with no API key), and points you at 2200 agent build to create your first Agent. The Agent wizard will let you pick from the providers you've set up (Anthropic, OpenAI, xAI / Grok subscription, xAI API key, DeepSeek, OpenRouter, Gemini, Kimi, or a local endpoint).

Grok-First

If you already pay for SuperGrok or X Premium+, you do not need an XAI_API_KEY. The bare-2200 wizard offers sign-in inline; you can also do it any time from Settings → "Sign in with X / SuperGrok" or from the CLI:

2200 oauth xai login     # device-code flow; print code + URL, poll
2200 oauth xai status    # show current credential + expiry
2200 oauth xai logout    # delete the local token (does not revoke at xAI)

The OAuth credential is fleet-wide: one sign-in covers every Agent in your fleet whose model is set to xAI / Grok (SuperGrok subscription) in the picker. The legacy API-key path (xai, reading XAI_API_KEY) stays available as a separate, parallel provider for anyone who prefers metered access. See the Grok-First decision record.

Update

2200 update           # check the registry, prompt, install, restart the daemon
2200 update --check   # just report whether a newer version is available
2200 update --yes     # install without the confirm prompt (for scripted updates)

2200 update only replaces the global package binary; your 2200_HOME state is never touched.

Uninstall

npm uninstall -g @twentytwohundred/2200
rm -rf ~/.local/share/2200/ ~/.config/2200/

Doing the npm uninstall without the rm lines is safe ... your fleet data remains on disk and a reinstall picks it up.

Windows

Use WSL2. Native Windows is not on the v0.1 support matrix.

Where to start

If you are new, read these in the wiki, in order:

1. Vision ... what 2200 is, who it is for, why it exists.
2. Architecture ... object model, runtime shape, how OpenPub and SCUT compose underneath.
3. Epic map ... the epic plan with scope, done-when, and dependencies.
4. Seed team ... who is building this, how they coordinate, when they migrate.

Then follow the conventions to understand how the wiki itself is structured (it dogfoods the same Brain pattern that 2200's Agents use for their own memory).

Status

Active build, in public. Live as of 2026-05-19.

What's shipped on main:

• Agent runtime kernel ... persistent supervisor + per-Agent processes, scheduler, brain (SQLite FTS5), tools, audited credential vault, structured logging, cost caps + per-Agent budgets. [[02-architecture]]
• Local pub coordination ... multi-Agent messaging on a shared box via OpenPub. Ambient routing, @-mentions, @team broadcast, anti-ack-spiral guards. Multi-Agent coordination has been running end-to-end for weeks.
• Nine LLM providers wired through a single provider abstraction: Anthropic (native Messages API), OpenAI, DeepSeek, Kimi (Moonshot), xAI (API key), xAI / Grok via SuperGrok subscription (OAuth, no API key), OpenRouter, Gemini, plus local for self-hosted endpoints (Ollama, LM Studio, vLLM, llama.cpp). The subscription path is the Grok-First positioning ... see the section above.
• SCUT cross-instance identity ... every Agent gets a verifiable identity at creation time. Hosted minter at register.openscut.ai for the default path; self-hosted SCUT for advanced operators.
• Conversational onboarding ... the wizard interviews you about an Agent you want to build, then materializes the Identity, suggests tools, suggests schedules, and auto-applies a curated Capability set. The interview transcript carries through to the new Agent's first brain note.
• Capability Catalog (Phase F) ... 13 first-party Capability entries on main (Gmail, Calendar, Drive, Slack, Discord, Telegram, GitHub, the major LLM providers, 1Password, Twilio, Stripe). Schema-validated frontmatter, walkthrough runner that drives credential prompts structurally, operator-override picker in the wizard, gap tracker that auto-files demand signals when the interview surfaces an intent the catalog can't satisfy.
• Web app (Epic 15) ... React + theme-aware design system. Fleet (Mission Control layout), Agent detail (Identity Card), Inbox (Keyboard Triage), Studio (multi-Agent pub canvas), Onboarding wizard, ⌘K command palette, Settings, Endpoints.
• Live gateways ... Discord and WhatsApp gateways are live; Slack and Telegram are catalog-ready.
• Restart authority model locked. Agents can restart themselves (restart_self); cross-Agent restart without operator approval is structurally impossible. See agent-restart-authority.
• 48 architecture decision records and 11 conventions locked. Prior-art surveyed (Hermes Agent, OpenClaw, Logseq, Trilium, Joplin, Cytoscape.js, react-markdown, remark-wiki-link, SilverBullet, Quartz, Foam, EdgeClaw, OCMT, OpenAEON, AnyClaw, mimiclaw) with license analysis.

1849 tests passing across the two workspace packages: 1754 runtime + 95 web. pnpm verify:all clean on every PR via CI.

The Cray test ... Hobby's actual migration into 2200 from Claude Code ... is the parallel track to the substrate work. The launch moment is David: when 2200 spawns its first Agent end-to-end through the wizard and that Agent does real work as a member of the team, the project ships. See 03-epic-map for the full plan.

Who is building this

Three Agents and a product lead, the seed team:

• Hobby ... primary build Agent. Writes spec and code. Currently runs as Claude Code on Doug's MacBook; migrates into 2200 on the Cray test.
• Simon ... DevOps. Owns infrastructure: provisioning, DNS, TLS, backups, deployment.
• Poe ... OpenPub specialist. Part-time on 2200 until OpenPub v0.3.1 ships.
• Doug Hardman (MrDoug) ... product lead.

David is not on the seed team. David is the first Agent 2200 will spawn through its own conversational onboarding flow. See 04-seed-team.

The daily handoffs at wiki/handoffs/hobby/ are the build log: every working day Hobby writes what was shipped, what's open, what's parked, what's coordinated with whom. The work is visible.

Repository contents

Path	Purpose
LICENSE	Elastic License v2
README.md	this file
AGENTS.md	conventions for Agents working in this repository
SECURITY.md	responsible disclosure
CONTRIBUTING.md	contribution model (seed-team-closed during the build phase)
CHANGELOG.md	release notes (populated when versioned releases start)
THIRD_PARTY_NOTICES.md	attribution for any code-lifts
.github/	issue templates, PR template, CI workflows
src/	runtime code (224 TypeScript modules)
tests/	test code (142 test files, 1754 runtime tests)
apps/web/	web app (Epic 15) ... React + Vite, theme-aware
scripts/	build, deploy, sync, and ops scripts

Development

TypeScript monorepo with two pnpm workspaces: the runtime at the project root and the web app at apps/web/. Node 22+ required (see .nvmrc).

# install dependencies (one-time)
pnpm install

# common dev commands (runtime workspace)
pnpm typecheck          # tsc --noEmit
pnpm lint               # eslint . (flat config; type-aware rules)
pnpm lint:fix           # auto-fix what's auto-fixable
pnpm format             # prettier --write .
pnpm format:check       # prettier --check . (used by CI)
pnpm test               # vitest run
pnpm test:watch         # vitest in watch mode
pnpm test:coverage      # vitest with v8 coverage
pnpm build              # tsup -> dist/
pnpm clean              # remove dist, coverage, .tscache

# everything CI runs, in order, for both workspaces
pnpm verify:all

CI runs on every PR and on main pushes (see .github/workflows/ci.yml). Type-check, lint, format check, test, build, for both workspaces. All must pass before merge. Branch protection requires CI green; self-merge is the workflow during the seed-team build.

Toolchain

Each pick is documented in the wiki decisions/ folder.

• Language: TypeScript with strict + type-aware ESLint rules
• Build: tsup (esbuild-based, sensible defaults for CLIs and libraries)
• Test: vitest
• Lint: eslint with typescript-eslint flat config; strictTypeChecked + stylisticTypeChecked recommended sets
• Format: prettier (no semicolons, single quotes, trailing commas, 100-char width)
• Package manager: pnpm
• Web framework: React 19, Vite, theme-aware design tokens generated from tokens.json

Project layout (high level)

src/runtime/
├── agent/                Agent process boundary (bootstrap, loop, sandbox)
├── llm/                  provider abstraction (8 vendors + local)
├── pub/                  OpenPub integration, ambient routing, anti-ack guards
├── brain/                per-Agent + shared Brain (SQLite FTS5)
├── credentials/          audited vault, credential_request surface
├── onboarding/           conversational interview + Capability catalog + walkthroughs
├── supervisor/           fleet supervisor, scheduler, control plane
├── http/                 HTTP API the web app drives
├── connectors/           Discord, WhatsApp, Slack, Telegram gateways
├── tools/                baseline tool registry (built-in tools)
├── secrets/              SecretRef resolution + sealed storage
└── ...
apps/web/src/
├── screens/              Fleet, Agent, Inbox, Studio, Settings, Onboarding, ...
├── primitives/           Pill, Card, Button, Tag, ...
├── palette/              ⌘K command palette
├── theme/                theme switcher + token plumbing
└── ...

License

Elastic License v2. Source-available. Use, copy, distribute, and create derivative works are permitted; hosting as a managed service to third parties and license-key tampering are prohibited.

Prior-art surveyed in the wiki has been license-checked. See License posture in AGENTS.md and license-posture in the wiki for the discipline applied to any code-lift. Attributions live in THIRD_PARTY_NOTICES.md.

Security

See SECURITY.md for responsible disclosure.

A deeper read on what's a structural security boundary in 2200 vs what's a heuristic ... heuristics-vs-boundaries ... is the public posture.

Contributing

The seed team is closed during the build phase. After launch, see CONTRIBUTING.md for the contribution model.

Cross-references

• Project domain: 2200.ai
• GitHub org: github.com/twentytwohundred
• Wiki (knowledge base): twentytwohundred/wiki
• Daily build handoffs: wiki/handoffs/hobby/
• License: Elastic License v2

---

Built in public. Ship when ready.

2200 is developed by TWENTYTWOHUNDRED LLC. Licensed under the Elastic License v2.0.