Cmux Socket Policy

If you're working on cmux socket or CLI commands, this enforces two critical rules: don't block the main thread with telemetry spam, and don't steal focus from the user. It's specific about which commands get main-thread access (AppKit/Ghostty UI manipulation) versus what should run off-main (telemetry parsing, deduplication). The focus policy is strict: only explicit focus-intent commands like window.focus or workspace.select can touch focus state. Everything else must preserve user context. It's opinionated architecture guidance that prevents the two most common ways socket commands turn into laggy, disruptive experiences.

skills.sh installs: 4.9K
GitHub stars: 28.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add manaflow-ai/cmux --skill cmux-socket-policy --agent claude-code

Installs into .claude/skills of the current project.

Files

cmux Socket Policy

Threading policy

Do not use DispatchQueue.main.sync for high-frequency socket telemetry commands such as report_*, ports_kick, status/progress updates, or log metadata updates.
For telemetry hot paths, parse and validate arguments off-main.
Dedupe and coalesce off-main first.
Schedule minimal UI/model mutation with DispatchQueue.main.async only when needed.
Commands that directly manipulate AppKit/Ghostty UI state are allowed to run on the main actor.
If adding a new socket command, default to off-main handling and require an explicit reason in code comments when main-thread execution is necessary.