hev factory

Stop prompting Claude directly.

hev factory orchestrates a crew of coding agents on a Mac you own: a front desk that takes the work, a loop that breaks an approved RFC into tasks, and a worker per task in its own session. It is for work that takes longer than one session and spans more than one repo. You approve a plan, and it reports what needs you.

Three abstractions

Reception is the desk you talk to, and talking to it is how this is meant to be used: bring it a half-formed idea and it argues back until there is an RFC worth approving. It writes the RFC up and never approves it.

An RFC is the unit of approval. A plan enters the factory when it lands in plans/active/, and you are the one who puts it there: either by merging the pull request that adds it, or, on a factory wired to Linear, by moving its issue into the one state that means approved. The factory does everything else, and is barred from exactly that one act.

The gaffer is the parent agent for one factory, and its loop is the beat. Each beat reads the plans you approved, breaks them into tasks, dispatches a worker per task into its own tmux session, checks what came back, and reports what needs you.

Above all three sits the picker, the one screen you leave open, where watching becomes steering the moment you start typing.

What it does not ship

No model, and it never sees your API keys. Reception, the loop and every worker run claude on the subscription you already hold. Every agent is a tmux session, which is why you can attach to any of them mid-task and take over by typing.

Three things it deliberately leaves to you each have a known file name that either exists or does not: a runtime that runs a beat somewhere else, an identity per role instead of one account, and wherever you want the status block sent. If the file is absent the factory does the local thing and keeps going. The fourth seam is the gaffer’s own instructions, which are always there and always yours. One page: where it plugs in.

That fourth one is why there is no configuration language here. The gaffer’s entire behaviour is one file of prose you read and edit, so changing how a factory operates is a commit against a document you already understand.