v1.0 — Now available for macOS · Press ⌘ Space to launch
← Back to blog

How to migrate from Spotlight to CmdSpace on macOS Tahoe

CmdSpace Team·

Spotlight on macOS Tahoe 26 looks better than ever. It also breaks more than ever. If you have ever watched mdworkershared pin a CPU core for an afternoon, or asked Spotlight for a file you know is on disk and gotten a blank result page, y…

Spotlight on macOS Tahoe 26 looks better than ever. It also breaks more than ever. If you have ever watched mdworker_shared pin a CPU core for an afternoon, or asked Spotlight for a file you know is on disk and gotten a blank result page, you already know the story. This guide is a calm, keyboard-first migration plan: keep the parts of Spotlight that still work, move the daily-driver hotkey onto a local-only launcher, and stop fighting indexer storms after every macOS update.

The launcher we use here is CmdSpace — a local-only, keyboard-first launcher for macOS. It is $29 one-time, no subscription, no remote sync, no telemetry. If you would rather try a different launcher, the same migration steps still apply; only the install step changes.

Why move off Spotlight at all

Spotlight is not bad on paper. It is system-integrated, it lives behind ⌘Space by default, and on Tahoe 26 it finally gained a real command palette UI with Apps, Files, Actions, and Clipboard tabs reachable via Cmd+1/2/3/4. The problem is that the underlying indexer has been unstable for two macOS generations. Notebookcheck has tied unusual SSD wear on Sequoia to runaway Spotlight indexing. The same family of bugs survived into Tahoe 26 — TidBits threads from 2026 are full of users reporting Spotlight refusing to index user files on OS 26.

A few quotes from public threads that captured the mood for me:

my spotlight is still broken

Spotlight searching on macOS just breaks and forcing a rescan can fix it for a while

If your machine is healthy, you may never see it. If you are a developer with a busy node_modules tree, or a writer with thousands of files, or anyone who has just installed a .x.0 macOS release, you will. The migration below assumes you have hit the issue at least once and want a backup plan.

What "migrating" actually means

You are not turning Spotlight off. Spotlight powers far more than the ⌘Space panel — it backs Finder search, Mail search, the Photos library, and a long list of system features. Disabling it entirely will break those.

What you are doing is two things:

  1. Rebind the ⌘Space hotkey from Spotlight to your new launcher, so the muscle memory still works.
  2. Trim Spotlight's indexing scope so it stops fighting your dev tree and your external drives.

Both are reversible in under a minute.

Step 1 — Install CmdSpace

Download CmdSpace from cmd-space.app, open the .dmg, drag the app into /Applications, and launch it once. On first launch CmdSpace asks for Accessibility and Full Disk Access. Both are required for a launcher on Tahoe 26: Accessibility for the global hotkey, Full Disk Access so CmdSpace can read file metadata locally without bouncing through Spotlight.

CmdSpace's index is local-only and lives at ~/Library/Application Support/CmdSpace/index. It is a Rust-backed inverted index — sub-25ms search latency on a 250k-file tree on an M-class Mac in my own testing. No telemetry, no calls home; you can verify by pointing Little Snitch at the bundle.

Step 2 — Rebind ⌘Space

Open System Settings → Keyboard → Keyboard Shortcuts → Spotlight, and turn off the "Show Spotlight search" shortcut. Spotlight will keep indexing; only the hotkey detaches.

Then open CmdSpace's preferences (CmdSpace menu → Settings → Hotkey) and set the activation hotkey to ⌘Space. CmdSpace will warn you if Spotlight is still holding the shortcut — accept the override.

A common pitfall: some users assign ⌘Space to CmdSpace while Spotlight still owns it. macOS resolves the conflict silently and you get neither launcher. Always clear Spotlight's binding first.

If you also use the Siri / dictation hotkey, leave those alone. They are independent.

Step 3 — Tame Spotlight's indexing scope

Now that ⌘Space goes to CmdSpace, you can shrink Spotlight to the bare minimum it needs to keep system features working.

Open System Settings → Spotlight → Search Results, and uncheck everything you do not actually search for through Spotlight: Suggestions from Apple, Web Searches, Movies, Music, Bookmarks & History, Mail & Messages, Siri Suggestions. Most users can safely leave Applications, System Settings, and Documents enabled.

Then open the Privacy tab and add the paths that hurt your indexer the most. Common offenders for developers:

  • ~/Developer (or wherever your repos live)
  • Any folder that contains node_modules, .venv, .build, target, or vendor
  • External drives, especially Time Machine targets and removable SSDs

You can also do this from the command line if you have many trees:

sudo mdutil -i off /Volumes/Backup
sudo mdutil -i off ~/Developer

To re-enable later:

sudo mdutil -i on ~/Developer

If Spotlight is still spinning hours after the change, force a rebuild of the system volume's index:

sudo mdutil -E /

OSXDaily has a longer fix-it guide for when the index itself is corrupted; the steps are identical on Tahoe 26.

Step 4 — Move the daily commands over

This is the part where keyboard-first launchers earn their keep. Spotlight on Tahoe 26 has tabs, but every command is still mouse-or-arrow driven inside its own modal UI. CmdSpace runs everything through a single command line:

  • calc 1024 / 7 → inline calculator, result on the same row
  • kill 3000 → kill the process bound to port 3000 (uses lsof under the hood)
  • clip → clipboard history, ⌥1…9 to paste
  • :emoji rocket → emoji picker, no menu bar dance
  • dict mercurial → dictionary lookup
  • gh open → opens the GitHub page for the current Git repo

None of these require ever leaving the keyboard, and none of them call out to a server. If a command needs the network, CmdSpace tells you and asks first.

Step 5 — Verify the migration

Spend one normal working day on CmdSpace before deleting anything. At the end of the day, check three things:

  1. ⌘Space still feels like ⌘Space. If your fingers reach for it without thinking, the muscle-memory transfer worked.
  2. mdworker_shared in Activity Monitor is no longer above 30% CPU for sustained periods. If it is, an indexed path on your Privacy list slipped through — add it again.
  3. Finder search inside a specific folder still works. (It should — you only narrowed Spotlight's scope, you did not disable it.)

If anything is broken, every step above is reversible: re-enable Spotlight's ⌘Space shortcut, remove the privacy exclusions, and you are back where you started. Spotlight's index will rebuild itself on the next idle cycle.

What about Tahoe 26's new Spotlight UI

Tahoe 26's Spotlight redesign is genuinely nicer than the old single-row list. The tabs help. Apple Intelligence inline answers are interesting if you opted into Apple Intelligence. They are also opt-in, and you should know what you are opting into — Apple has published a privacy guide for Apple Intelligence that is worth a read. If you want a launcher that has no AI surface at all, CmdSpace is what we ship; if you want AI inside your launcher, Spotlight on Tahoe is now a credible option for the first time in years.

The two are not mutually exclusive. Most of the people I know who migrated kept Spotlight installed and indexing a narrow scope, and put their daily hotkey on a third-party launcher. That is the configuration this guide leaves you in.

Sources