#Keyboard Shortcuts

JAT uses keyboard shortcuts for fast navigation and common actions. All shortcuts use the Alt key as the primary modifier since its less likely to conflict with browser defaults.

#List navigation (every route)

Every route with a list, table, or card grid supports vim-style j/k navigation. The shortcuts below work on /triage, /chores, /automation, /integrations, /servers, /kanban, /config, /clients, /search, /dash, /memory, /source, /files, /data, /bases, and /workflows.

Some routes add route-specific keys (e.g. n for new rule on /automation, Space to toggle start/stop on /servers, →/← to drill into milestones on /clients). Press ? on any page for the full list.

#Global shortcuts

These work from any page in the IDE.

#Session shortcuts

These target the currently hovered session on the Work page. Hover over a SessionCard first, then press the shortcut.

The hovered session is tracked through mouse events on SessionCard components. If no session is hovered when you press a session shortcut, nothing happens.

#Files page shortcuts

These are active when the Files page editor is focused.

#System shortcuts

#How shortcuts work

The shortcut system uses a Svelte 5 store (keyboardShortcuts.svelte.ts) that manages two maps:

• Global shortcuts for IDE-wide actions with factory defaults
• Command shortcuts for user-assigned slash command bindings

Both maps persist in localStorage. The store initializes on layout mount and registers a global keydown listener.

// Matching a keyboard event to a shortcut
export function matchesShortcut(event: KeyboardEvent, shortcut: string): boolean {
    const parsed = parseShortcut(shortcut);
    if (parsed.alt !== event.altKey) return false;
    if (parsed.ctrl !== event.ctrlKey) return false;
    if (parsed.shift !== event.shiftKey) return false;
    return event.key.toLowerCase() === parsed.key.toLowerCase();
}

The system handles platform differences. On macOS, Alt maps to Option and the display format uses symbols (the option glyph for Alt, the command symbol for Meta). On Linux and Windows, shortcuts display as text labels like Alt+N.

#Customizing shortcuts

Open Settings and navigate to the Shortcuts tab. Every global shortcut shows its current binding with a "Record" button to capture a new key combination.

Requirements for custom shortcuts:

• Must include at least one modifier (Alt, Ctrl, or Meta)
• Must include a main key (letter, number, or special key like Escape)
• Cannot duplicate an existing shortcut

The Settings UI shows conflict warnings in real-time. If you try to assign Alt+K to a new action but it already maps to "Kill Session," you'll see a warning with the conflicting action name.

// Conflict detection
const conflict = findGlobalShortcutConflict('Alt+K', 'my-new-action');
if (conflict) {
    console.log(`Conflicts with: ${conflict}`);
}

Reset any shortcut to its default with the reset button. "Reset All" restores every shortcut to factory defaults.

#Browser conflict avoidance

The shortcut system deliberately uses Alt as the primary modifier because standard browser shortcuts use Ctrl (Ctrl+C, Ctrl+V, Ctrl+T, etc.). This avoids most conflicts.

Shortcuts that do use Ctrl (like Ctrl+S for save and Ctrl+for terminal) callevent.preventDefault()` to override the browser default. The validation system warns if you try to assign a shortcut that conflicts with a known browser binding.

#See also

• IDE Overview for page navigation
• Work Sessions for session controls
• File Explorer for editor shortcuts