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

# Search history

View and manage search history in Tellius—track past queries, apply filters, bookmark searches, and revisit insights to streamline data exploration.

Tellius maintains a comprehensive record of all your search queries, enabling you to effortlessly track and revisit your data exploration journey. Using any relevant word or phrase, you can easily retrieve the required search results.

* Bookmark important queries for quick access, making it convenient to revisit.
* Tellius filters your search history to show only valid queries.
* Remove unwanted queries to refine your search recommendations.
* Your search history is private and not accessible to administrators or other users.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/h792B5f74weOJ3wsq865/image.png" alt="" width="271"><figcaption><p>Search history panel</p></figcaption></figure>

The panel displays all your searched queries and offers the ability to filter them based on the business view and a custom date range.&#x20;

* In the search bar, search for any previously rendered query by using the keywords or phrases used.
* Click on the dropdown to view the search queries associated with a specific Business View.
* Click on Custom Range to view the search queries from a specific date range.

<br>


---

# 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.tellius.com/search/search-history.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.