back
loading skill details...
Customize cmux for an end user. Use when changing cmux.json actions, custom commands, workspace layouts, plus-button behavior, surface tab bar buttons, Command…
cmux Customization Keep the user's config intact, prefer schema-backed edits, and validate before reporting completion. Choose the right surface Want to change Edit App preferences (appearance, sidebar, notifications, browser routing, automation, shortcuts, new-workspace placement) ~/.config/cmux/cmux.json via the cmux-settings helper Custom actions, workspace layouts/commands, tab bar buttons, plus-button behavior, Command Palette entries, notification hooks ~/.config/cmux/cmux.json globally or .cmux/cmux.json in the project Dock controls (right-sidebar terminals: logs, test watchers, git TUIs, dev servers, queues, cmux feed tui --opentui) .cmux/dock.json or ~/.config/cmux/dock.json; cmux docs dock when available Terminal rendering and terminal keybindings (fonts, themes, cursor style, copy-on-select, shell integration) Ghostty config, usually ~/.config/ghostty/config Workspace names, descriptions, colors, read state, sidebar metadata cmux CLI, see ../cmux-workspace/SKILL.md Feed event sources cmux hooks setup Project-local .cmux/cmux.json and .cmux/dock.json let worktree, SSH, review, dev, CI, and docs patterns travel with the repo; project actions and commands override global entries with the same ID or name. Global app preferences do not belong there. If a request can be handled by Ghostty config, say so and use Ghostty config instead of inventing cmux UI settings.
don't have the plugin yet? install it then click "run inline in claude" again.