Where tickets live

A project’s tickets live in one of three places. You choose when you write the spec, and the crew works the same way in all of them.

Where	Choose it when	What you set up
Tares	You want nothing else to set up.	Nothing.
Linear	Your team plans in Linear.	Connect Linear once.
GitHub Issues	Your team tracks work in a GitHub repo.	A GitHub credential that reads issues, and `gh` with the `repo` scope.

With Linear or GitHub Issues, sessions create and change the tickets there, and Tares reads them about once a minute to keep the project’s ticket list in step. Tares never writes to Linear or GitHub. A ticket closed in its home is closed everywhere, and the crew stops working on it.

Linear

Connect Linear under Settings, Tools, Linear:
- On Tares Cloud, choose Connect Linear and approve the Tares app in Linear.
- On your own Tares, paste a personal API key (in Linear: Settings, Security and access, Personal API keys). Read access is enough.
Give the spec session Linear’s own MCP tools: a linear MCP server in Claude Code, or your Linear connector.
When the spec asks where the tickets live, say Linear and name the Linear project.

To link a project that already exists, ask a session with the Tares plugin to call link_linear_project with the Linear project’s name.

Linear connector has what syncs and the events each change records.

GitHub Issues

Add a GitHub credential under Settings, Tools, GitHub that can read the repo’s issues.
Sign in to gh with the repo scope on the machine that runs the sessions:
```
gh auth login --scopes repo
```
When the spec asks where the tickets live, say GitHub Issues and name the repo. Claude creates the issues with gh, under the label tares:<project>, and links the project.

GitHub owns these tickets: change a ticket’s title, state, order, milestone or dependencies with gh. To link a repo yourself, ask a session to call link_github_issues with the repo and, optionally, the issue label.

GitHub Issues connector has how issues map to tickets and what happens when GitHub cannot be reached.

Who a ticket is assigned to

On a team, every ticket has an assignee. Linear maps the assignee’s email, GitHub Issues maps the first assignee’s GitHub login, and the spec assigns each Tares ticket to the owner of its repo. A person’s crew works on the tickets assigned to them. Teams

All tickets in one place

The console’s Tickets page lists the tickets of every project, wherever they live, as a board, a list or swimlanes. The console