cmux-customization

Customize cmux.json actions, UI layout, dock controls, and terminal behavior.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill cmux-customization-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-customization
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/cmux-customization
Command: npx skills add https://github.com/selfagency/agentsy --skill cmux-customization-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you safely customize cmux so your workspace buttons, actions, layouts, dock controls, notifications, routing, shortcuts, and terminal preferences match how you work.

Core Features & Use Cases

  • End-user cmux config customization: update cmux.json actions, command palette entries, plus-button behavior, and surface tab bar buttons without clobbering unrelated sections.
  • Workspace and UI layout control: define commands that open specific workspaces (splits, multiple terminals, browsers, SSH sessions) and update workspace metadata via the cmux CLI/tools.
  • Dock + sidebar + app behavior: manage .cmux/dock.json (project) or ~/.config/cmux/dock.json (global) for terminal controls, plus supported cmux-settings behaviors for notifications, routing, automation, and shortcuts.
  • Validation-first workflow: back up user-owned config, apply the smallest diff, validate JSON/JSONC shape, validate settings via cmux-settings, and reload config after changes.
  • Terminal preference alignment: use Ghostty configuration for terminal rendering and keybindings, keeping cmux changes scoped to cmux-owned concerns.

Quick Start

Ask an AI to apply the smallest safe edit to your project-local .cmux/cmux.json (or app-global ~/.config/cmux/cmux.json) to implement the exact UI/action/layout change you want, including a validation and rollback plan.

Frequently Asked Questions about cmux-customization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize cmux UI layout and dock controls?

You customize cmux UI layout and dock controls by editing `cmux.json` or `.cmux/dock.json` files to define workspace commands, tab bar buttons, and terminal preferences. The process involves backing up user-owned config, applying the smallest diff, validating JSONC shape, and reloading config.

Can I add custom command palette entries and actions to cmux?

Yes, you can add custom command palette entries and actions to cmux by updating the `cmux.json` configuration file. This allows you to define commands that open specific workspaces like splits, multiple terminals, browsers, or SSH sessions without clobbering unrelated sections.

What is the safest way to update cmux configuration files?

The safest way to update cmux configuration is using a validation-first workflow. This requires inspecting the current config scope, backing up user-owned files, making schema-backed JSONC edits with validation via `cmux-settings`, and reloading to verify the configured entrypoints and bindings.

Does cmux customization work with Ghostty terminal configuration?

Yes, cmux customization works alongside Ghostty terminal configuration. You use Ghostty configuration for terminal rendering and keybindings, while keeping cmux configuration changes scoped strictly to cmux-owned concerns like workspace layouts, actions, and dock controls.

How do I configure project presets using .cmux files?

You configure project presets using `.cmux` files by defining workspace metadata and commands that open specific workspaces such as splits, multiple terminals, browsers, and SSH sessions. These project-local files allow you to manage terminal controls via `.cmux/dock.json`.

Why are my cmux settings not working after editing the config?

If cmux settings are not working after editing the config, it may be due to invalid JSONC shape or missing validation. You must validate settings via `cmux-settings`, ensure the smallest safe diff was applied, and reload the configuration to verify that the configured entrypoints and bindings are active.