How to connect a runner to your Infa board and let Claude Code agents execute tasks on your behalf.
This feature is available on all Infa plans (Free, Pro, and Enterprise).
Runners let you trigger Claude Code agent sessions directly from your Infa board — without leaving the browser. You write a prompt, start a run, and a connected runner picks it up, executes the task in your local repository, and streams progress back to the board in real time.
Copy link
How it works
infa.ai board (browser)
│
│ You create a run (queued)
▼
Supabase Realtime
│
│ Runner subscribes and picks up the run
▼
Infa CLI / Electron app (your machine)
│
│ Spawns a Claude Code session in your repo
▼
Claude Code agent
│
│ Edits files, runs commands, reports progress via hooks
▼
Supabase Realtime → back to your board
We at Infa designed runners so that Claude always has access to your actual filesystem — meaning it can read and modify real files, run your test suite, and commit changes to Git, just as it would in a normal Claude Code session. Everything it does streams back to your board live.
Both options run a local server on http://localhost:7100 that the board polls to detect runner status.
Copy link
Connect with Infa CLI
# 1. Install
npm install -g infa
# 2. Authenticate
infa auth
# 3. Link the board to your local repo
infa board
# 4. Start the runner
infa preview
Once running, the board shows a "Runner connected" indicator at b/{boardId}/runs. Any run you create is immediately picked up.
Keep it running
The runner only picks up queued runs while the process is active. Runs created while the runner is offline will queue and execute as soon as it reconnects.
Copy link
Connect with the Desktop App
Download and install the Infa desktop app
Sign in with the same account you use on infa.ai
Open the app and select the board you want to work with
The app starts the runner automatically — no extra steps needed
The board detects the connection within 30 seconds.
Copy link
Run configurations
Before starting runs, set up at least one run configuration on your board. A run configuration tells the runner which repository to use, which branch to base new work on, and what the agent is allowed to do.
Run configurations are managed per board. To create one:
In your terminal, run infa board from your repo folder — this walks you through linking a repo and creates the first configuration
Or open your board → overflow menu → Integrations to manage existing configurations
Each configuration stores:
Field
Purpose
Repository path
Local folder the runner opens Claude Code in
Base branch
Git branch new work branches off from
Branch prefix
Prefix applied to auto-created branches (e.g. agent/)
Permissions
What Claude is allowed to do (read-only, edit files, run commands)
Copy link
Connection status
The Runs page (b/{boardId}/runs) always shows current runner status at the top:
Runner connected — a runner is active and will pick up new runs immediately
No runner connected — runs will queue; connect a runner to start execution
If you see "No runner connected" but your CLI is running, check that infa preview started without errors and that you are authenticated (infa auth --status).
Claude Code Agent Runners
This feature is available on all Infa plans (Free, Pro, and Enterprise).
Runners let you trigger Claude Code agent sessions directly from your Infa board — without leaving the browser. You write a prompt, start a run, and a connected runner picks it up, executes the task in your local repository, and streams progress back to the board in real time.
We at Infa designed runners so that Claude always has access to your actual filesystem — meaning it can read and modify real files, run your test suite, and commit changes to Git, just as it would in a normal Claude Code session. Everything it does streams back to your board live.
Infa CLI (recommended)
Infa Desktop App
Both options run a local server on
http://localhost:7100that the board polls to detect runner status.Once running, the board shows a "Runner connected" indicator at
b/{boardId}/runs. Any run you create is immediately picked up.The runner only picks up queued runs while the process is active. Runs created while the runner is offline will queue and execute as soon as it reconnects.
The board detects the connection within 30 seconds.
Before starting runs, set up at least one run configuration on your board. A run configuration tells the runner which repository to use, which branch to base new work on, and what the agent is allowed to do.
Run configurations are managed per board. To create one:
infa boardfrom your repo folder — this walks you through linking a repo and creates the first configurationEach configuration stores:
agent/)The Runs page (
b/{boardId}/runs) always shows current runner status at the top:If you see "No runner connected" but your CLI is running, check that
infa previewstarted without errors and that you are authenticated (infa auth --status).Managing Runs
Board Agents
Hooks & Agents
Run Modes
Infa CLI Reference