Tares

Always-on AI agents, as a Software Factory or an AI SRE.

Tares comes in two editions, and each Tares you create is one of them. As a Software Factory, a crew of Claude Code sessions takes your projects from a spec to pull requests merged on main. As an AI SRE, agents watch your services and tell you what broke and why. Both keep what they decide (plans, tickets, reviews, incident notes, your answers) for the next reader, human or agent.

Software Factory

You plan a project with Claude Code. A crew of Claude Code sessions on your machine builds it: an orchestrator hands out the tickets, builders open pull requests, a reviewer holds every change to a fixed bar, and a change merges once it passes review and CI. You talk to one session, and only for the decisions that are yours.

• Plan once: a spec, milestones with acceptance checks, and tickets with a working doc each, kept on Tares, Linear or GitHub Issues.
• Build in parallel: one crew serves every project, with a builder per milestone and repo.
• See it all in one place: the console shows what waits for you, each project's progress, the tickets, the pull requests in review and the crew at work.
• Nothing is lost: tickets, reviews, the crew's calls and your answers live on Tares, so the crew carries on after a restart and you can check every choice it made.
• Work as a team: each person runs their own crew on the same Tares, with project leads, private projects and repo owners the spec asks instead of guessing.

uv tool install tares                         # or: brew install glassflow/tap/tares
tares login                                   # sign in to your Tares Cloud workspace (or run `tares up`)
tares factory crew up                         # start the crew; the first run asks how far it may go
tares factory spec "what you want to build"   # in your repo: plan the project and hand it over

Needs Claude Code (signed in, on a plan with background sessions) and gh with write access to your repos.

→ Get started, The console, Teams, A project, end to end

AI SRE

Connect your logs, metrics, alerts, traces and deploys. Tares puts every event about a service on one timeline, a watcher checks every service on a schedule, and when something looks wrong an investigator writes an incident note: what is failing, the likely cause, the evidence and the next step. The note lands in Slack, where your team takes it, resolves it, or says whether it was worth raising.

uv tool install tares     # or: brew install glassflow/tap/tares
tares up                  # choose 2) AI SRE; console on http://127.0.0.1:8787

→ Get started, Tutorial: build an AI SRE

Tares Cloud or your own machine

Tares Cloud is the managed version: create a Software Factory or AI SRE workspace, and it is ready in about a minute. Team features are included.

On your own machine, tares up runs the same open source Tares: one daemon and one DuckDB file, with no external database, no broker and no telemetry. To run it on your private cloud for a team, use the enter

... View full README on GitHub