Build

CLI

One surface for humans and agents.

draftline is a Rust binary that does what your fingers and your agents do. Same commands. Same outputs. Same auth. Built so agents and operators share the same terminal surface — if you can call it, an agent can. If an agent can call it, you can.

Install

Install paths are being published. The CLI is in beta. Until the homebrew tap, crates.io publication, and GitHub releases pipeline are live, request a build via sales@gofield.net. The commands below are stable.

Planned install paths:

Homebrew
brew install draftline-tools/tap/draftline
Cargo
cargo install draftline
Prebuilt binary
# macOS / Linux / Windows
# Download from: github.com/draftline/cli/releases

Auth

The CLI authenticates against your workspace via your browser. Tokens are stored in your OS keychain — never on disk in plaintext.

draftline auth login    # opens browser, stores token
draftline auth status   # verify current token
draftline auth logout   # remove token

On a headless box (CI, server, agent runner), use a workspace-scoped service token via DRAFTLINE_TOKEN.

Common commands

The CLI surface mirrors the platform's domain model — jobs, routes, photos, classifications, reviews, writebacks.

# Jobs
draftline jobs list
draftline jobs get <job-id>
draftline jobs create --name "Buckhead Loop" --client Verizon

# Photos and classification
draftline photos upload <job-id> ./photos/
draftline photos classify <job-id>
draftline photos reassociate <job-id>

# Review queue
draftline reviews list --pending
draftline reviews signoff <review-id>

# Export
draftline export <job-id> --format json
draftline export <job-id> --format csv

# Writeback (requires signoff)
draftline writeback push <job-id> --target katapult

Every command supports --json for machine-readable output, and --help for full flag reference.

Why the CLI is the test.

Most companies build an internal CLI for engineers and a separate API for partners and agents. The surfaces drift. The CLI lies. The API rots.

We don't do that. The CLI is the same surface our MCP server exposes, the same surface our purpose-built agent runs against, and the same audit log catches every call. If the agent can do it via MCP, you can do it via the CLI. If the CLI can do it, the agent can. That symmetry is the test that keeps the surface honest.

Want a CLI build now, before the install paths are live?

We'll send you a signed binary. Tell us your OS and what you're trying to wire up.