If you write one book at a time, clicking through menus and tabs is a minor annoyance. If you're managing three, five, or a dozen books at once — sequels, a backlist, a box set, a ghostwriting project — those clicks add up to real lost time. The Ctrl+K command palette shortcut (Cmd+K on Mac) exists to solve exactly this problem: it lets you jump anywhere in your writing software by typing instead of hunting.

Command palettes started in code editors like VS Code and Sublime Text, then spread to tools like Notion, Linear, and Slack because the pattern works so well. Type a few letters, see a filtered list, hit enter. No sidebar scrolling, no remembering which folder something lives in. For authors running multiple books through the same software, it's one of the highest-leverage habits you can build — but only in the places where it actually works.

Where the Ctrl+K command palette is available

Ctrl+K opens a searchable jump-to box, but it only works outside the manuscript text itself. This is the important constraint that changes how and when you use it:

  • In the Library — press Ctrl+K to jump straight to any book by name, or to Settings.
  • In the editor's sidebar and toolbars — Ctrl+K switches views (Writing / Formatting / Corkboard / Outline / Plot / Map / Workshop), jumps to any chapter by title, or takes you back to the library.
  • NOT while your cursor is in the manuscript page — Ctrl+K is reserved there for the Link function, creating or editing links in the text itself. Click outside the page, or use the **Command palette button** on the right-hand icon rail instead.

Type to filter, use ↑/↓ to move through results, Enter to go, Esc to dismiss. It's quick once you trust it.

What the command palette actually lets you do

At its core, Ctrl+K is a context-aware search box that lives above your normal navigation. Press it (outside your manuscript), and a small overlay appears. Depending on where you are, it can jump you to:

  • A specific book in your library
  • A chapter or section inside the current manuscript
  • A character, place, or group in your story codex
  • A different editor view — Writing, Corkboard, Plot, Workshop tabs
  • A settings page or tool you don't open often
  • The library, from anywhere in the app

The point isn't that any single jump saves much time. Clicking "Library," then scrolling to find a title, then clicking into the right chapter might cost you eight or ten seconds. The command palette gets you there in two. But multiply that by the dozens of times a day you switch context — checking a character's detail in book two while drafting book four, or pulling up your outline — and it adds up to minutes, then hours, over a project.

Why it matters more as your library grows

Most writing software is designed and demoed with one manuscript open. Navigation feels fine because there's nothing to navigate between. The friction shows up later, once you've published book one and started building a series or a backlist.

Say you're three books into a series. Book one needs a typo fixed before a promo. Book two is mid-draft. Book three is an outline you're fleshing out. A book of short stories is sitting half-finished from last year. Every one of these lives in the same app, and every time you switch between them you're paying a small navigation tax — unless you can just type the title and go.

This is where menu-based navigation starts to show its age. A sidebar that lists five books is fine. A sidebar that lists twenty gets scrolled, squinted at, and eventually ignored in favor of whatever tab happens to still be open. A command palette doesn't care how long the list is, because you're not browsing it — you're filtering it by typing.

How to build the habit

The fastest way to make Ctrl+K stick is to stop using the alternative. For one week, resist clicking through your library sidebar or menu tree, even when it's right there. Force yourself to hit the shortcut and type instead. It'll feel slightly slower at first, because typing a book title is a new motion and clicking a familiar link isn't. By day three or four, the shortcut usually wins on raw speed, and by the end of the week it's automatic.

This matters more than it sounds like it should. Time-poor authors don't lose hours to any single bad workflow habit — they lose it in five-second increments, dozens of times a day, across months of drafting and editing a backlist. A command palette shortcut is a small fix for a problem that compounds.

One practical note: the first time you use it in the manuscript, you'll likely accidentally hit Ctrl+K while typing and trigger the Link function instead of the palette. That's the reminder to click outside the page first, or hit the palette button on the sidebar. After a week it becomes automatic — click outside, then Ctrl+K.

Other shortcuts worth learning alongside it

Ctrl+K rarely travels alone. Most writing software that implements a command palette pairs it with a handful of other shortcuts that reduce mouse dependency:

  • Ctrl/Cmd+Shift+F for Find & Replace within a chapter or across the whole book — distinct from hunting for a specific chapter, which is what Ctrl+K does when you're already in the manuscript.
  • Ctrl/Cmd+S to force a save, even in apps with autosave, for that moment of paranoia before closing the laptop.
  • Ctrl/Cmd+B and Ctrl/Cmd+I for bold and italic — standard but easy to forget you don't need the toolbar for.
  • Ctrl/Cmd+Shift+L to toggle dark mode, reachable from anywhere in the app.
  • Ctrl/Cmd+Z and its redo counterpart, especially useful when testing a formatting change you might revert.

None of these are exotic. The value is in not thinking about them — reaching for the shortcut before your hand even considers the mouse. That only happens with repetition, so it's worth deliberately using each one for a week even when clicking would be just as fast in the moment.

If you're evaluating writing software and want a quick sense of how much friction a given tool removes from daily tasks, Pendrilo's free tools page offers five no-login calculators and checkers — no account required, and they'll give you a feel for how the rest of the app handles the work around your manuscript. And if cross-book search, a shared codex, and jump-anywhere navigation sound like what your growing library actually needs, you can try Pendrilo and see how it handles a real, multi-book workflow rather than a single-manuscript demo.