Overview

Getting started

Last updated: 2026-04-30

Five minutes from npm install to a working fastpace install with a sample feature in flight. Pre-flight: Node 18 or higher.

1. Install

npm install -g @fastpace-ai/fp

Air-gapped? See Air-gapped install instead — it's a tarball with no npm involvement.

2. Initialize a repo

cd ~/work/your-repo
fastpace init

This writes:

~/.fastpace/manifest.json — host-level discovery manifest.
~/.fastpace/identity/ — your Ed25519 install identity (private key mode 0o600, never transmitted).
fastpace/manifest.json — this repo's discovery manifest.
fastpace/audit.log — the hash-chained audit log starts here.
fastpace.config.yaml — guardrails + hook config.
.claude/ — agent + hook + skill files (Claude Code convention).

Tip: Drop fastpace into an existing repo (brownfield) or a fresh directory (greenfield). Either works — the only difference is whether fastpace inventory finds pre-existing files to surface.

3. Verify the chain

fastpace verify

[ok] chain integrity: 1 entry signatures verified 1

That's the bootstrap entry from init. Every tool call your AI agents make from here on appends to this chain, signed with your install identity, and verifiable any time with that one command.

4. Open the local dashboard

fastpace ui

Default port 7777 (override with --port or FASTPACE_PORT). The dashboard shows agents, hooks, manifests, AI-BOM, reliability score, exception log, framework mapping, and 30+ other Compliance views organized into 5 collapsible subgroups plus 3 collapsible top-level groups (Documents / Planning / Learning).

5. Check your governance posture

fastpace posture

One command answers "how much of my AI code can I prove and govern?": provenance coverage, audit-chain integrity, reliability, open risk, red-team posture, shadow-AI (AI commits with no fastpace provenance), the cross-vendor assistant mix, and per-vendor policy conformance. --json emits the payload the dashboards consume.

6. Govern more than one assistant (optional)

fastpace plugin build --target all --out ./dist/plugins
fastpace plugin policy --target all
fastpace plugin context --target all --out .

One hook codebase, one fastpace.policy.yaml, and one fastpace/context/ tree generate the guardrail bundle, native policy config, and context file for Claude Code, Codex, and Gemini CLI. Swap the model — the governance doesn't move.

7. Scaffold a feature (optional)

Inside Claude Code (or Codex / Gemini CLI), run:

/fp-new-feature "migrate auth to OIDC"

This calls fastpace's onboarder agent, which scaffolds a watch-card with a draft PRD, ERD scaffold, and execution plan. Every tool call along the way lands in the audit chain.

What's next

CLI reference — full command catalog with examples.
Primitives index — what each F0.x / F1.x / F2.x / F3.x feature does and which version shipped it.
Audit schema — the contract every signed artifact follows.
Hook contract — how to write your own hooks against the same fastpace inputs.