Run autonomous, self-running Claude Code sessions

Tares runs a software factory for Claude Code: a crew of Claude Code sessions that run in the background on your machine. A watch brings back any session that stops, the orchestrator checks for work on a schedule, and builders merge reviewed pull requests, so the work continues while you are away. The crew asks you before the decisions that are yours.

How the sessions keep running

Claude Code stops an idle session after about an hour. Tares plans for that:

• tares factory crew up starts the crew and a watch in the background. The watch brings back any station that stops, under the same name. Its log is ~/factory/watch.log.
• The orchestrator wakes on a schedule every 20 minutes and checks for work, so an idle crew still notices a new project, a stalled ticket or a merged pull request that unblocks the next one.
• A revived session reads its notes and the project on Tares, so it carries on from where the last one stopped. Tares keeps the plan, the tickets, the reviews and your answers.

tares factory crew down stops every station. Tares keeps the projects, tickets and answers, and tares factory crew up starts fresh sessions that carry on from them.

How work gets picked up

You plan a project with Claude, and Tares keeps the plan as tickets, each with the repo it changes. After that you do not assign anything.

• The orchestrator hands out work and starts builders itself, one per milestone and repo of a project.
• A builder takes its tickets, opens pull requests and merges its own once they pass.
• The reviewer reviews every pull request to a fixed bar and posts the verdict.

What still needs you

The crew does not guess at decisions that are yours. The orchestrator is the session you talk to, and it brings you what needs you, one question at a time and with a recommendation.

• Questions wait on the desk until you answer them. When the plan does not answer a smaller question, the crew records an assumption and carries on, and the orchestrator confirms the assumptions with you once per milestone.
• Merging is your setting. At L4-ship, a builder merges once the reviewer approves and CI is green. At L3-review, every merge waits for your yes.
• Releasing is off unless you ask for it. Without a releaser, the crew stops when work is merged to main.

To answer, attach to the orchestrator:

tares factory crew attach orchestrator

Start a crew

Install Tares, bring up the crew, then plan a project. On Tares Cloud, sign in once with tares login:

uv tool install tares     # or: brew install glassflow/tap/tares
tares login
tares factory crew up
tares factory spec "what you want to build"

To run Tares on your own machine instead, replace tares login with tares up and start the MCP endpoint the sessions share. Build a software factory with Claude Code has the Local and Tares Cloud setup, what you need on your machine and the commands to watch the crew.