> ## Documentation Index
> Fetch the complete documentation index at: https://panopticon-cli.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard keyboard shortcuts

> Every Overdeck dashboard keyboard shortcut, with its keys on macOS, Linux and Windows, and the pages where each shortcut works.

The dashboard has one set of keyboard shortcuts. Each one names its keys for macOS and for Linux and Windows, because the browser keeps some keys for itself on each platform.

## Open the list

Press `?` anywhere outside a text field to open the **Keyboard shortcuts** sheet. It lists every shortcut that works on the page you are on, with the keys for your platform. On God View, `?` opens God View's own help instead.

## Shortcuts

| Action | macOS | Linux and Windows |
| - | - | - |
| Command palette | `⌘K` | `Ctrl+K` |
| Find a conversation | `⌘J` | `Ctrl+J` |
| Search | `/` | `/` |
| Go to Pipeline | `G` then `P` | `G` then `P` |
| Go to Board | `G` then `B` | `G` then `B` |
| Go to Agents (experimental; opens Home while Experimental features is off) | `G` then `A` | `G` then `A` |
| Go to Command Deck | `G` then `C` | `G` then `C` |
| Keyboard shortcuts sheet | `?` | `?` |
| Go to Stage tab 1 to 9 | `⌘1` to `⌘9` | `Ctrl+Alt+1` to `Ctrl+Alt+9` |
| Close the Stage tab | `⌘W` | `Ctrl+Alt+W` |
| Toggle the terminal drawer | `⌘T` | none |
| Collapse the left column | `[` | `[` |
| New conversation | `N` | `N` |
| Show or hide Files | `⌘⇧E` | `Ctrl+Shift+E` |
| Show or hide Changes | `⌘⇧G` | `Ctrl+Shift+G` |
| Search file contents | `⌘⇧F` | `Ctrl+Shift+F` |
| Go to file | `⌘P` | `Ctrl+P` |
| Next / previous file in a diff | `J` / `K` | `J` / `K` |
| Emergency stop | `⌘⇧.` | `Ctrl+Shift+.` |

For the `G` shortcuts, press `G`, let go, then press the second key within one and a half seconds.
For every view these shortcuts reach, see [Dashboard views](https://panopticon-cli.com/features/dashboard-views.md).

## Keys on single pages

These keys work only where named, and the `?` sheet does not list them.

| Action | macOS | Linux and Windows | Where |
| - | - | - | - |
| Next or previous issue, then open it | `J` / `K`, then `↵` | `J` / `K`, then `↵` | Board and Pipeline, when you are not typing |
| Undo the last status move | `⌘Z` | `Ctrl+Z` | Board |
| Undo the last settle or snooze | `⌘Z` | `Ctrl+Z` | the Conversations list, when it has focus |
| Open the folder in your preferred editor | `⌘⇧O` | `Ctrl+Shift+O` | a conversation, or an issue's open-in picker |
| Voice input | `⌘⇧M` | `Ctrl+Shift+M` | the conversation composer |
| God View help, fullscreen | `H` or `?`, `F` | `H` or `?`, `F` | God View (experimental) |

## Command palette

Press `⌘K` (macOS) or `Ctrl+K` (Linux and Windows) to open the command palette with every result
type. Press `⌘J` (macOS) or `Ctrl+J` (Linux and Windows) to open it with the **Conversations** chip
already selected. `Esc` closes the palette from anywhere inside it. The palette is not what `/`
opens: `/` opens issue search instead.

Before you type anything, the palette lists built-in actions, workspaces, issues and running agents.
The `pan` command catalog appears only once you start typing. Example actions: **New workspace…**,
**Open Flywheel**, **Open Settings**, **Go to Kanban Board** and **View Agents**; there are more.

As you type, local results (actions, commands, issues, agents, workspaces) filter instantly against
your text. Once you have typed two or more characters, the palette also searches conversations and
memory on the server; that search waits briefly for you to stop typing, and gives up with
`Search timed out after 10 s. Try again.` if the server has not answered within 10 seconds.

Scope chips under the input narrow the list to one result type:

| Chip | Shows |
| - | - |
| All | every result type |
| Actions | built-in actions and other orchestration and navigation entries |
| Files | files, listed only where a work dock is mounted (the Command Deck) |
| Commands | the `pan` command catalog |
| Issues | issues, active workspaces and running agents |
| Workspaces | the workspaces registry |
| Conversations | conversations, including results from linked machines |
| Memory | memory entries and observations |

A chip appears only when its result type is present in the current results, except
**Conversations**, which is always offered so `⌘J` / `Ctrl+J` always has somewhere to land. If the
selected chip's type drops out of the results, the palette falls back to **All**.

Choosing a row acts on its type. An action runs it, and an issue or a workspace opens it. A file
opens it too, but only in the Command Deck, where the Files chip lists anything. A memory row opens
the issue it belongs to, or shows its text in a toast when it has none. A conversation opens at its
matching message, see [Find a conversation](https://panopticon-cli.com/features/conversations.md#find-a-conversation). A
**command** row copies the command text to your clipboard instead of running it. A row under
`On <machine label>` opens that conversation on the linked machine instead of this one.

Inside the palette, `↑` `↓` move the highlight, `↵` chooses the highlighted row, and `Esc` closes the
palette. The **Newest first** button in the footer reorders conversation results by date; see
[Find a conversation](https://panopticon-cli.com/features/conversations.md#find-a-conversation) for how conversation results are
ranked.

## Where shortcuts work

Single keys such as `N`, `?`, `/`, `[`, `J`, `K` and the `G` shortcuts, and the Stage tab keys, work only when you are not typing. They do nothing while focus is in a text field, a terminal or a code editor, so the key goes to what you are typing in.

Shortcuts with `⌘` or `Ctrl`, such as the command palette, also work in text fields and code editors. In a terminal, the terminal gets the key first: `Ctrl+K` and `Ctrl+J` go to the shell, as they would in any terminal. In a Chrome tab, `Ctrl+W` never reaches the terminal: Chrome keeps it and closes the browser tab. The emergency stop works from anywhere outside a terminal, including text fields.

The four Files keys (show or hide Files, show or hide Changes, search file contents and Go to file) work only in the Command Deck, where the work dock is. There they work from anywhere, including text fields and the code editor, where they win over the editor's own keys: on macOS `⌘⇧G` opens Changes instead of Monaco's Find Previous. On other pages, `Ctrl+P` keeps the browser's print dialog. In a conversation, `Ctrl+F` (`⌘F`) without Shift opens the conversation's find bar.

## Keys the browser keeps

Chrome never passes `Ctrl+N`, `Ctrl+T` or `Ctrl+W` to a web page, and on Linux and Windows it keeps `Ctrl+1` to `Ctrl+9` to switch browser tabs. That is why Stage tabs switch with `Ctrl+Alt+1` to `Ctrl+Alt+9` and close with `Ctrl+Alt+W` there. On macOS, `⌘1` to `⌘9` and `⌘W` reach the page, so they stay.

Stage tabs show no shortcut chips. The keys are listed in the `?` sheet, and the **N tabs** button at the end of the tab strip lists every tab, including tabs scrolled out of view. Escape closes the **N tabs** list and the **+** menu and returns focus to the button that opened it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.