cmux-socket-policy

Source excerpt starting at line 1.

1---2name: cmux-socket-policy3description: "Socket command threading and focus policy for cmux CLI/socket work. Use when adding or changing socket commands, CLI commands, telemetry commands, focus/select/open/close/send-key behavior, or automation that could steal app focus."4---5 6# cmux Socket Policy7 8## Threading policy9 10- Do not use `DispatchQueue.main.sync` for high-frequency socket telemetry commands such as `report_*`, `ports_kick`, status/progress updates, or log metadata updates.11- For telemetry hot paths, parse and validate arguments off-main.12- Dedupe and coalesce off-main first.13- Schedule minimal UI/model mutation with `DispatchQueue.main.async` only when needed.14- Commands that directly manipulate AppKit/Ghostty UI state are allowed to run on the main actor.15- 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.16 17## Focus policy18 19- Socket/CLI commands must not steal macOS app focus.20- Do not activate the app or raise windows unless the command has explicit focus intent.21- Only explicit focus-intent commands may mutate in-app focus/selection.22- Explicit focus-intent commands include `window.focus`, `workspace.select/next/previous/last`, `surface.focus`, `pane.focus/last`, browser focus commands, and v1 focus equivalents.23- All non-focus commands should preserve the current user focus context while still applying data/model changes.24 25## Detailed reference26 27- Read [references/threading-and-focus.md](references/threading-and-focus.md) when adding a command, changing command execution context, or deciding whether focus changes are allowed.28