Run Claude Code and Codex in parallel, each in an isolated git workspace.

Turn issues into branches, steer multiple agents, review changes, and keep pull requests moving from one local command center.

Factory Factory is a local workspace manager for AI coding agents. Every workspace gets its own git worktree and branch, so agents can work on separate tasks without stepping on each other. The UI brings chat, diffs, files, terminals, issues, and pull request status together in one place.

You will need:

• Node.js 26.8.1+ for the CLI and development (pinned in .node-version); the desktop app uses Electron's bundled Node.js runtime
• macOS 13 (Ventura) or newer for the macOS desktop app
• A local git repository
• At least one agent provider:
  • Claude Code, authenticated with claude login
  • A ChatGPT/Codex account configured for Codex sessions
• The authenticated GitHub CLI for GitHub issues and pull requests

Start Factory Factory without installing it:

npx factory-factory@latest serve

Factory Factory opens in your browser and stores its database in ~/factory-factory/ by default.

See Settings for IDE commands, default chat models, and project configuration.

Then:

1. Add a project by selecting a local git repository. If the New Project page cannot load your projects, it shows the error and a Retry button. Retry loads the list again before showing onboarding or the Add Project form.
2. Create a workspace, or start one from a GitHub or Linear issue.
3. Choose Claude or Codex and start a session.
4. Review the agent's changes, use the integrated terminal when needed, and open a pull request.

• Parallel, isolated work: Each task runs in a dedicated worktree and branch while your main checkout stays untouched.
• One workspace for the whole task: Chat with agents, inspect files and diffs, run commands, and track PR state without switching tools.
• Claude and Codex sessions: Factory Factory connects to both providers through the Agent Client Protocol (ACP), with resumable sessions and runtime model options.
• Issue-to-PR workflow: Pull assigned work from GitHub or Linear, link it to a workspace, and follow it through to merge.
• Automatic PR progression: Ratchet watches open pull requests and can dispatch follow-up agents for failing CI and actionable review feedback.
• Repeatable automation: Quick actions, periodic tasks, and child workspaces help split up or repeat common workflows.

The core model is intentionally small:

Project (a local git repository)
└── Workspace (an isolated worktree and branch)
    ├── Agent sessions (Claude or Codex over ACP)
    └── Terminal, files, changes, and pull request state

For regular use, install the CLI globally:

npm install -g factory-factory
ff serve

Useful commands:

ff serve --help     # Ports, database path, host, and other options
ff proxy --private  # Share the app through a password-protected Cloudflare tunnel
ff db:studio        # Inspect the local database with Prisma Studio

ff proxy requires cloudflared on your PATH. Factory Factory automatically runs database migrations, finds an available port, and opens the browser when the server is ready.

To serve Factory Factory from your own domain (e.g. https://ff.example.com) via nginx, Caddy, or another reverse proxy:

• Set CORS_ALLOWED_ORIGINS to the exact public origin(s), comma-separated: CORS_ALLOWED_ORIGINS=https://ff.example.com. This gates both HTTP CORS and WebSocket upgrades; non-loopback origins must match exactly (scheme + host + non-default port, no trailing slash).
• Keep BACKEND_HOST bound to localhost/127.0.0.1 so only your proxy can reach the server.

By default the server rejects WebSocket upgrades that carry client-address headers (x-forwarded-for, cf-connecting-ip, etc.), because it expects to sit behind an authenticated proxy that strips them. If your reverse proxy adds these headers, either strip them before forwarding, or set TRUST_PROXY_HEADERS=true to accept them. Only enable TRUST_PROXY_HEADERS when the backend is reachable solely through your trusted proxy (i.e. bound to loopback) — otherwise clients could spoof address headers. The remote-address trust check (loopback / TRUSTED_LOCAL_CIDRS) still applies.

For local testing from an origin that isn't in CORS_ALLOWED_ORIGINS (an alternate dev frontend, curl/Postman, or a LAN device that also satisfies TRUSTED_LOCAL_CIDRS), set DISABLE_CORS_CHECKS=true to skip Origin validation entirely. Local dev only — never set this in a deployed or reverse-proxied environment; it removes the app's only defense against a malicious webpage you have open calling the local API on your behalf (workspace/project creation, local command execution).

[!WARNING] Factory Factory runs coding agents that can execute commands and modify files without manual confirmation. Workspaces isolate git branches; they are not containers or security sandboxes.

Use Factory Factory only with repositories and agent instructions you trust. Review changes before merging, protect your GitHub and Linear credentials, and consider a VM or container when working with untrusted code.

Use pnpm 12.4.2, pinned in package.json. Dependency build permissions live in pnpm-workspace.yaml under allowBuilds; review new build scripts with pnpm approve-builds when adding or updating dependencies.

Development requires Git 2.32 or newer for lint-staged. Builds and typechecks use TypeScript 7 through the @typescript/native package alias. The typescript alias provides Microsoft's TypeScript 6 compatibility API for guardrail scripts and tools that parse source files; tsc runs version 7 and tsc6 runs version 6.

git clone https://github.com/purplefish-ai/factory-factory.git
cd factory-factory
pnpm install
pnpm dev

Before opening a pull request, run the standard checks:

pnpm test
pnpm typecheck
pnpm check

See CONTRIBUTING.md for project structure, conventions, and the full contributor workflow.

Factory Factory was inspired by Conductor, VibeKanban, Gastown, and Multiclaude.

MIT