brainiac-featureparity

FeatureParity plugin for Brainiac: your agents take work straight from FeatureParity.

• Start work. Someone presses Start work on a requirement and picks one of your agents. That agent gets a worktree for the requirement and implements it, with tests bound to it (fp:<slug>).
• Tags. Someone tags your agent in a requirement's comments (for example "please re-check the suspect tests"). The agent reads the comment, does it, and replies on the requirement.
• Coverage gaps (opt-in). A requirement goes live on a surface with no tests. An agent writes them.
• Rejections. A human rejects a change your agent proposed. The same agent reworks it in its existing worktree.

Every delivery is signed by FeatureParity, and the plugin refuses anything it can't verify.

You need Brainiac running with a public URL that reaches it (Brainiac's setup uses an ngrok tunnel), and an account on FeatureParity.

gem install brainiac          # if you don't have Brainiac yet
brainiac setup                # its own first-run setup
brainiac install featureparity
brainiac featureparity setup  # writes ~/.brainiac/featureparity.json
brainiac restart

Every repository your agents should work in must be a project in ~/.brainiac/projects.json (Brainiac's usual setup). FeatureParity names projects by their slug (fp projects). Name the Brainiac project the same, or map it (see Configuration).

In FeatureParity, open Agents & API keys (under your account). For each agent that runs on this Brainiac, click Wake-up and enter:

https://<your-public-url>/featureparity

FeatureParity shows a signing secret (whsec_...) once. Add it to ~/.brainiac/featureparity.json:

{ "signing_secrets": ["whsec_..."] }

All your agents can share the one address, because each delivery names the agent it's for. Each key has its own secret, so list every one.

The agent key's name has to match the Brainiac agent: a key named galen or shown as Galen reaches the Brainiac agent Galen. Map names that differ with "agents".

For events no single agent owns, add a webhook in Project Settings → Integrations: same URL, provider generic. Subscribe to Change rejected and, if you turn on dispatch_gaps, Coverage gap. Add its signing secret to signing_secrets too.

If your agents already have wake-up addresses, there's no need to subscribe this webhook to Work started or Agent tagged. If you do, the plugin notices the repeat and starts the agent only once.

Open an approved requirement, click Start work, and pick your agent. The page tells you whether the agent received it. brainiac logs shows the dispatch. Each webhook's Recent deliveries in FeatureParity shows what was sent and what Brainiac answered.

~/.brainiac/featureparity.json (reloaded when it changes):

{
  "api_base_url": "https://api.featureparity.dev",
  "environment": "prod",
  "accept_environments": ["prod"],
  "signing_secrets": ["whsec_..."],
  "agents": { "claude-laptop": "Galen" },
  "default_agent": "Galen",
  "projects": { "feature-parity": "feature_parity" },
  "dispatch_gaps": false,
  "gap_agent": "Galen"
}

The plugin answers within FeatureParity's 5-second window and does the work in the background. FeatureParity retries a delivery that gets no answer; the plugin acts on each delivery, and each Start work, comment or gap, once.

brainiac featureparity setup   # create the config and show these steps
brainiac featureparity config  # show the config (secrets shortened)
brainiac featureparity status  # what's set up
brainiac featureparity help

• Brainiac >= 0.1.8
• Ruby >= 3.4
• A FeatureParity account (agent wake-up addresses and signed deliveries need the current FeatureParity)

MIT