The console

The console is where you see the factory at work and answer what waits for you. On Tares Cloud it is your workspace’s address; on your own machine it is http://127.0.0.1:8787 .

The menu on the left holds Home, Projects, Tickets, Reviews, Crew, Docs and memory, People and, at the bottom, Settings. The header has search and your account.

Home

Home answers one question: what needs you now? It refreshes every 15 seconds.

• Get your factory going shows on a new Tares: sign in from Claude Code, connect GitHub, connect Linear or GitHub Issues, start the crew, and write your first spec. Each row ticks itself off. Hide this list puts it away, and Show it again brings it back.
• Waiting for you puts what holds the crew up first, under The crew is waiting on you: a question that blocks work, a command the crew was refused, a pull request waiting for your merge. Below it, When you have a moment holds the rest, and anything older than a week folds away. Each row says who it is from.
• Projects lists your open projects with their progress.
• Your crew shows your crew’s stations and what they are on.
• Your Claude plan shows how much of your plan’s limits the crew has used.
• Connected shows each tool and what it is connected to: GitHub, Linear, Slack and Claude Code. A chip opens its settings.

You answer most things right on the page:

On a team, Home shows what is addressed to you and who it comes from, a Mine and Team switch on Projects, and the projects you lead that wait on someone else. Teams

Projects

Every project as one row: its goal, state, current milestone, tickets merged and blocked, repos and last activity. Filter by state, search by name, and close a project whose tickets are all merged. Projects kept for later wait under Later.

New project gives you the tares factory spec command to start a spec in Claude Code, with what you want to build filled in. Plan a project

A project’s page

Open a project to see where it stands, top to bottom:

• Stages, from spec to done, and how many tickets are in each state.
• Waiting for you on this project.
• Moving now: the tickets in progress and in review, and the next ticket.
• Milestones, one row each with its counts and a link to its tickets.
• Decisions you made and the crew’s open calls: the choices it made on its own, which you keep or change.
• Pull requests: the three newest, and a link to the project’s GitHub page.
• Docs: the spec, the plan, the project’s AGENTS.md and memory.
• Work on it yourself: the command that opens a session on the project.
• People: the lead, whether the project is for the team or private, and its members.
• Delete this project, at the foot of the page, after you type its name. Its tickets, decisions, calls and docs go. Pull requests and branches on GitHub stay.

The GitHub page lists every pull request the project’s tickets opened, grouped by repo: open, merged or closed without merging, each with its ticket, CI, the crew’s review, the size of the change and who merged it.

Tickets

The tickets of every project in one place, wherever they live, as a Board, a List or Swimlanes. Filter by project, milestone, state or text, and sort by newest, oldest or ref. The filters stay in the address, so a view can be shared as a link.

A ticket’s page holds its pull request, its reviews and findings, its checks, the calls and decisions about it, what it depends on and what it blocks, who works on it, its history and working notes, and the command that opens its builder’s session under Open in a terminal.

Reviews

Every pull request in review, across projects, oldest first, with the reviewer’s verdict, CI and the milestone it holds up.

• Waiting for you: passed by the reviewer and waiting for your merge.
• With the crew: folded, each with who has it next (the reviewer, the builder, CI or the crew’s merge).
• Nobody is on it: each with the reason, such as a finished project, a project never handed to the crew, one you took over, a pull request closed without merging, or one the reviewer blocked.

Crew

Who is on the crew by role (Orchestrator, Reviewer, Releaser and Builders grouped by project), what each is doing and when it was last heard. A station is working, idle, waiting for you, not heard for a while, or ended. An idle station needs nothing; it is between ticks or waiting on a peer, and resumes by itself.

The page also shows:

• Autonomy: how far the crew may go. Run the crew
• Claude plan: your plan’s use, with each project’s share.
• Rules the crew proposes: rules the reviewer suggests from what it keeps finding, each with Accept and Reject.
• Standup: what moved in each project since yesterday, over the last 7 days, or between dates you pick, with a short summary. Copy it, or send it to a Slack channel.

On a team, the page lists every person’s crews, yours first, each with its machine and stations. Crews not seen for a day fold under Not seen recently.

Docs and memory

What every session reads. For every project: the crew’s shared rules (AGENTS.md) and memory. Then each project’s spec, plan, rules and memory. Each memory line says who wrote it and when, and you can add a line from the page. Your own rules and memory, which only you see, show under Only you see these.

People

Who is on the Tares, whether they have signed in, the projects they lead and the repos they own. Add a person invites someone: on Tares Cloud, with the workspace’s invite; on your own Tares, an admin adds them. A person’s picture shows where the console shows them. Teams

Settings

Settings is one page with a sidebar of groups, one open at a time.