Chaos Control is a cross-platform desktop app that gives Claude Code and Codex CLI a unified management surface. It started because I had skills and subagents and MCP servers drifting between the two CLIs and wanted one place to deploy, compare, and reconcile them.
Why it exists
Both CLIs are great. Running them side by side means maintaining two config trees, two skill libraries, two agent definitions, and two MCP registries. Chaos Control lets me author once, deploy to either, and resolve drift with a real diff view instead of guessing.
Highlights
- Dashboard view showing installed counts for plugins, skills, subagents, and MCP servers across both CLIs.
- Operations surface for drift resolution, deploy preview, rollback history, and bundle import/export.
- Skill import from disk + cross-deploy between Claude and Codex formats.
- Subagent, prompt, and CLAUDE.md / AGENTS.md management with visual diffs.
- MCP server unified registry with per-target deploy status and one-click cross-deploy.
- AI Studio — generate skills, subagents, MCP definitions, and prompts using Claude Code or Codex CLI as a subscription-powered subprocess (no API keys required).
- Live file watcher so manual edits show up immediately.
Technical approach
Tauri v2 with a Rust core that calls into Claude Code and Codex CLI as subprocesses. Svelte 5 runes model the dashboard as a reactive view over both CLIs’ on-disk config. The library directory at ~/.chaoscontrol/ is the canonical source; each deploy is a structured write to one or both CLIs. Finder-launched installs resolve subprocess PATH from the app environment first and then fall back to shell PATH, so Homebrew / nvm installs still work outside a login shell.
