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 plan: Pro Plan

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

Team Plan

• Repository cloned into hosted Cyrus infrastructure

This is managed automatically.

---

​

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. Open the repository in the dashboard
2. Click Delete Repository
3. Confirm deletion

---

​

What’s Next

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

Cyrus Community

Get support on Discord