Configs

Four layers, cleanly stacked

fastpace reads from four configuration layers. A later layer overrides an earlier one only for the keys it sets — everything else falls through.

CLI flags
on the command line
1

Highest precedence — overrides everything below for this single invocation.

  • --port 7778
  • --no-open
Environment variables
process env
2

Per-shell or per-CI overrides. Common for setting a custom identity directory.

  • FASTPACE_PORT
  • FASTPACE_IDENTITY_DIR
  • FASTPACE_NO_UPDATE_CHECK
Repo config
fastpace/config.json
3

Lives in your repo, committed to git. Picked up by every fastpace command run inside this repo.

  • { "approved_runtimes": [...] }
User config
~/.fastpace/config.json
4

Per-developer baseline. Everything else falls through to these defaults.

  • { "port": 7777 }

Common settings

Whatever isn't set here falls through to defaults baked into the binary.

KeyDefaultWhat it does
port 7777 Local UI port
approved_runtimes ["claude-opus-4.7", …] Allow-list of model aliases — calls to anything else are blocked
pii_pattern_override null Extend the prompt-redactor with org-specific regex patterns
pii_pattern_disable [] Turn off bundled redactor patterns by name
integrations {} Jira / Linear / Slack credentials (per-repo)
webhooks [] Outbound webhook receivers for fleet events
Identity has its own directory

The cryptographic identity (F0.1) lives separately at ~/.fastpace/identity.{json,key} — override with FASTPACE_IDENTITY_DIR. Losing config is annoying; losing the identity key invalidates every signed manifest you've ever shipped.

Inspect the merged config

Run fastpace ui and jump to Settings · Config — every effective value is shown alongside the layer it came from, so you can debug overrides without spelunking through four files.