Skip to content

Focus and conflicts: which section a key goes to #13

Closed

Description

@shayan-ys

Part of the map Map: integration key contract.

Question

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.

Activity

  1. self-assigned this
    on Oct 9, 2026
  2. shayan-ys commented on Oct 9, 2026

    @shayan-ys
    OwnerAuthor

    Resolution

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions