> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/reviewing-variants/search.md).

# Search across variant types

The **Search** tab finds every variant in the genes you name, across all variant types at once: small, structural, copy number, tandem repeat, paralog, and methylation. Use it when you have a candidate gene in mind and want to see everything the case holds for it, not just the priority findings.

The Search tab sits between **Summary** and the variant-type tabs. You can also reach it from **Search all variants →** on the [Summary tab](/products/workbench/variant-interpreter/getting-started/the-summary-tab.md).

## Running a search

1. Open the **Search** tab. Nothing loads until you search.
2. In **Genes**, type a gene symbol and press Enter. Add as many genes as you need.
   * To start from the case itself, click one of the suggested genes: genes the pipeline flagged in this case. These are a starting point, not a filter.
3. Review the results. A strip above the table shows how many matches each variant type returned (**SNV**, **SV**, **CNV**, **TR**, **PARA**, **METH**).
4. Switch between **All variants** (the default) and **Priority only** to narrow the list to priority findings.
5. Click a row to open the variant drawer. Use its previous/next controls to step through the search results.

## The results table

| Column                       | Description                                                                                                                |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Type**                     | The variant type.                                                                                                          |
| **Gene**                     | The gene that matched your search.                                                                                         |
| **Automated Classification** | The pipeline's own classification.                                                                                         |
| **User Classification**      | A reviewer's classification, where one was made.                                                                           |
| **Relation**                 | How the variant relates to the gene: **in gene** (annotated to it) or **overlaps** (within the gene or within 2 kb of it). |
| **Coordinate**               | The variant's location.                                                                                                    |
| **Effect**                   | A one-line summary, tailored to the variant type.                                                                          |

{% hint style="warning" %}
If a search matches more variants than can be listed at once, a warning asks you to narrow it. Search fewer genes to be sure nothing is missed. If one variant type couldn't be searched, the page says so; don't read its absence as a negative result.
{% endhint %}


---

# 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.omics.ai/products/workbench/variant-interpreter/reviewing-variants/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.