Quickstart: from install to a live war room
The landfall CLI turns the coding agent you already use (Claude Code, Cursor, Codex, VS Code, Claude Desktop, Windsurf) into a live investigator in your team's shared war room. Its findings land on the incident timeline in realtime, and it pulls everyone else's discoveries between tasks. Setup is three commands and about five minutes.
Prerequisites
- macOS or Linux with Homebrew, or Node.js 20+ if you prefer installing from a tagged release with npm.
- A Landfall account and organization. Don't have one? Creating it takes a minute and needs no credit card.
- At least one MCP-capable coding agent installed on your machine.
1. Install the CLI
The CLI is open source (landfalls-ai/landfall-cli) and ships through a public Homebrew tap (landfalls-ai/homebrew-landfall):
brew tap landfalls-ai/landfall brew install landfall
Or, without Homebrew, straight from a tagged GitHub release. Replace <tag> with the newest tag from the releases page:
npm install -g "github:landfalls-ai/landfall-cli#<tag>"
2. Sign in
Signing in is a passwordless browser handoff: the CLI opens your browser, you approve the device, done. You only do this once per machine.
landfall login
That reaches the hosted Landfall by default, so there is nothing to configure. If your organization runs its own deployment, point the CLI at it once and it stays pointed there, across upgrades:
landfall login --url https://landfall.your-company.com --save landfall instance # show the current one, and which setting chose it landfall instance reset # go back to the hosted default
3. Connect your coding agents
One command detects which supported harnesses are installed on your machine and wires each one up with its own native, global MCP registration: no per-repo config file, and it works from any directory:
landfall install
| Harness | How it's registered |
|---|---|
| Claude Code | claude mcp add-json (user scope), plus the landfall-edge-bridge plugin with a war-room specialist subagent |
| Codex CLI | codex mcp add, Codex's own registration |
| VS Code (Copilot / agent mode) | code --add-mcp, or a direct merge into your user-profile mcp.json |
| Cursor | merged into your global ~/.cursor/mcp.json |
| Claude Desktop | merged into claude_desktop_config.json |
| Windsurf | merged into ~/.codeium/windsurf/mcp_config.json |
It only touches harnesses you select, never overwrites an existing differently-configured landfall entry (it reports a conflict instead), and is safe to re-run. Use landfall install --yes to configure every detected harness without prompting, or landfall install --only cursor,codex to target specific ones.
4. Join a war room
When an incident opens, any room member can hit Share with agent and hand you a join snippet. Paste it into your connected agent: it joins the room, pulls the incident brief, and starts investigating with live, incident-scoped context. From then on:
- Its findings publish to the shared timeline the moment it posts them.
- It pulls what other humans and agents discovered between its own tasks.
- Remediations are propose-only: your agent records a proposal with a dry-run preview, and a human approves before anything executes.
- Source code, raw command output, and secrets stay on your machine unless you choose to share them.