> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/chrome-extension/command-palette.md). # Command palette Use the command palette to find a meeting link or start a handoff without opening the side panel. The default Chrome shortcut is **Alt+Shift+D**; on Mac, use **Option+Shift+D**. The assigned shortcut may differ if you or Chrome have changed it. Check the shortcut setting in Distro's extension settings. Type to search. Use the arrow keys to select an entry and **Enter** to open it. Link entries let you copy a link or open the available scheduling actions. Saved favorites appear under **Preferred**. Choose **Book a new meeting** to start a sales handoff. On pages where Distro detects supported contacts, **Book for a contact on this page** helps you select the prospect first. The Distro web app also has a search control in its header. Its **⌘K** shortcut is separate from the extension's browser shortcut. If the extension shortcut isn't assigned or conflicts with another extension, change it through the shortcut setting and Chrome's extension keyboard shortcuts page. You can continue to use Distro's visible controls while resolving the shortcut. ## Book through a personal or group link Choose a personal or group link, open its actions, and select **Book a meeting** when available. Pick an available time, enter the guest details, and review the booking before confirming. This uses that link's host or participants; it doesn't start a routed sales handoff. --- # 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://help.distro.so/integrations/chrome-extension/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.