> ## Documentation Index
> Fetch the complete documentation index at: https://atcyrus.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

# cuConfiguration

Cyrus configuration is fully managed through the web dashboard at [https://app.atcyrus.com](https://app.atcyrus.com). All settings are stored securely and automatically synced to your Cyrus infrastructure.

## Configuration dashboard

Access your configuration at:

* **Repositories**: [https://app.atcyrus.com/repos](https://app.atcyrus.com/repos)
* **Settings**: [https://app.atcyrus.com/settings](https://app.atcyrus.com/settings)

## Repository configuration

Configure repositories through the web dashboard to control how Cyrus processes Linear issues for each codebase.

### Adding a repository

1. Navigate to [Repositories](https://app.atcyrus.com/repos)
2. Click "Add Repository"
3. Select from one of the allowed repositories
4. Choose routing option

**Pro Plan**: Cyrus will clone the repository to `~/.cyrus/repos/{name}` on your machine

**Team Plan**: Cyrus will clone the repository to the hosted infrastructure

### Repository settings

Each repository has the following configuration options:

#### Basic settings

* **Active/Inactive**: Toggle whether Cyrus monitors this repository
* **Default Branch**: Branch to base new worktrees on (usually `main` or `master`)

#### Routing configuration

Control which Linear issues are routed to this repository:

**Linear Team Keys**

* Select which Linear teams' issues should be processed in this repository
* Multiple teams can be assigned to one repository
* Issues must be from one of the selected teams to be processed

**Routing Labels**

* Linear labels that trigger processing in this repository
* Useful for splitting work within a Linear team (e.g., "frontend" vs "backend" labels)

### Deleting a repository

1. Navigate to the repository in the dashboard
2. Click "Delete Repository"
3. Confirm deletion

**Warning**: This removes the repository configuration and cloned code. Ensure you've pushed all important changes first.

## API keys & authentication

Manage API keys through the settings dashboard:

### Claude Code API key

Required for AI functionality:

1. Get your API key from [console.anthropic.com](https://console.anthropic.com/)
2. Navigate to [Settings](https://app.atcyrus.com/settings)
3. Update your Claude API key
4. Changes apply immediately

### GitHub integration

Managed during onboarding:

* **GitHub OAuth**: Your GitHub identity
* **GitHub App**: Repository access for Cyrus
* **GitHub Token**: Automatically refreshed

### Linear integration

Connected during onboarding:

* **Linear OAuth**: Workspace access
* **Linear Webhook**: Automatic issue monitoring
* **Team Selection**: Choose which teams Cyrus monitors

## Advanced configuration

The following configuration is automatically managed by Cyrus infrastructure. As we add more user-facing configuration options, they will be documented here.

### Automatically managed settings

**Pro Plan:**

* Repository paths: `~/.cyrus/repos/{name}`
* Worktree paths: `~/.cyrus/worktrees`

**Team Plan:**

* Infrastructure provisioning
* Domain setup
* Network configuration
* Resource allocation

### Default models

Cyrus automatically selects appropriate AI models:

* **Primary Model**: Claude Sonnet (balanced performance)
* **Fallback Model**: Claude Haiku (faster, cost-effective)

### Tool permissions

Base tools available to Claude:

* Read files
* Edit files
* Task management
* Web search and fetch
* Todo and notebook operations
* Git operations
* GitHub CLI operations

### Setup scripts

**Repository Setup Script**: Place a `cyrus-setup.sh` script in your repository root to run initialization tasks when Cyrus creates new worktrees. See [Setup Scripts](setup-scripts.md) for details.

**Global Setup Script**: Managed automatically by Cyrus infrastructure for team-wide configuration.

## Troubleshooting

### Configuration changes not applied

**Pro Plan:** Make sure that the `cyrus` process is running.

**Team Plan:** Configuration changes apply immediately to the hosted infrastructure.

### Repository not processing issues

Check:

1. Repository is marked as "Active"
2. Issue is assigned to the Cyrus agent in Linear
3. Issue is from one of the configured teams

### API key issues

* Ensure Claude API key is valid at [console.anthropic.com](https://console.anthropic.com/)
* Verify you have sufficient credits
* Check API key hasn't been rotated or revoked

## Getting help

Need assistance with configuration?

* **Discord**: [Join our community](https://discord.com/invite/prrtADHYTt)
* **Email**: Pro and Team Plan subscribers receive priority support
* **GitHub**: [Report issues](https://github.com/ceedaragents/cyrus)

***

Next: [Labels & Routing](labels.md)