Cyrus Setup

One-command setup for self-hosted Cyrus. This orchestrator walks you through everything needed to run Claude Code as a background agent from Linear, Slack, and GitHub.

CRITICAL Rules

Never Read or Write ~/.cyrus/.env Directly

FORBIDDEN: Do NOT use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. This file contains secrets (API keys, tokens, signing secrets). All interaction with this file MUST go through Bash commands (grep, printf >> ..., etc.) which the user can see and approve. Never read its contents into the conversation context.

Browser Automation

The goal of browser automation in this skill is to reduce sign-in and setup fatigue — the agent navigates web UIs, fills forms, and scrapes credentials so the user doesn't have to do it all manually.

Three modes, in order of preference:

1. claude-in-chrome (preferred when available) — if the user is running Claude Code and has the claude-in-chrome MCP extension connected, use it. This has the huge advantage of using the user's existing Chrome with all their signed-in sessions (Linear, Slack, GitHub). Check availability by seeing if mcp__claude-in-chrome__* tools exist.
2. agent-browser CLI — a standalone Playwright-based binary invoked via Bash. Requires launching a fresh Chrome profile with remote debugging enabled (the user will need to sign in to services in that profile). Check with which agent-browser.
3. Manual guided flow — the user follows the agent's step-by-step instructions and does the clicks themselves. Always available as Path B in each sub-skill.