SugarCraft keymaps

A fleet-wide index of where each app's keys are documented. This page is links only, on purpose: every app's key table is generated or guarded where it lives (for example candy-code's is pinned by KeyBindingDriftTest against its registry), and restating a table here would fork it — the fork would drift, and the drift would lie. So grab the chord list from the authoritative page, never from a copy. Chords are written Modifier+Key (Ctrl+k, Shift+Tab, Alt+letter) throughout.

Apps

App Authoritative key documentation
candy-code README §Keys — global/palette/modal dispatch; slash commands in COMMANDS.md; keys are rebindable per SETTINGS.md, and the App claims some chords (e.g. Ctrl+K) before Chat sees them. Terminal/SSH questions: TROUBLESHOOTING.md.
candy-top README §Key bindings — the same table feeds the in-app help overlay (F1 / ? / h) and candy-top -h; config options (including vim_keys, disable_mouse) in §Config keys.
candy-files README §Keys — including the honest Ctrl+Tab caveat: most terminals send plain Tab for it; it works where modified-Tab reporting exists (Kitty-protocol terminals — and Ctrl+PgUp/Ctrl+PgDn as the universal alternative). tmux and browsers may intercept.
candy-sql README §Keys, plus Admin Dashboard keys.
candy-git README §Keys, plus diff-viewer keys.
candy-mdview README §Pager.
candy-tetris README §Controls (+ VS mode).
candy-flappy README §Keys.
candy-minesweeper README §Keys.
candy-codetime README §Keys (dashboard).
candy-gifview README §Keys.
candy-image README §Keys — only while --animate plays.
candy-ssh-launcher README §Keybindings.
candy-scriptui README §Keyboard map — plus its editing-keys sub-table.
candy-code-web README — browser chords live in the Keyboard bullet; ? opens the in-app overlay listing the live chords, and palette / help / tab-chord are rebindable (src-web/lib/keymap.ts).
candy-starter README — scaffold demo: the counter exits on q, Esc or Ctrl+C; your own keys start there.

Apps deliberately not listed: candy-ansi-inspect, candy-codeshot, candy-mail and candy-kv are one-shot CLIs, candy-discord, candy-msteams and candy-git-server run headless (plugin / daemon — no key input of their own), and candy-vcr is driven by a recorded script, not keystrokes. If a candy-* app reads keys, it belongs in the table above.

Making chords arrive at all

Whether Ctrl+Tab, Ctrl+Enter, or Alt+letter ever reach an app as themselves is a terminal question, not an app question:

Every app that draws a menu bar keeps keyboard equivalents for every mouse affordance — if you find one that doesn't, that's a bug report, not a workaround.

Color and reduced-motion env

The env-var hub for the fleet is the shared table in the sugar-core README; the color-depth ladder (TERM/COLORTERM/NO_COLOR/force flags/CI) is documented by sugar-colorprofile. REDUCE_MOTION / PREFERS_REDUCED_MOTION behavior and the honest per-app NO_COLOR status are in GETTING-STARTED.md §Accessibility & reduced motion.

Not yet here

Per-lib layout maps (ASCII diagrams of where each key is) don't exist yet anywhere in the fleet; that gap is recorded in the audit evidence and would be its own follow-up. This index will link them where they land.