Command palette & search
FreeThe editor has four search boxes that you open from anywhere with a shortcut. They find commands, files, recently used files and everything else the editor knows, without touching the mouse.
What you do here
- Commands: run any action of the editor by its name
- Open files: open a project file by its name
- Recent files: back to a file from a moment ago
- Search everywhere: files, tools, sites, branches, tables, settings and more in one box
- Run scripts: scripts from
package.jsonandcomposer.jsonas commands
The four boxes
| Shortcut | What opens |
|---|---|
| ⌘K or ⇧⌘A | Commands |
| ⌘P or ⇧⌘O | Files |
| ⌘E | Recent files |
| ⇧⇧ (Shift twice, quickly) | Search everywhere |
The search field in the middle of the title bar shows these shortcuts as a hint: "⌘P File · ⌘K Commands · ⇧⇧ Everywhere". Clicking into it opens Search everywhere.
Working in every box
- Typing filters the list. The search tolerates gaps: the letters just have to appear in the right order, word starts count more. "gtl" finds "Go to line".
- ↑ and ↓ select, ↩ runs, Esc or a click outside closes.
- When nothing matches, the box says "Nothing found".
Tip: To search for text inside files, use ⇧⌘F (Find).
Commands Free
The command palette lists every command of the editor that can run right now, with its group and shortcut. You don't need to know a menu or a shortcut: a few letters of the name are enough.
Where to find it
- ⌘K or ⇧⌘A
- View › Command palette in the menu bar
- In Open file (⌘P), start your input with >
How to do it
- Press ⌘K. The box says "Type a command…".
- Type a few letters, such as "mini" for Toggle minimap. The search looks at names and keywords, so "clone" also finds Clone repository….
- Select with ↑/↓ and press ↩.
The list shows up to 80 matches. To the right of each command are its group and, if it has one, its shortcut.
What is in the list
Only commands that work right now. Compare with HEAD only appears with an open file, Git: Push only in a repository, the Markdown toolbar commands only in a Markdown file. Tools you switched off in the settings bring no commands.
The groups:
| Group | Examples |
|---|---|
| File | Open folder…, Clone repository…, Close project, Save, Reload file from disk, Local history, Recent files |
| View | Search everywhere, Show/hide Project and the other tools, Maximize tool window, Reload window, Settings, Check for Updates…, Changelog & Updates, Documentation: guide to WebDonkey Editor, Legal: imprint, terms of use, privacy, Mappings & Sync…, Remote: backups, Remote: scheduled tasks, Remote: server logs, Remote: fetch locally, the image commands such as Image: Rotate right |
| Editor | Close tab, Reopen closed tab, Split editor right, Split editor down, Go to line…, Format document, Copy reference (path:line), Toggle preview (Markdown/JSON) |
| Git | Git: Commit…, Git: Push, Git: Pull, Git: Fetch, Compare with HEAD |
| Terminal | Terminal: New terminal, Terminal: Clear, Terminal: Move to editor tab |
| Theme | Switch theme…, Theme: Aurora, Theme: Arctic, Theme: like WebDonkey and your own themes |
| Claude | Continue last Claude conversation, Claude: Open the project's Claude terminal |
| Scripts | your project's scripts, see Run scripts |
| Launcher, Database, Mail, Remote, Search, Markdown | the commands of these tools, such as New SQL console or Upload to … |
The menu bar uses the same commands, with the same names and shortcuts (Menus). You see and change every shortcut under Settings › Shortcuts (Shortcuts).
⌘K in the terminal and the Git window
- In the terminal, ⌘K also opens the palette out of the box. Under Settings › Terminal, ⌘K in the terminal lets it clear the terminal instead.
- In the Git window, ⌘K means Commit, ⇧⌘K Push and ⌘T Pull, as in PhpStorm. If you switch on PhpStorm shortcuts everywhere under Settings › Features, group Git, these shortcuts apply everywhere except in the terminal. The command palette then lives on ⇧⌘A and ⇧⇧.
Free and Premium
The palette is free. Commands for Premium features such as Switch theme… or Upload to … don't appear without WebDonkey Premium.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| A command is missing | it can't run right now (no file open, no repository) or its tool is switched off | open a file or switch the tool on under Settings › Features |
| ⌘K commits instead of opening the palette | PhpStorm shortcuts everywhere is on, or the focus is in the Git window | use ⇧⌘A |
| ⌘K clears the terminal | ⌘K in the terminal is set to clear | use ⇧⌘A or change the setting |
See also
Open files Free
Open file takes you to any file of your project by its name. You don't have to type the whole name or know which folder the file is in.
Where to find it
- ⌘P or ⇧⌘O
- File › Open file… in the menu bar
How to do it
- Press ⌘P. The box says "Open file…".
- Type parts of the file name. Letters in the right order are enough, word starts count more: "chsub" finds
CheckoutSubscriber.php. - Select with ↑/↓. ↩ opens the file in a tab. If it is already open, its tab comes to the front.
Next to each match is its path in the project. The list shows up to 60 matches.
What is searched
- the project folder with all its subfolders
- files Git should ignore (
.gitignore, also.ignore) are left out, even outside a repository. That is why ⌘P usually finds nothing invendor/ornode_modules/. - hidden files such as
.envare included, the.gitfolder never - the list follows new, deleted and renamed files by itself
⌘P doesn't search attached folders. You find their files through Search everywhere or in the project tree.
Switching to commands
Start your input with > and the box becomes the command palette, as in VS Code.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| "Nothing found" although the file exists | it is in a folder .gitignore excludes, or in an attached folder |
open it from the project tree or search its content with ⇧⌘F |
| The list stays empty without typing | no project is open | open a folder |
See also
Recent files Free
Recent files shows the files you just worked with: first the open tabs in the order you last used them, then the recently closed ones. That way you jump back and forth between two or three files without scanning the tab strip.
Where to find it
- ⌘E
- Go › Recent files in the menu bar
How to do it
- Press ⌘E.
- Type to filter the list by file name. Each name has its path in the project next to it.
- Select with ↑/↓. ↩ brings the tab to the front or opens the closed file again.
The list shows up to 40 files, and only files, no tools or terminals.
Related
- ⇧⌘T brings back a tab you just closed (Tabs).
- Recently opened projects are in the project menu of the title bar (Projects and windows).
See also
Search everywhere Free
Search everywhere is one search box over everything the editor knows: files, tools, sites, launchers, commands, settings, Git branches, database tables, servers and more. Matches are sorted into categories you switch between with Tab.
Where to find it
- ⇧⇧: press Shift twice in quick succession. This doesn't work in the terminal, where Shift belongs to the program.
- Click into the search field in the middle of the title bar. What you type there goes straight into the box.
- View › Search everywhere in the menu bar
How to do it
- Press ⇧⇧ and type your term.
- The All category shows the best matches of each category, with the category's name on the right.
- ⇥ switches to the next category, ⇧⇥ back. Or click a category at the top.
- Select with ↑/↓ and press ↩.
In All the list stays empty until you type, showing "Type to search · ⇥ switches the category". Many categories list everything they have in their own tab even without input.
Categories
| Category | What you find | ↩ does |
|---|---|---|
| Files | project files, as with ⌘P | opens the file |
| Text | the entry Find “term” in files | opens Find (⇧⌘F) with your term |
| Tools | every tool window that is switched on, with its shortcut | opens the tool |
| Sites | your sites from WebDonkey | opens the site's project folder |
| Launchers | the project's launch commands | runs the launcher, see Launcher |
| Commands | every command, as with ⌘K | runs the command |
| Settings | every setting, also by English terms and keywords | opens the settings right at that row |
| Git branches | local and remote branches, marked as current, local or remote branch | for the current branch: opens the Git window; otherwise switch: checks the branch out, a remote branch is created as a local branch |
| Service configs | configuration files of WebDonkey's services, such as php.ini or nginx, Apache and Caddy files, by name, service or version |
opens the file; files that are part of Premium only with Premium |
| Tables | tables of your databases, with database and connection | opens the table |
| Servers | your server connections and, in this tab only, file names on the connected server | connects in the Remote window or opens the file |
| AI chats | your conversations with the local AI | opens the chat |
| Notes | the notes of the active brain | opens the note |
Which categories you see depends on your setup:
- Sites and Service configs need WebDonkey.
- Tables knows the tables of your site's database and the tables the Database window has listed once.
- Launchers, AI chats and Text are missing when their tool is switched off.
File names on the server
In the Servers tab, the editor searches for file names below the server folder you are working in. This happens in this tab only, never under All: the first search starts a run on the server whose result the editor keeps for ten minutes. If the server is busy or the folder is very large, the list shows a notice. Clicking it searches anyway.
Free and Premium
Search everywhere is free. The Servers and Notes categories are part of WebDonkey Premium and don't appear without it.
See also
Run scripts Free
The scripts from your project's package.json and composer.json are commands in the command palette, in the Scripts group. You start npm run dev or composer test with a few keys, without opening a terminal and typing the command.
Where to find it
Press ⌘K and type the script's name.
How to do it
- Press ⌘K and type the name, such as "dev" or "build".
- Select the entry, such as npm run dev, and press ↩.
- The editor opens a new terminal in the folder the script belongs to and runs the command there. The terminal is named after the command.
Where the scripts come from
| File | Palette entry | What runs |
|---|---|---|
package.json |
npm run name, pnpm run name, yarn run name or bun run name | the script with the package manager whose lock file is in the folder (pnpm-lock.yaml, yarn.lock, bun.lockb or bun.lock, otherwise npm) |
composer.json |
composer name | composer run-script name; Composer's own hooks starting with pre- or post- are left out |
With attached folders, the list holds the scripts of every folder, with the folder name after a dot, such as npm run dev · shop-theme. Saving a package.json or composer.json refreshes the list.
More than scripts: Launcher
The Launcher tool window goes further: it detects launch commands from many sources, such as Makefiles, Docker Compose or VS Code tasks, and starts them with one click. You also find launchers in Search everywhere under Launchers and in the bar at the top of the title bar. Before the first start in a project, the editor shows the exact command there and asks whether you trust the project. See Launcher.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| No scripts in the list | the project has no package.json or composer.json with scripts, or the file isn't valid JSON |
check the file and save it |
| The terminal says "command not found" | npm, pnpm, yarn, bun or composer isn't installed or not on the path | install the package manager |