Reference

landfall CLI

The landfall CLI is open source at landfalls-ai/landfall-cli, its README is the authoritative, always-current reference; this page is the short map.

Install & upgrade

Terminal

brew tap landfalls-ai/landfall
brew install landfall
brew upgrade landfall   # later, to pick up new releases

The Homebrew formula lives in the public tap at landfalls-ai/homebrew-landfall.

Authenticating

landfall login opens your browser and signs this machine in the same way you already sign in to Landfall on the web — password, or your organization's own identity provider if it has one connected. The CLI never needs to know which: your browser resolves that, and hands a working, org-pinned session back to the terminal that asked for it. There is nothing different to configure for an organization with SSO — the same command works either way.

That session renews itself silently in the background from then on — no re-prompt, no flag to turn on. You only see the browser again if you explicitly landfall logout, or an organization admin revokes all sessions.

For anywhere login's browser handoff can't reach — a CI job, a cron job, a headless machine with no browser to open — create a personal API key instead. In the web app, go to Settings → Security for any organization you belong to and use the API keys panel to mint one. The full key is shown exactly once, at creation; store it wherever your script or CI system keeps secrets. Present it as a bearer token on any request:

Terminal

curl -H "Authorization: Bearer lf_key_…" \
  https://api.landfalls.ai/o/<your-org-slug>/incidents

A key is scoped to the one organization it was created for and to your own account's access within it — never more. Revoke it any time from the same panel; revocation takes effect on the very next request. Up to 10 active keys per organization, so keys for different machines or jobs can be told apart and rotated independently.

Commands

Command	What it does
landfall login	Sign this machine in via a passwordless browser handoff. Needed once, before install.
landfall install	Detect the coding harnesses on this machine and register the landfall MCP server with each one you select. Idempotent and conflict-safe. Flags: --yes (all detected, no prompt), --only <list> (target specific harnesses).
landfall uninstall	Remove the registrations install created. Only deletes an entry that still matches exactly what was written; anything modified is left in place and reported.
landfall serve	Run the MCP Edge Bridge on stdio: join the incident and expose the ten war-room tools to whatever agent started it. Harnesses invoke this themselves via the registration; --link <shareURL> (or LANDFALL_LINK) pre-joins from a share link.
landfall join	Join an incident and keep presence alive without exposing MCP tools; Ctrl-C to leave.
landfall note "…"	Post a one-off finding to the room straight from your terminal.
landfall leave	Leave the incident.
landfall logout	Clear the cached session from this machine and revoke it server-side.

For what the bridge actually does inside a session (the tools, the realtime loop, the Claude Code plugin), see Using Claude Code.

Issues & contributions

Found a bug, or a harness we don't support yet? Open an issue on the GitHub repo, the CLI is developed in the open.