Fabriq
Agents

Connecting AI Agents

Choose and connect your AI coding agent backend — OpenCode or Claude Code.

Fabriq works by communicating with an AI coding agent through ACP (Agent Communication Protocol) — a stdio JSON-RPC bridge. You install an agent on your machine, configure it in Fabriq, and the bridge handles the rest.

One agent process, multiple Fabriq UI surfaces. The agent writes files in the worktree, Fabriq surfaces every action for your approval.

Which agent should I use?

OpenCodeClaude Code
CostFree (open source)Paid (Anthropic API)
Setupnpm/pnpm installInstall CLI + API key
CapabilitiesFull feature setFull feature set
Best forTeams that want open-source controlTeams already using Claude ecosystem
LanguagesAny (language-agnostic)Any (language-agnostic)

Both agents work identically from Fabriq's perspective — the ACP protocol abstracts the backend. Choose whichever fits your workflow and budget.

How to connect

The connection flow is the same for both agents:

  1. Install the agent on your machine (see setup guides below)
  2. Verify the agent CLI works (run opencode --version or claude --version)
  3. Configure in Fabriq: Settings → Agent → Select your agent
  4. Connect: Fabriq starts the agent as a subprocess via ACP

When connected, you'll see:

Agent: OpenCode v2.1.0 ● Connected

What the connection enables

Once connected, the agent can:

  • Read and write files in the feature worktree
  • Run terminal commands
  • Use git operations
  • Access project context you've injected
  • Respond to your questions and direction

All actions are validated, displayed for your review, and require your confirmation before execution.

Quick troubleshooting

ProblemCheck
Agent not appearing in dropdownIs it installed? Run <agent> --version in terminal
Connection refused after selectingDoes the CLI work outside Fabriq? Try running <agent> manually
Agent connects but then disconnectsCheck for version incompatibility. Update both Fabriq and the agent
Actions seem slowAgent processing time varies. Check the activity log for progress

Next steps

Edit on GitHub

Last updated on

On this page