cmux-settings

Edit and validate cmux.json configuration using schema-aware JSON-path operations.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill cmux-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-settings
Source: https://github.com/deerawan/dotfiles/tree/main/agents/skills/cmux-settings
Command: npx skills add https://github.com/deerawan/dotfiles --skill cmux-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

cmux.json configuration changes are easy to make incorrectly, and unknown or misspelled keys can lead to settings not applying as expected.

Core Features & Use Cases

  • Set and update settings by JSON path: Change appearance, sidebar behavior, notifications, automation, browser rules, and shortcut bindings using the exact dotted key the app expects.
  • Validate keys against cmux’s schema: Detect unknown/unsupported settings after edits so users don’t silently configure nothing.
  • Read, inspect, and open the config safely: Dump raw content (including JSONC comments), view parsed JSON, fetch current values, and open the file in a preferred editor; changes take effect immediately via cmux’s file watcher.

Quick Start

Tell the assistant: set the sidebar tint to match the terminal background by running cmux-settings set sidebarAppearance.matchTerminalBackground true, then confirm with cmux-settings validate.

Frequently Asked Questions about cmux-settings

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

FAQPage Schema
How do I safely edit and validate cmux.json configuration settings?

Schema-aware JSON-path operations let you edit cmux.json by targeting exact dotted keys for appearance or automation settings, ensuring changes apply correctly through strict validation.

Why are my cmux configuration changes not applying as expected?

Configuration changes often fail due to unknown or misspelled keys in cmux.json. Validating keys against the cmux schema after editing detects unsupported settings so they don't silently fail.

Can I change keyboard shortcut bindings and UI appearance in cmux without restarting?

Yes, you can update shortcut bindings and UI appearance by writing to cmux.json. Changes take effect immediately through the application's file watcher without requiring a manual restart.

How do I update embedded browser allowlists and automation socket settings in cmux?

Update embedded browser allowlists and automation socket settings by using dotted JSON-path keys in the cmux.json configuration file, then validate the keys against the schema to confirm accuracy.

What is the best way to preserve JSONC comments when modifying cmux settings?

Use a bundled helper script designed for comment-safe atomic writes to modify cmux settings. This preserves JSONC comments in the configuration file while applying structured JSON updates.

Are there limitations when managing cmux configuration through JSON-path operations?

The primary limitation is that strict schema validation rejects unknown or unsupported settings keys. You must use exact dotted keys expected by the cmux application to successfully update configuration values.