cmux-shared-behavior

To maintain consistent UI state across multiple entrypoints, route all feature mutations through a single shared action path. This central mutation path ensures uniform state updates regardless of whether the user interacts via keyboard shortcuts, command palette, or context menus.

Handling optimistic UI updates across different surfaces requires a centralized mutation path with pending state tracking. This approach enforces explicit rollback handling on failure, ensuring UI consistency whether the action originates from a CLI command or a settings UI.

To stop duplicating behavior logic for CLI commands and context menus, centralize the feature logic into one shared action/model path. This standardizes the behavior and reuses the same mutation logic across all cmux entrypoints.

Yes, you can use a single mutation path for features exposed through socket commands, settings UI, and the debug menu. A centralized action path coordinates cross-surface behavior to ensure consistent UI responses and state updates everywhere.

Application state becomes inconsistent when triggering actions from different entrypoints because of duplicated behavior logic. Adopting a single shared action path standardizes the mutation process, enforcing one update route with optimistic updates and explicit rollback handling.