From zero to a local city you can already observe.

Requirements

Install and authenticate only the CLIs you want to use: Claude, Codex, OpenCode, or Kimi. Agents City does not bundle or replace those accounts.

$command -v claude$command -v codex$command -v opencode$command -v kimi

GitHub is optional

You can mount repositories already on disk or document folders without an account. Only when you choose GitHub does Agents City use the separate gh CLI and its web or device-code login to list and clone repositories you can already access.

Install and open the Hall

The first command installs the current beta in your active Node installation. The second opens the Hall on 127.0.0.1 and guides you through the first city.

$npm install -g agents-city@beta$agents-city

Check the installed surface before starting a city.

$agents-city --version$agents-city --help

Try it without installing

npx downloads the beta into its cache and opens the same Hall without changing your global npm folder.

$npx agents-city@beta

Install from source

To contribute, inspect exactly what you will run, or try changes in main that are not on npm yet, clone the repository and pack the same file set.

$git clone https://github.com/jlcases/agents-city.git$cd agents-city$npm pack$npm install -g ./agents-city-*.tgz

Try the demo first

Choose Aurora Games, Clínica Alba, or Costa & Ley. Each story creates a temporary copy and replays the committee, a failed verification, the replan, and the corrected close over the real system. It starts no models and does not change ~/.agents-city.

$agents-city demo$agents-city demo --domain medicina$agents-city demo --domain legal

Create the first city

With no command, Agents City opens the Hall. If you prefer terminal questions, use seat or setup --tui.

$agents-city$agents-city setup --city product$agents-city setup --city product --tui

On current main, the first run covers seven decisions

1. 1

   Domain — software, healthcare, legal, finance, marketing, sales, research, operations, or custom.

2. 2

   Seat role — the chair’s responsibility, not a bus permission.

3. 3

   Agents, one at a time — each agent gets a name, code/knowledge/coordinator kind, role, all its repositories or folders, runtime, and explicitly selected skills when the engine supports them.

4. 4

   Goal — a signal, baseline, target, and date; qualitative judgement is also valid.

5. 5

   Chair runtime — Claude by default, or Codex, OpenCode, Kimi, and an explicit terminal fallback.

6. 6

   Chair confirmation — choose whether your own local chair asks permission; agent windows keep their cage.

7. 7

   Desktop door — main can create a macOS app, Linux entry, or Windows shortcut through WSL.

Hall or tmux session

The Hall manages the same configuration as the CLI and opens on the map. seat starts or resumes tmux with one chair plus one window per agent.

$agents-city hall --city product$agents-city seat --city product