fcs-bridge

Local supervision daemon for the Founder Control System — installs Claude Code hooks into a project and relays structured build events to a self-hosted FCS dashboard.

No source code, diffs, or secrets leave your machine unless a project explicitly opts in — only structured metadata (tool name, file path, lines changed, test pass/fail, commit SHA) crosses the wire, and a local secret-redaction pass runs before anything is sent.

Usage

In the repo you want supervised:

npx fcs-bridge init --project-id <id> --token <token> --cloud-url <your-fcs-dashboard-url>

This writes .fcs-bridge.json (safe to commit) and .fcs-bridge/credentials.local.json (gitignored automatically) into that repo, and merges PreToolUse/PostToolUse/Stop/SessionStart/Notification hooks into its .claude/settings.json — non-destructively, alongside whatever hooks are already there.

Start a Claude Code session in that repo as normal — supervision begins automatically.

Associate the session with a specific build stage (optional):

fcs-bridge set-stage <buildStageId>

You'll need an FCS dashboard running somewhere reachable (self-hosted) to supply the --cloud-url, --project-id, and --token. See the main repo for dashboard setup.

Optional: plan summaries

Set ANTHROPIC_API_KEY in the shell you run Claude Code from and the bridge will summarize each plan-mode plan (stages, risks, decisions worth confirming, acceptance criteria) into the dashboard — entirely local: the plan text never leaves your machine, only the resulting structured summary is sent. Leave it unset and this step is silently skipped; nothing else about supervision depends on it. This makes a real API call per plan (small cost, using claude-haiku-4-5).

Optional: provider decision assistant

With the same ANTHROPIC_API_KEY set, a blocked dependency install (npm install X, pip install X, etc.) gets a quick check for whether X is an external hosted service rather than an ordinary library — if so, the approval includes a cost estimate and 2-4 alternatives. Silently skipped without the key, same as plan summaries.

Bringing an existing repo under supervision

If the repo already has code (possibly already AI-built) rather than starting blank, run this after init:

fcs-bridge audit

Requires ANTHROPIC_API_KEY. Scans the repo locally (README, manifest, recent commit history, top-level structure — not a deep source read) and reconstructs a first-pass product vision plus any decisions/open questions it can find real evidence for. Everything lands as provisional: the vision appears on the dashboard's Vision workspace as a pending import you explicitly adopt or discard, and decisions land as PROPOSED/INFERRED in the normal Decisions review flow — nothing is adopted automatically.