Factory

Runners and Claude

Factory threads run on SpudSuite runners that you install, using the Claude Code command-line tool on that machine. Each thread stays on the runner that first ran it, and every turn picks up the same Claude Code session.

#Set up a runner for Factory

1. Install a runner and pair it with your workspace.
2. Install Claude Code on the same machine, so the claude command works.
3. Sign Claude Code in, in one of two ways (below).
4. Check with spud factory status, which says whether Claude Code is installed and signed in. The Factory page shows the same for each runner.

#Signing in to Claude

With your Claude account. Open the runner app's settings and choose your Claude account, or run:

spud factory use account
spud factory signin

This opens Claude Code's own sign-in on Anthropic's page. The runner never sees, stores or sends your sign-in: it only asks Claude Code whether it's ready. Using your own subscription this way is for your own work; it's not for running Factory on behalf of other people.

With an API key. Put an ANTHROPIC_API_KEY in the runner's secrets (in the runner app, or see Secrets), then:

spud factory use api-key

Some SpudSuite sites only take turns from runners using an API key. Factory says so when you start a project if that's the case.

#Running commands

By default, Claude Code asks before running commands in a thread, and the thread waits on you. Tick Let threads run any command without asking when you start a project to let them carry on by themselves. Only do this on a machine where that's safe, such as a dedicated server or a container.

#Where the work happens

• The orchestrator works in a main folder: a clone of your repository, or a fresh git repository.
• Each thread gets its own git worktree on a branch named factory/<thread>, so threads don't trip over each other.
• If a runner goes away mid-turn, the turn goes back in the queue and runs again when the runner is back.