Command palette

Stop hunting through panels.
Press one key instead.

AgentsRoom holds a lot of things: agents across several projects, a skills library, a prompt library, the project memory, scheduled agents, webhook triggers, a backlog, dev commands, SSH and database connections, and the repository itself. The command palette puts all of it behind one shortcut.

Cmd K on macOS, Ctrl K on Windows and Linux, or the Search button in the title bar. The field opens near the top of the screen, over whatever you were doing. Type three letters, read results grouped by category, move with the arrow keys, press Enter.

Command palette⌘K
BacklogFix the login redirect loop#248
PromptsAudit a login flow
Filessrc/auth/login-form.tsxsrc/auth
Commitsfix: keep the login form focuseda3f19c2
↑↓moveopenescclose

Skills, prompts, memory notes, agents, scheduled runs, dev commands and connections are in the same list

One field, every source at once. The palette groups what it finds so a ticket, a prompt, a file and a commit can share the same three letters without competing for the same row.

A command center gets crowded, and that is not a defect: it is what you asked for when you put five projects, a dozen agents, your prompts, your skills, your tickets and your servers in the same window. The cost shows up later, in the two seconds it takes to remember which panel holds the thing you want, times forty times a day.

The command palette removes the remembering. It is one field, opened over whatever you were doing, that searches every list AgentsRoom maintains at the same time. You do not pick a panel first, you type what you have in your head: a ticket number, half a filename, the name of a skill, the beginning of a commit message.

It is built the way developers already expect this to work, because Spotlight, Raycast and the editors taught everyone the same gesture: a shortcut, a few letters, arrow keys, Enter. Nothing new to learn, and the mouse stays where it is.

Why one bar beats ten panels

You search by what you remember, not by where it lives. Nobody thinks I need the skills library, they think I need the review checklist. The palette accepts the second one, and it works even when you no longer remember which library the thing was saved in.

The search is forgiving. Matching is fuzzy: letters can be missing, in the wrong order, or typed without their accents, and the result still comes up. That matters most for the things you named yourself, months ago, in a hurry.

Everything shares one ranking. Results come back grouped by category rather than mixed into one flat list, so a file called auth never buries the backlog ticket about authentication. You read four groups of three rows instead of thirty rows of noise.

It stays a keyboard gesture from start to finish. Open, type, arrow, Enter. The palette closes itself and puts you in the thing you picked: the agent, the ticket editor, the skill, the terminal of the dev command, the file.

What the palette searches

Every list AgentsRoom maintains for the project, plus the repository itself.

Skills library

The reusable procedures your agents follow, from this project and from your global library. Search a skill by name, description or tag, and the result opens it straight in its editor.

Scheduled agents and triggers

The agents that start on a clock and the ones that start on a webhook are in the same list. Find the nightly log scan or the pull request trigger without opening the panel that owns it.

Prompt library

Saved briefs, project ones and global ones, matched on the title, the first line or a tag. The one you wrote for the release notes comes back on release, not on the exact title you gave it.

Project memory

The notes your agents write for each other: decisions, architecture, pitfalls. Project notes and account notes are both searched by name and description, and a result opens the note in the memory editor.

Backlog tickets

The open tickets of the project, by title, by number, by tag or by a word in the description. The one you half remember filing on Tuesday is three letters away, in whatever column it ended up in.

Dev commands and servers

Your saved commands, the dev servers, the build scripts. Open one from the palette and it starts in its terminal, with no trip through the panel.

SSH and database connections

The machines and the databases you saved. Search by the name you gave them or by the host, and open the session straight from the field.

Agents of the current project

Everyone working on the project you have open: the running agents first, by name or by role, so a session you left an hour ago is one keystroke away.

Files of the project

Fuzzy search on the whole path, so src auth login finds src/auth/login-form.tsx. What .gitignore excludes is excluded here too: no node_modules, no build output, no dependency you never wrote.

Commits of the current branch

When the project is a git repository, the last 200 commits of the branch you are on are searchable by subject, by hash or by author, and the result opens the commit with its diff. It is the fastest way back to when did we change this.

Agents of your other projects

They come last on purpose, under the current project, so they never push aside what you were looking at. Useful when you remember the agent and not the project it lives in.

Narrow it down with one character

Each group shows only its best rows so no single source takes the whole screen. Start the query with a prefix character and the palette searches one source, uncapped. The same thing is one Tab away: the chips under the field cycle through the active sources with Tab and Shift Tab.

Dev commands only

>

The greater-than sign restricts the search to your saved commands, dev servers and scripts. It is the same convention editors use, so your fingers already know it.

Backlog only

#

The hash sign searches tickets and nothing else. Type it followed by a number to jump straight to that ticket.

Agents only

@

The at sign lists the agents, current project first. The fastest way back to a session when you have four running and three projects open.

Files only

/

The slash searches the repository. It is worth it when a filename is also a common word: a slash keeps the tickets, the prompts and the commits out of the way.

Commits only

:

The colon searches the history of the current branch and nothing else. Handy when the words of a commit message would also match a ticket and a file.

It never asks for the mouse

Four keys cover the whole feature.

Open

Cmd K on macOS, Ctrl K on Windows and Linux. The shortcut is configurable in the settings if it collides with something you already use, and the Search button in the title bar does the same thing for the days you prefer to click.

Move

Up and down arrows walk through the results across every group, so you never have to aim at a category first. The selected row scrolls itself into view.

Open the result

Enter opens what is selected and closes the palette. An agent opens its session, a ticket its editor, a dev command its terminal, a file its viewer, a skill or a prompt its card.

Leave

Escape empties the field first, so a search you mistyped costs one key rather than a reopen; press it again on an empty field and the palette closes and puts back what was underneath. Nothing is started, nothing is saved, nothing moved because you looked.

It opens on what you were doing

With an empty field the palette shows your last eight choices rather than a blank rectangle, in order. Most of the time the result you want is already on screen and you press Enter without typing anything at all. It is also the quickest way back to a file you closed by accident.

It costs nothing until you use it

Search over a whole repository is easy to make slow. The palette is built around not being that.

What the index costs
  1. App launch
    nothing is scanned
  2. First Cmd K
    index built in the background
  3. You type
    results while the letters land
  4. Afterwards
    refreshed in place, never rebuilt

Nothing you type leaves your machine

Nothing is indexed at startup

AgentsRoom does not walk your repository when it launches. The file and commit index is built the first time you open the palette, in the background, so the app opens at the same speed on a small project and on a large one.

Refreshed in place

Once the index exists it is updated incrementally as the project changes, instead of being rebuilt from scratch. A branch switch or a long agent session does not send you back to a full scan.

Results while you type

Matching runs against what is already in memory, so results appear as the letters land. The lists AgentsRoom maintains are searched immediately, and the repository joins in as soon as its index is ready.

It stays on your machine

The index lives on your disk and nothing you type in the palette is sent anywhere. Your filenames, your commit messages and your ticket titles are not a search query to a server, here or elsewhere.

Settings

You decide what it searches

Each source can be turned off. A project where you never touch the backlog does not need tickets in its results, and a monorepo with a hundred thousand files may be better searched without files at all.

One setting for every project
Sources are enabled or disabled globally in the settings, so the palette looks the same everywhere by default. Turn commits off once and no project offers them again.
Overridden per project
A project can depart from the global setting when it needs to. The huge repository searches files nowhere else needs, the client project keeps its backlog out of the way, and neither decision leaks into the other.
The shortcut is yours
Cmd K and Ctrl K are the defaults, not a rule. Record the combination you want in the settings if another tool already owns that one. It fires while the AgentsRoom window has the focus, so it never steals the key from the app you are actually in.

Everything the palette knows about your project comes from lists AgentsRoom already keeps and from the repository on your disk. Turning a source off removes it from the results, it does not hide it from you anywhere else.

How it works, in practice

The whole feature, from the shortcut to the thing you wanted.

01

Press the shortcut

Cmd K on macOS, Ctrl K on Windows and Linux, from anywhere in the app. The field opens near the top of the screen, over whatever you were doing, and takes the focus. The Search button in the title bar does the same.

02

Type what you remember

A fragment is enough, and it does not have to be the beginning. Letters can be missing or out of order, and accents are optional: cafe finds the file you named with an accent.

03

Read the groups

Results arrive grouped: skills, scheduled agents, prompts, memory notes, tickets, commands and connections, agents, files, commits, then the agents of your other projects. The groups keep small categories visible instead of letting the repository take every row.

04

Narrow it if you need to

Add a prefix character to search one source only, or press Tab to walk the chips under the field. A narrowed search also drops the per-group cap, so you see everything that matched instead of the best few.

05

Press Enter

The palette closes and the thing opens: the agent session, the ticket, the skill, the prompt, the terminal, the file. Escape at any point puts you back with nothing changed.

Command palette questions

What is the command palette in AgentsRoom?

It is a search field that opens over the whole app and searches everything AgentsRoom keeps about the project at once: the skills library, the scheduled agents and webhook triggers, the prompt library, the project memory, the open backlog tickets, the dev commands, the SSH and database connections, the agents of the current project and then of your other projects, the files of the repository and the commits of the current branch. Results come back grouped by category, and Enter opens the one you selected in the surface that owns it.

Which key opens it, and can I change it?

Cmd K on macOS, Ctrl K on Windows and Linux. The shortcut is configurable in the settings, so you can record another combination if a tool on your machine already owns that one. There is also a Search button in the title bar that opens the same palette, for the moments when your hand is already on the mouse.

Is this like Spotlight or Raycast?

The gesture is the same one, deliberately: a shortcut, a few letters, arrows, Enter. Two things differ. The index: Spotlight and Raycast search your machine and your applications, this palette searches what AgentsRoom knows about the project you have open, which is the part no system launcher can see. And the scope of the shortcut: it works while the AgentsRoom window has the focus, it is not a system-wide hotkey, so it never takes the key away from the app you are actually working in.

Does it search the files of my project?

Yes, with fuzzy matching over the whole path, so a few letters of a folder and a few of a filename are enough. What .gitignore excludes is excluded from the index too, so you never scroll through node_modules, build output or dependencies you did not write. Files can be turned off entirely if a repository is so large that you would rather search it elsewhere.

Does it search git history?

When the project is a git repository, the last 200 commits of the branch you are on are searchable by subject, by hash or by author, and opening one shows the commit with its changes. It is the fastest route to when did we change this. Projects that are not git repositories simply do not show that group.

Does anything I type leave my machine?

No. The index is built and kept locally, and the search runs locally against it. Your filenames, your commit messages and your ticket titles are never sent to a server to be searched, and there is no remote autocomplete behind the field.

Will indexing slow the app down?

The index is built the first time you open the palette, in the background, and never while the application is launching: opening AgentsRoom takes the same time on a small repository and on a large one. After that it is refreshed incrementally as the project changes rather than rebuilt, and the lists AgentsRoom already holds in memory answer instantly whatever the repository is doing.

Can I turn off the sources I never use?

Yes, source by source, in the settings. The setting is global so the palette behaves the same in every project, and any project can override it when it needs to: a monorepo can drop files, a project you only pilot can drop the backlog, and neither choice affects the others.

Can I find an agent that is running in another project?

Yes. Agents of the project you have open come first, and the agents of your other projects come after them, at the bottom of the list. They are deliberately last so they never displace what you were looking at, which makes the palette a reasonable way to jump between projects when you remember the agent and not where it lives.

How do I search only one kind of thing?

Start the query with a prefix character: the greater-than sign for dev commands, the hash sign for the backlog, the at sign for agents, the slash for files, the colon for commits. Or press Tab to walk the chips under the field, which do the same thing without a character to remember. A narrowed search also lifts the per-group cap, so it is worth using when the word you are looking for is common enough to match everywhere at once.

Does it work on Windows and Linux?

Yes, on macOS, Windows and Linux, with the same sources and the same behaviour. Only the default shortcut differs, Ctrl K instead of Cmd K, to match what each system expects.

Does it depend on which agent CLI I use?

No. The palette searches AgentsRoom itself, not an agent, so it behaves the same whichever CLI your sessions run on: Claude, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs. An agent found in the results opens its session with the provider it was started with.

Goes well with

One key. Everything you were looking for.

Download AgentsRoom, press Cmd K on macOS or Ctrl K on Windows and Linux, and type the first thing that comes to mind.

FreeDownload AgentsRoom

Companion app: monitor your agents on the go

Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.

Get the extension
Chrome Web Store

Push bugs and requests straight to your public backlog.

A glimpse of AgentsRoom in action.

Multiple projects
Multi-provider
Multiple agents
Live status
File diff & commit
Mobile companion
Live preview
Agent teams
Browser automation
Backlog-driven dev
Prompt Library
Skills Library
View all features