> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/platform/command-search.md).

# Command Search

Use Pylon's powerful Command Search to search, navigate, and perform commands in Pylon.

{% hint style="info" %}
Hit `Cmd-K` on Mac and `Ctrl-K` on Windows anywhere in Pylon to open up Command Search.
{% endhint %}

## Search

Type a search term to search across all data in Pylon, including issues, accounts, contacts, knowledge base articles, and more. You can click into a specific tab to narrow down your results, or use the keyboard shortcuts listed at the bottom of the search window to preview different results before you select a specific page to view.

To jump straight to an issue, type its number, such as `1234` or `#1234`.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FPts43QgEkuMBdJRyCxC2%2FCleanShot%202024-09-29%20at%2017.14.37.png?alt=media&amp;token=2c848c88-e10b-457a-be68-79b1e1dac4a7" alt=""><figcaption></figcaption></figure>

## Search page

For deeper searches, click the **Search** icon at the top of the left navigation to open the full Search page. It has the same tabs as Command Search (**All**, **Issues**, **Pages**, **Accounts**, **Contacts**, and **Commands**), plus:

* **Filters**: narrow results using the fields for the selected tab. For example, the **Issues** tab offers the same filters as issue views.
* **Exact match**: only show results that contain your exact search term.
* **Sort**: on a specific tab, order results by **Relevance**, **Last updated**, or **Last created**.
* **Issue preview**: click an issue to open it in a side panel and work on it without leaving your results.

Press `Cmd-[` and `Cmd-]` (`Ctrl-[` and `Ctrl-]` on Windows) to switch between tabs.

## Commands

Run commands, like `Create issue` or `Create article` to quickly take an action without having to navigate to the corresponding view in the UI.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FOqu5UbWRyEvsH2cRIbGy%2FCleanShot%202025-03-27%20at%2000.56.03%402x.png?alt=media&amp;token=8af7e519-e65e-418b-8bc2-9bc7d5012cec" alt=""><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/platform/command-search.md?ask=<question>&goal=<user_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.
