> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/getting-started/command-palette.md). # Command Palette The command palette is a keyboard overlay for getting anywhere in App Maker without walking the menu tree. Press one shortcut, type a few letters, press Enter — the palette takes you to the project, page, or build you meant. It is navigation only: every row takes you somewhere. Nothing in the palette creates, changes, or deletes anything. ## Opening the Palette Press **Cmd+K** on macOS, or **Ctrl+K** on Windows and Linux, anywhere in App Maker once you are signed in. The shortcut deliberately stays out of your way while you are typing: if the cursor is inside a text field, a text area, or any other editable box, Cmd/Ctrl+K does nothing. Click outside the field first, then press the shortcut. You can also click the search bar in the header — labelled **Jump to…**, with a ⌘K badge — to open the same palette with the mouse. ## Reading the Panel The palette opens as a centered overlay over the page you were on. At the top is a single search field with the placeholder **Search or jump to…**; below it, results grouped under section headings; at the bottom, a reminder of the keys that work here: * **↑ ↓ Navigate** — move between rows. * **↵ Select** — go to the highlighted row. * **esc Close** — dismiss the palette. * **⌘K / Ctrl K Open** — the shortcut that opened it. Arrow keys run through the whole list, crossing section headings, and wrap around at either end. You never need the mouse, but clicking a row works too, and clicking the dimmed area outside the panel closes it.
Closing the palette clears the search field — reopening it always starts from a blank query, not from wherever you left off. ## The Sections With the search field empty, the palette shows four sections in this order. Typing adds a fifth, **Deployments**, between Projects and Navigation. ### Recents Your **three** most recently started builds and CodePush updates, across every project you work in — so the first thing an empty palette shows you is what you were last doing. Each row shows the build's tag, its platform icon, the target and kind (for example `Production Build` or `Staging CodePush`), its build number, and its current status. Selecting a row opens that build or update's detail page — for a CodePush update, that exact update, not the project's latest one. Recents does not search. The moment you type the first character it removes itself, leaving the sections that do. ### Projects The **five** most recently active projects in the organization you are working in, each row carrying the project's three main destinations. Typing filters these rows by project name. * **Enter** on a project row opens its **Dashboard**. * The three small icons at the right edge of the row are shortcuts to that project's **Dashboard**, **Settings**, and **Deployments** — click the one you want. Draft projects are left out, since they cannot be opened. If your role does not allow opening project detail pages, the whole section is absent. Because the section holds the five most recently active projects rather than the full list, typing narrows *those* five — it is not a search across every project in the organization. Use the [Projects](/tutorials/app-maker/projects.md) page to find an older one. ### Deployments Appears as soon as you type. It searches the builds and CodePush updates of every project in the organization you are working in by **tag**, and lists up to **five** matches. Each row shows the tag, its platform icon, the target and kind (for example `Production Build` or `Production CodePush`), its build number or CodePush label, and its current status. Selecting a row opens that build or update's detail page — for a CodePush update, that exact update. If your role does not allow opening project detail pages, the section is absent.
### Navigation The pages that exist regardless of which project you are in: **Projects**, **Dependency Management**, **Upgrade Helper**, **Plugins**, **Release Tracker**, **Users**, **Roles**, and **Invitations**. Typing filters them by name. ### Account Your own pages, separate from any organization: **Profile**, **Language Settings**, **Notification Settings**, **User Access Token**, and **Public Keys**. ## Searching Typing filters each section against what you see on screen — project rows match on the project's name, and page rows match on the page's label in your current language, so searching in Turkish finds Turkish labels. **Deployments** is the exception: it searches the organization's builds and CodePush updates by tag, starting a moment after you stop typing. A section with no matches disappears rather than showing an empty heading. When nothing in the palette matches, you get a single **No results found** message instead. While Recents, Projects and Deployments are still loading, the palette shows placeholder rows and waits before saying it found nothing. ## Permissions The palette never lists a destination you could not reach by navigating. Pages your role does not grant, features not enabled for your organization, and organization pages while you are not acting in an organization are all simply absent — not greyed out. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.akinon.com/tutorials/app-maker/getting-started/command-palette.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.