Claude‑Ops – A Business‑Operating System for Claude Code

What it is (in plain language)

Claude‑Ops is a plugin‑plus‑installer package that turns the Claude Code editor/CLI into a full‑stack operations dashboard for a software business. Once installed, a single command (/ops:go) shows you a colour‑coded, terminal‑style snapshot of:

• infrastructure health (ECS, RDS, Redis, etc.)
• CI/CD pipeline status
• inbox messages across Slack, Telegram and Gmail
• open pull‑requests and sprint progress
• real‑time revenue numbers pulled from Stripe, RevenueCat and AWS

The system also ships a set of “agents” that can act autonomously – e.g. auto‑fix failing deployments, merge PRs, rotate Claude accounts, or place outbound voice calls via Twilio or Bland AI.

Core pieces

Component	What it does	How you get it
Plugin (ops)	Adds 66 “skills” (commands) that expose dashboards, automation and integrations.	/plugin install ops@ops‑marketplace
Installer / harness	Detects which Claude‑compatible CLIs you have (Claude Code, Codex, Gemini, OpenClaw, Hermes, OpenCode, etc.) and mirrors the same skill set into each one.	node bin/claude‑ops‑installer.mjs install
Background daemon	A launchd service that keeps a warm cache, polls health endpoints, and runs safety hooks (secret‑scan, rm‑rf guard, etc.).	Started automatically by the wizard (/ops:setup).
Specialist agents	Small autonomous LLM‑driven workers (e.g. “yolo” C‑suite agents) that can execute tasks like auto‑fixing a broken deploy or rotating Claude Max accounts.	Invoked via /ops:yolo, /ops:orchestrate, etc.

Main user workflow

1. Add the marketplace – tells Claude where to find the plugin.
2. Install the ops plugin (and optionally the desktop‑act companion).
3. Run /ops:setup – a guided wizard that configures integrations (GitHub, AWS, Stripe, etc.), installs the daemon and warms the cache.
4. Run /ops:go – instantly see a “morning briefing” with all the business‑critical metrics.
5. Use the other /ops:* commands to dive deeper (inbox, merge, revenue, marketing, voice calls, etc.) or let the autonomous agents act on your behalf.

Notable features (as described in the README)

• Auto‑fix subsystem – after a PR merge, the plugin can poll the deployment, verify health, and if it fails automatically rerun the workflow or dispatch a Haiku‑based fixer. Budget caps and deduplication prevent runaway costs.
• Safety hooks – always‑on checks that block dangerous commands, scan for secrets, and warn before pushing to main.
• Multi‑account Claude Max rotator – rotates between several Claude accounts with a launchd daemon to avoid rate‑limit bursts.
• Voice & video surface – /ops:voice can place native Phone.app calls, start Zoom meetings, send Twilio SMS, or make AI‑agent calls via Bland AI, with TTS/ transcription powered by ElevenLabs and Groq Whisper.
• Unified inbox – aggregates Slack, Telegram, Gmail and other channels into a single /ops:inbox view.
• Revenue dashboard – pulls Stripe, RevenueCat and AWS billing data into /ops:revenue.
• Marketing integration – connects to Windsor.ai, Klaviyo, Meta Ads, GA4, GSC, etc., exposing a /ops:marketing command.
• Skill parity checker – ops-update --check verifies that every supported Claude‑compatible CLI loads the exact same skill binaries.

Who would use it?

• Small‑to‑medium SaaS teams that already rely on Claude Code (or other Claude‑compatible CLIs) for development and want a single terminal‑based control plane for ops, finance and communications.
• Engineers who prefer keyboard‑first workflows over web dashboards.
• Companies that need automated safety and auto‑fix mechanisms for CI/CD without building custom scripts.

Limitations / things to watch

• The product is tightly coupled to the Claude ecosystem (Claude Code, Claude.ai accounts, etc.). It won’t run on unrelated editors without the provided installer.
• Many integrations require API keys or OAuth tokens (Stripe, RevenueCat, WhatsApp, etc.). Those must be supplied during the wizard.
• The auto‑fix and autonomous agents are add‑ons; they can be disabled if you prefer manual control.
• The README mentions a “desktop‑act companion” but does not detail its UI; it appears optional.

Quick start recap (from the README)

# add marketplace
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops

# install plugin (and optional companion)
/plugin install ops@ops-marketplace

# run the guided wizard – sets up integrations, daemon, skill mirroring
/ops:setup

After that, a single /ops:go gives you the full business snapshot.

---

All information above is taken directly from the repository’s README; no external assumptions have been added.