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

# Recent Search History

Browsing your archive search history with Solar Archive is straight forward, head over to the "History" page by using the link in the top navigation bar. Once you're on the History page, you'll be able to see your Recent, Saved, and Shared Searches. Navigating to any of the search type tabs will show you the corresponding searches that you have performed. Clicking on any of the searches will replay that search automatically for you and allow you to edit the search in the search panel window. (Learn more about Search Panel Window)<br>

### **Recent Searches**

This tab showcases all of the recent searches you have performed on the archive with the properties (Keywords, Recipients, Attachments, Date Range, and Results) that were set when carrying out that specific search. You can click on any of the recent searches to replay this search.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.solar-archive.com/docs/using-the-archive/history/recent-search-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.