Command Palette

Press Ctrl+K to open the palette. It is the app's unified switcher: one query searches your workspaces, your projects, your conversations, and every command at once.

The groups

Results are always grouped in the same order, each under a sticky header carrying an honest match count (8 of 77 when the list is capped — never a silently truncated number):

At rest the palette shows up to 8 workspaces and 4 projects; while searching, up to 24 and 8.

Conversations are searched too

The palette searches inside your chats, not just their titles — full-text over your messages and the agent's replies, across every open workspace. Only human-visible prose is indexed, so tool payloads and reasoning never pollute results. Selecting a hit jumps to the exact message without starting a provider process. See Searching Your Conversations.

Themes are search-only

The Themes group never appears at rest. It surfaces when you type a theme's name or any of the words theme, colors, palette, or appearance — and stays hidden in command mode (>) and path queries (/), so it can't crowd out those results.

Arrowing through theme rows repaints the whole app live; Enter keeps the highlighted one and Esc puts back the one you started on. The group also carries two entries that open the theme studio: Make a theme from two colors… and Paste a VS Code or shadcn theme…. See Themes & Typography.

The resting order answers "where was I?"

Opening the palette without typing is not an alphabetical index. Workspaces sort by needs-you > working > review > idle, then by most recent activity, with settled and snoozed work last.

Parked work stays fully searchable — settling or snoozing a workspace changes where it ranks, not whether the palette can find it.

Two query modes

/ — path mode. A query with no separator matches names: workspace title, branch, project name. A query containing / switches to matching locations only — project root, worktree path, cwd. These are deliberately separate: subsequence-matching a long path matches nearly everything, so a mixed haystack stops narrowing as you type.

> — command mode. Typing > first hides workspaces and projects, shows a Commands chip in the input row, and searches command labels plus hidden keyword synonyms.

pr — pull request mode. Typing pr narrows to loaded pull and merge requests, ranked by number, title, repo, and author — pr 285 puts #285 first. Selecting one opens the Pull Requests page at that request. The footer hints both modes: > for commands, pr for pull requests.

What selecting a row does

• A workspace — clears any active chat draft, then activates the workspace.
• A project — scopes the sidebar inbox filter to that project and lands you on its top-ranked workspace. "Go to this project" in one keystroke.
• A command — runs it through the same dispatcher the global keyboard handler uses, so a shortcut and its palette row can never drift apart.

Workspace-scoped commands are hidden when no workspace is active, rather than shown as silent no-ops.

Commands

New agent · New workspace in this project · Create new workspace · Open project… · Run dev command · Next workspace · Previous workspace · Find file by name · Search in files · Split pane right · Split pane down · Close pane · New terminal tab · Close tab · Focus next pane · Focus previous pane · Open browser · Pull requests · Toggle sidebar · Toggle right panel · Toggle preset bar · Keyboard shortcuts · Settings · Regenerate MCP config

The sidebar's Search button opens the palette directly at Find file by name.

Matching

Fuzzy matching is scored — type partial words in any order and results rank by match quality. Changing the query scrolls the list back to the top. An empty result names the query that failed and points you at >.

Keyboard

Current limits

• No user-defined custom commands.
• No recently-used or frecency ranking — resting order is status-and-activity based.
• No nested submenus.
• A project with no workspaces is not listed; project rows are derived from grouped workspaces.