Keyboard shortcuts and command palette
Keyboard shortcuts speed up familiar workspace actions. Learn the visible control first so you can recover when focus changes or a shortcut behaves differently.
What this page covers
Complete command-palette behavior and shortcut inventory, including platform differences and conflicts.
Focus rules
Shortcuts depend on focus. The same key can behave differently when focus is inside the note editor, chat input, source viewer, map, sidebar, or command palette.
If a shortcut does not work, click the surface you intend to control and try again.
Shortcut areas
| Area | Shortcut purpose |
|---|---|
| Command palette | Open actions and destinations quickly. |
| Editor | Format text, move through content, and edit notes. |
| Chat | Submit prompts or manage input focus. |
| Source viewer | Move through documents, pages, or search results. |
| Map | Move through visual nodes and map controls. |
| Workspace | Switch panels, tabs, or active surfaces. |
Discovering current shortcuts
Atlas may expose shortcuts in tooltips, menus, the command palette, or visible shortcut hints. Treat the in-product list as the source of truth because shortcuts can change as the workspace evolves.
Common failure cases
| Symptom | Cause | Fix | |---|---| | Shortcut types into a field | A text input has focus. | Leave the input or use the visible control. | | Shortcut does nothing | Wrong panel has focus. | Click the intended panel. | | Browser intercepts the shortcut | The browser owns that key combination. | Use the menu or command palette alternative. | | Shortcut differs by OS | Modifier keys vary. | Check the visible hint on your device. |
Accessibility note
Every critical action should also be available through visible UI. If a workflow only seems possible with a shortcut, search the command palette or inspect the relevant panel controls.
Use the command palette
The command palette is the fastest way to find actions and open project material without moving through the visible navigation.
What it can find
Depending on the active workspace state, the command palette can surface:
- project actions
- sources
- notes
- map or workspace commands
- navigation targets
- searchable project terms.
Commands can appear or disappear based on context. For example, editor actions are most relevant when a note editor is active, while map actions are most relevant when the map is active.
Search behavior
The palette works best with exact names:
- source title
- note title
- action label
- project concept
- visible UI command.
If you cannot find an action, try the verb first: "open", "create", "search", "import", "map", or "note".
Context and permissions
Some actions require a project, selected source, active note, processed content, or account permission. Those actions may be hidden, disabled, or fail with a state-specific message when the requirement is missing.
Quick inputs
| Input | Likely result |
|---|---|
| Source title | Open a source. |
| Note title | Open a note. |
| Action name | Run or reveal a command. |
| Concept term | Find related project material. |
When to use visible navigation instead
Use the sidebar, tabs, or panels when you need to understand project structure, compare multiple items, or teach someone else where an action lives. Use the command palette when you already know what you want.