cyrus-setup-launch
Skill902 starsChanged 53 days agoApache-2.0View on GitHub
Print a summary of the Cyrus setup and offer to start the agent.
- Reads credentials
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ceedaragents/cyrusword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ceedaragents/cyrus★ 888100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 60
Use ✓ for configured items and ✗ for skipped/unconfigured items.
- Very specific: line 76
Check if pm2 is installed (which pm2).
- Very specific: line 79
Run pm2 startup — this prints a system-specific command.
- Distinctive: line 81
After setup, inform the user of useful commands:
- Distinctive: line 96
Write the service file:
- Distinctive: line 138
If the user configured ngrok in the endpoint step, the agent should start it:
- Distinctive: line 144
If using pm2, also make ngrok persistent:
- Very specific: line 153
If the user's ~/.cyrus/config.json has sandbox.enabled: true, check whether the egress proxy CA certificate is trusted in the system …
- Distinctive: line 161
If sandbox is enabled, check trust status:
- Very specific: line 168
If the cert is found (exit code 0): report ✓ trusted.
- Distinctive: line 169
If not found (exit code 44): inform the user and offer to run the trust command:
- Very specific: line 182
After trusting system-wide, offer to set sandbox.systemWideCert: true in config.json.
- Very specific: line 184
If the user declines system-wide trust, Cyrus still works — it sets cert env vars per-session.
- Very specific: line 194
Should return {"status":"idle"} or similar.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CRITICAL: Never use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. Use only Bash commands (grep, printf >>, etc.) to interact with env files — secrets must never be read into the conversation context.
Setup Launch
Prints a summary of the completed setup and offers to start Cyrus.
Step 1: Gather Configuration
Read current state:
# Base URL
grep '^CYRUS_BASE_URL=' ~/.cyrus/.env 2>/dev/null | cut -d= -f2-
# Linear
grep -c '^LINEAR_CLIENT_ID=' ~/.cyrus/.env 2>/dev/null
# GitHub
gh auth status 2>&1 | head -1
# Slack
grep -c '^SLACK_BOT_TOKEN=' ~/.cyrus/.env 2>/dev/null
# Repositories
cat ~/.cyrus/config.json 2>/dev/null
# Claude auth
grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN)=' ~/.cyrus/.env 2>/dev/nullStep 2: Print Summary
Print a formatted summary:
┌─────────────────────────────────────┐
│ Cyrus Setup Complete │
├─────────────────────────────────────┤
│ │
│ Endpoint: https://your-url.com │
│ Claude: ✓ API key configured │
│ │
│ Surfaces: │
│ Linear: ✓ Workspace connected │
│ GitHub: ✓ CLI authenticated │
│ Slack: ✓ Bot configured │
│ │
│ Repositories: │
│ • yourorg/yourrepo │
│ • yourorg/another-repo │
│ │
└─────────────────────────────────────┘Use ✓ for configured items and ✗ for skipped/unconfigured items.
Step 3: Make Cyrus Persistent
Cyrus needs to run as a background process so it stays alive and restarts after reboots. Use the AskUserQuestion tool if available to ask:
How would you like to keep Cyrus running in the background?
- pm2 (recommended) — Node.js process manager. Simple to set up, auto-restarts on crash, log management built in. Best for most users.
- systemd (Linux only) — OS-level service manager. Starts on boot automatically, managed with
systemctl. Best for dedicated Linux servers.- Neither — just run
cyrusin the foreground for now (you can set up persistence later).
Option 1: pm2
The agent should run all of these commands directly:
- Check if pm2 is installed (
which pm2). If not, install it (npm install -g pm2). - Start Cyrus:
pm2 start cyrus --name cyrus - Save the process list:
pm2 save - Run
pm2 startup— this prints a system-specific command. The agent should run that output command too (it typically requiressudo).
After setup, inform the user of useful commands:
pm2 logs cyrus— view logspm2 restart cyrus— restartpm2 stop cyrus— stop
Option 2: systemd (Linux only)
The agent should run all of these commands directly:
- Resolve the actual values for the service file:
CYRUS_BIN=$(which cyrus) CYRUS_USER=$(whoami) - Write the service file:
sudo tee /etc/systemd/system/cyrus.service > /dev/null << EOF [Unit] Description=Cyrus AI Agent After=network.target [Service] Type=simple User=$CYRUS_USER EnvironmentFile=/home/$CYRUS_USER/.cyrus/.env ExecStart=$CYRUS_BIN Restart=always RestartSec=10 [Install] WantedBy=multi-user.target EOF - Enable and start:
sudo systemctl daemon-reload sudo systemctl enable cyrus sudo systemctl start cyrus
After setup, inform the user of useful commands:
sudo systemctl status cyrus— check statussudo journalctl -u cyrus -f— view logssudo systemctl restart cyrus— restart
Option 3: Foreground
Run directly:
cyrusStep 4: Start ngrok (if applicable)
If the user configured ngrok in the endpoint step, the agent should start it:
ngrok start cyrusIf using pm2, also make ngrok persistent:
pm2 start "ngrok start cyrus" --name ngrok
pm2 saveStep 5: Sandbox CA Certificate Trust (if sandbox enabled)
If the user's ~/.cyrus/config.json has sandbox.enabled: true, check whether the egress proxy CA certificate is trusted in the system keychain.
Check if sandbox is enabled:
grep -o '"enabled":\s*true' ~/.cyrus/config.json 2>/dev/null | head -1If sandbox is enabled, check trust status:
# macOS — check System keychain for the Cyrus CA
security find-certificate -c "Cyrus Egress Proxy CA" /Library/Keychains/System.keychain 2>&1- If the cert is found (exit code 0): report ✓ trusted. Offer to set
sandbox.systemWideCert: truein config.json to skip per-session cert env vars. - If not found (exit code 44): inform the user and offer to run the trust command:
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ~/.cyrus/certs/cyrus-egress-ca.pemOn Linux, check with test -f /usr/local/share/ca-certificates/cyrus-egress-ca.crt. If not present:
sudo cp ~/.cyrus/certs/cyrus-egress-ca.pem /usr/local/share/ca-certificates/cyrus-egress-ca.crt
sudo update-ca-certificatesAfter trusting system-wide, offer to set sandbox.systemWideCert: true in config.json. This skips per-session cert env vars (NODE_EXTRA_CA_CERTS, GIT_SSL_CAINFO, etc.) since the OS cert store handles trust for all tools.
If the user declines system-wide trust, Cyrus still works — it sets cert env vars per-session. But some tools (Bun, .NET, curl on macOS with SecureTransport) will only work with system-wide trust.
Step 6: Verify Running
Once Cyrus starts, verify it's listening:
curl -s http://localhost:3456/statusShould return {"status":"idle"} or similar.
Then try assigning a Linear issue to Cyrus, or @mentioning it in Slack, to verify the full pipeline works!
Completion
✓ Cyrus is running and ready. Assign a Linear issue or @mention in Slack to test it out!
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

