Managing Repositories

Repositories tell Cyrus where it is allowed to work and which issues belong there. This page shows how to add, update, and remove repositories — and how routing rules affect behavior.

---

​

Add a repository for Cyrus to work in

1. Go to https://app.atcyrus.com/repos
2. Click Add Repository
3. Select a repository from the allowed list
4. Choose a routing configuration
5. Save

Once active, Cyrus can route matching issues to this repository.

---

​

Where code lives

Where Cyrus clones and works depends on your runtime: Self-host Runtime

• Repository cloned locally to ~/.cyrus/repos/{name}

Cloud Runtime

• Repository cloned into hosted Cyrus infrastructure

---

​

Control how Cyrus uses this repository

Each repository has basic controls:

​

Active / inactive

• Active: Cyrus may route issues here
• Inactive: Repository is ignored entirely

​

Default branch

• Branch used to create new worktrees
• Usually main or master

---

​

Decide which issues go to this repo

Routing is based on Linear metadata.

​

Linear teams

• Select one or more teams
• Only issues from these teams are considered

​

Routing labels

• Optional but strongly recommended
• Used to split work within a team
• Example: frontend, mobile, api

Issues must match both team and label rules.

---

​

Remove a repository

1. Go to the Repos page
2. Find the repository’s card and click the more (three dots) icon
3. Select Remove from the dropdown
4. Confirm removal

---

​

What’s next

Repositories define where Cyrus can work.
Next, use labels to control what it works on and how