← ClaudeAtlas

cmuxlisted

Manage Stephen's 30-50 Claude Code sessions running in cmux workspaces. Use when asked "which session/workspace handles X", to delegate a task to another session, foreground a workspace, prep for a call using another session's context, get a status roll-up across all sessions, or trace a running process to its owning session. Also invocable as /cmux with subcommands who-owns, delegate, status, brief.
smorrel1/claude-code-skills · ★ 2 · Web & Frontend · score 65
Install: claude install-skill smorrel1/claude-code-skills
# cmux Session Management Binary: `CMUX=/Applications/cmux.app/Contents/Resources/bin/cmux` ## Who owns a topic / contact / process Run `scripts/who_owns.py <keywords>` (or `--pid <pid>`). It searches `~/.claude/history.jsonl` (survives transcript deletion) plus transcript grep, and maps PIDs via `CLAUDE_CODE_SESSION_ID` env. Then: 1. Check `references/registry.md` first for an instant answer; update it with anything newly learned. 2. Map session -> workspace: transcript cwd/project narrows it; live processes give a tty; `$CMUX tree --all` maps tty -> workspace ref and title. 3. Verify by topic, not keyword density: read the candidate's first user message and last assistant message before asserting a match. Short substrings of a name or acronym produce false positives. 4. If no transcript exists, the session was auto-deleted; its prompts survive in history.jsonl. Say so explicitly. ## ALWAYS refer to workspaces by NAME, never by number (Stephen, 4 Sep 2026) In all user-facing text, identify workspaces by their title ("Accountant", "my ai tools", "grant applications"), never "workspace:16". Numbers are for tool calls only; they drift across restarts and mean nothing to Stephen. ## Choosing the target: task NATURE beats topic ownership Route by what kind of work it is, rather than by whose content it touches: - **Content work** (drafts, briefs, analysis) -> the session with the richest topic context. - **Debugging / tooling / pipeline failures** (broken attachments, co