Skip to main content
Cyrus intentionally limits user-facing configuration. This page documents what is automatically handled, so you don’t have to think about it.

​
Infrastructure

Pro Plan
  • Local repository paths
  • Worktree lifecycle
  • Process management
Team Plan
  • Hosted compute
  • Networking and domains
  • Scaling and resource allocation
All infrastructure is provisioned and maintained by Cyrus.

​
AI Model Selection

Cyrus runs on high-quality defaults so you don’t have to think about model selection. By default, all tasks use Claude Opus 4.5, which delivers the strongest reasoning and best results with no setup required. Defaults
  • Primary: Claude Opus 4.5 (highest-quality reasoning)
  • Fallback: Claude Sonnet 4.5 (fast, reliable)
Optional Overrides In some cases, you may want to trade quality for speed or cost. You can do this explicitly by applying a model label:
  • sonnet → Faster, reliable execution
  • haiku → Lightweight, cost-efficient tasks
Most users will never need to change this.

​
Tool Permissions

Cyrus enables a safe, limited toolset for AI reasoning:
  • File read/write
  • Git operations
  • GitHub CLI
  • Task and planning tools
  • Web fetch and search
Permissions are scoped and audited.

​
Setup Scripts (Optional)

​
Repository Setup Script

You may add a cyrus-setup.sh file to your repository root. This script runs when Cyrus creates a new worktree and is useful for:
  • Installing dependencies
  • Bootstrapping environments
  • Running checks
See: Setup Scripts

​
Global Setup

Team-wide setup is handled automatically and does not require configuration.

​
Design Philosophy

If something isn’t configurable, it’s intentional. Cyrus optimizes for:
  • Predictable behavior
  • Minimal setup
  • Fewer footguns
As new configuration becomes user-relevant, it will be documented here.

​
What’s Next

If something isn’t behaving as expected fOjhOFI

Cyrus Community

Get support on Discord