CLI · single binary

Drive faultline
from your terminal.

The faultline CLI authenticates your machine, mints API tokens, wires the MCP server into your editor in one command, and — if you self-host — runs the server itself.

1. Install

Have the Go toolchain? Install straight from source. Version: latest.

terminal

go install github.com/outdoorsea/faultline/cmd/faultline@latest

No Go toolchain? Grab a pre-built binary (macOS / Linux, arm64 + amd64) from the latest GitHub release ↗, unpack it, and put faultline on your PATH.

2. Authenticate

Log the CLI in — it opens a browser for OAuth, so there's no dashboard token-copying. Then mint a long-lived fl_ token for scripts and the MCP server.

terminal

faultline login          # OAuth against https://faultline.live
faultline token create   # mint a long-lived fl_ token

Pointing at a different backend? Add --url https://faultline.live to faultline login.

3. Wire up your agent

One command registers the faultline MCP server with Claude Code — it runs claude mcp add on your behalf. The MCP server page covers editor-specific config and the full tool list.

terminal

faultline mcp install                 # register with Claude Code
faultline mcp install --print         # print the command instead (Cursor, Windsurf)
faultline mcp install --project-id 7  # pin a project

Command reference

faultline init — first-run setup (self-host)
faultline login [--url URL] — authenticate the CLI
faultline token create — mint a long-lived fl_ token
faultline mcp install [--local] [--print] [--project-id N] — wire up the MCP server
faultline issues [--mine] [--claim ID] — crew helpers
faultline start | stop | status — daemon control (self-host)
faultline serve — run the server (self-host)
faultline version — print version + commit

Run faultline help to see the full command list.

Next: point your agent at your bugs.

Install the MCP server and let your editor list, diagnose, and resolve faultline issues.

MCP server → Back to home