Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runwita.com/llms.txt

Use this file to discover all available pages before exploring further.

Hit ⌘K anywhere in Runwita and a launcher palette opens. Type a few characters, hit Enter. That’s the whole interaction. The point is to keep your hands on the keyboard. Hunting through sidebars and menus to mark an action done, or to jump to a journey by name, is wasted motion when you already know what you want.

​
What you can do from ⌘K

The bar exposes verbs whose plumbing already works. Stub features don’t appear, so anything in the list will do something when you hit Enter.
Verb classWhat it does
Jump toNavigate to Home, Inbox, Journeys, Contacts, or Settings. Single keystroke after the letter.
Open journeyType any part of a journey’s customer or use case. The matching journey lands at the top. Enter opens it.
Open engagementType any part of an engagement title. Enter deep-links to it on its journey, with the timeline scrolled into position.
Mark action doneType any part of an action. Enter expands the row into a confirm card with a before/after preview. Second Enter commits the change.
CaptureType capture followed by your note. Enter sends the note to the scratchpad. Useful when you’ve thought of something mid-task and don’t want to lose it.

​
How matching works

Subsequence with proximity. The characters you type all have to appear in the row’s text in the same order, but not adjacent. Bonus weight for hits in the title and earlier in the string. Case-insensitive. So “mapldig” finds “Maplewood Inn, digital ordering rollout”. You don’t have to type whole words. If your query produces nothing, two likely reasons:
  • The verb plumbing isn’t wired yet (e.g. setting a deal stage from the bar isn’t in the registry yet, intentionally hidden until it works).
  • Your character order doesn’t match anything. Try fewer characters or a different word.

​
Two-tier execute

Most rows execute on Enter and the bar closes. Mutations (currently only Mark action done) take an extra step:
  1. First Enter expands the row into a confirm card showing the before/after.
  2. Second Enter commits.
  3. Esc backs out of the confirm card. A second Esc closes the bar.
This is intentional. Navigation is cheap, mutation isn’t. The two-keystroke commit prevents accidentally checking off the wrong action because it sat near the top of your search results.

​
What’s NOT in ⌘K (yet)

The roadmap items currently hidden:
  • Set deal stage manually. Runs through Intelligence today, manual override coming.
  • Reschedule actions. Edit due dates without opening the engagement.
  • Export PDF. Once PDF export ships, it’ll be here.
  • Ask AI. Fuzzy intent resolution against the whole journey graph. “Where did we land on the Maplewood pricing?” answered without you picking the right command.
These appear once they’re real. The bar deliberately doesn’t show stubs.

​
Trigger and shortcuts

  • ⌘K anywhere in the app opens the bar (Ctrl+K on Linux/Windows builds, when those land).
  • Click the Search chip in the left sidebar opens the same bar.
  • Esc closes it.
  • ↑ and ↓ to move through results.
  • Enter to execute.
The bar is rendered at app root as a full-screen overlay, so it floats above any page. State you had on the page (scroll position, expanded sections, in-progress edits) is preserved when the bar closes.

​
When to reach for it

Three scenarios where ⌘K beats clicking:
  1. You know the journey by name. Faster than scrolling the Journeys list.
  2. You want to clear an action off your plate. ⌘K, type the action, Enter, Enter. Three seconds.
  3. You’re mid-thought and want to capture a note. Don’t switch context to Inbox; ⌘K, type capture, dump the thought.
For everything else (browsing engagements on a journey, editing inline, comparing two journeys side by side), the regular UI is the right tool.

​
What’s next

Home

Where ⌘K lands when you Jump to Home.

Journeys

The objects ⌘K is mostly searching against.