You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Focus and conflicts: which section a key goes to #13
When two integrations bind the same key, or an integration key matches a built-in key (r, q), what happens? Options: a focused section (for example Tab cycles focus) vs keys required unique across integrations and rejected at config load. Also decide when an integration, and when the user, may override or disable a built-in key.
Focus model: the first keyed integration has focus, and tab cycles it. Built-in keys win, then the focused integration's binding. A binding that uses an enabled built-in key fails config load; only the user can remap a built-in key. Two integrations may share a key.
Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec: Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md (private vault).
Activity
shayan-ys commentedon Oct 9, 2026
Resolution
Focus model: the first keyed integration has focus, and
tabcycles it. Built-in keys win, then the focused integration's binding. A binding that uses an enabled built-in key fails config load; only the user can remap a built-in key. Two integrations may share a key.Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec:
Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md(private vault).