---
title: Global Search
description: Jump to any page, node, or stack from anywhere in the app with a single keystroke.
---
The **global search palette** lets you move around Sencho without reaching for the mouse. It covers the destinations the top bar exposes for your tier and role, every configured node, and every stack on every online node in your fleet.
## Opening the palette
Three ways to open it:
- Press Ctrl + K (or Cmd + K on macOS) from anywhere in the app.
- Click the search icon in the top bar, left of the notification bell.
- Press Esc to close it at any time.
The shortcut works from the dashboard, editor, fleet view, resources, and every other screen.
## What you can find
The palette groups results into three sections.
| Group | What it contains | What happens when you pick one |
|-------|------------------|--------------------------------|
| **Pages** | The same set of destinations the top bar shows you. Home, Fleet, Resources, App Store, and Logs always appear; Auto-Update appears for admins on Skipper or higher; Console and Schedules appear for admins on Admiral; Audit appears for any role on Admiral with the audit permission. | Navigates to that page |
| **Nodes** | Every node in your fleet, with a green dot for online and a grey dot for offline. The currently active node carries a small **ACTIVE** chip on the right. | Switches the active node without leaving the current page |
| **Stacks** | Every compose stack on every online node, matched on the compose filename (extension included). | Switches to the stack's node and opens it in the editor |
Each stack row shows a status dot on the left (green for running, grey for exited, faded grey for unknown) and the node name as a mono tag on the right. That way you always know which host a match lives on before you pick it.
## Typing to filter
Start typing and the results narrow in real time. Pages and nodes filter instantly; stack search debounces for about 250 ms before fanning out across the fleet, so a fast typist sees the Stacks group fill in a beat after the rest. Matching is substring-based, so you can type a fragment from anywhere in a stack's filename or a node's name. Examples:
- `fleet` jumps to the Fleet page.
- `local` selects the Local node and switches the active context to it.
- `db` lists every stack with "db" in its filename, showing which node each one lives on.
When a query matches stacks on a remote node, selecting one switches the active node and opens the editor on that stack in a single action.
## Cross-node search
Stack search fans out across every online node in your fleet. Offline nodes are skipped so one unreachable host never slows the palette down. Results from the active node and remote nodes appear together, grouped in the order nodes appear in your fleet list.
The Stacks group caps at 50 rows. When a query matches more than that, a `Showing first 50 of N` line renders below the list so you know there is more to find. Keep typing to narrow the query; the line disappears once fewer than 50 matches remain.
While the fleet is responding, the empty area reads `Searching...` until the first batch of stack hits arrives. If no group has a hit at all, the empty area reads `No results.`
## Keyboard navigation
Once the palette is open:
- ↑ / ↓ moves through the results.
- Enter picks the highlighted result.
- Esc closes the palette.
Offline nodes show as greyed-out and are not selectable.