Skip to main content
Use cases / AI agent teams

Run a team of AI coding agents on your own machine, with every step visible

PRFactory orchestrates AI agent teams without running them. The AgentTeamForge worker CLI runs a lead agent and its team on the developer's machine, with the Claude Code or Codex subscription already there. The server holds the plan, the state and the checkpoints, and never executes an agent.

The problem

A coding agent in a terminal is fast but invisible. Nobody else sees what it is doing, a long run has no checkpoints, and putting agents on a shared server means handing over code, credentials and model keys.

How PRFactory handles it

Install AgentTeamForge (atf) on the machine and connect it with atf prfactory connect. From then on the machine polls PRFactory for work on the repositories its token covers and runs each phase locally, in a git worktree, with the CLI agents installed there.

  • A lead and its team. For a phase run as a team, a lead agent spawns child agents from the phase recipe and can add more from a bounded budget.
  • Visible while it works. Each agent's role, state and output are on the ticket. Message any one of them, or stop it.
  • Your agents, your subscription. Claude Code, Codex, Pi or Cursor CLI, each step with its own model and reasoning effort. No API key is handed to PRFactory and no credits are bought.
  • Nothing runs on the server. No server-side model call and no agent in the web process.
prfactory · PRF-41 · phase 4
TEAM LIVEElapsed 14:22Running 3 of 6Lead wake event-driven
Running
leadimplementClaude Code Claude Opus high
Applying review round 2: editing WorkItemClaimService.cs
started 14:22 agoheartbeat 3s5 spawns issued
Running
review:backendCodex GPT-5 xhigh
› lease fencing looks correct, checking the secondary-repo authorization order…
6:02
beat 1s
Waiting
review:frontendClaude Code Claude Sonnet mediumparked · awaiting reply
› asked the lead a question instead of blocking on a prompt
2:15
idle since 2:15
Running
test:unit-gateCursor CLI Gemini low
› 845 passed · 0 failed · running Web.Tests…
0:48
beat 4s
Done
plan:slicePi Claude Opus mediumdone
3:41

The split, in one line each

prfactory.dev — tickets, phases, artefacts, checkpoints, the work queue.

your machine — the worker, the agents, the worktree, the branch it pushes.

between them — the worker calls the server; the server never connects to your machine.

Put a team of agents on your next ticket

Your machine, your agents, your subscription. PRFactory keeps the process.