Console hotkeys

Dashboard's Shift+C opens release notes with either sidebar or content focus. Accounts' v also works with either focus; these commands browse the whole screen rather than acting on a selected project. Project-specific commands still require content focus. Personal rebindings apply to both paths.

Open Settings → Hotkeys in the terminal or browser console. Search the grouped command list, select an action, press Enter and type its new combination. Saving updates the current controller user's preferences. The same bindings drive TUI input and displayed web/native shortcut hints; clicking a web action still calls that action directly.

Conflicting commands on overlapping screens are rejected. Commands on unrelated screens may reuse a key. Once a command is reassigned, its old key no longer executes that command. The Settings screen shows whether a binding is customized.

Bindings apply to the main console commands listed in this screen: toolchains, context tools, Projects, sessions, hosts and other console actions. Text editing, modal confirmation/navigation and keys sent to an attached agent terminal retain their native behavior. Clipboard, terminal recovery and browser-owned combinations are protected; unsupported combinations are rejected by the editor. Keyboard-layout normalization still applies to action keys, while typed text keeps its original characters.

Storage and concurrent clients

Preferences live on the controller under the authenticated application user. Local mode uses the same path with its implicit operator. They are not repository files and never change another user's configuration. A console reload restores them; other connected clients refresh their copy periodically. Saving includes the current revision. A concurrent change returns HTTP 409; reload before saving again.

The shared registry is packages/contracts/src/hotkeys.ts. It supplies command IDs, labels, default combinations, screen scopes, validation, remapping and hint labels.

API and operator MCP

GET /v1/preferences/hotkeys returns:

{"overrides":{},"revision":0,"updatedAt":null}

PUT /v1/preferences/hotkeys accepts the complete override map and current revision:

{"overrides":{"project.view":"z"},"revision":0}

This changes the Projects list/mosaic toggle from m to z. Remove an entry to restore that command's default; use overrides: {} to reset all. Unknown commands, unsupported keys, collisions and arbitrary user IDs are rejected.

Operator MCP discovers the exact GET /v1/preferences/hotkeys and PUT /v1/preferences/hotkeys operation IDs through controller_operations and calls them through controller_request. Session MCP cannot edit operator console preferences. Interactive landing demos use isolated, reversible in-memory settings.

Settings opens a section list. Choose Hotkeys for personal bindings. History cleanup and Log streaming are separate administrator pages; see audit events. Escape from a subsection returns to the Settings list.