> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/chat-with-your-data/conversation-history.md).

# Conversation History

AskCorral conversations are saved, so an analysis you started yesterday — or a build the Agent was midway through — is never lost when you close the panel. See [HIPAA, PHI and AI](https://docs.corraldata.com/kb/security-and-privacy/hipaa-phi-ai.md) for how conversations are stored.

### How it works

Open the history list from the AskCorral panel to see your past conversations, each with an automatically generated title. From there you can:

* **Resume** any conversation and pick up exactly where you left off — the full thread and context come back with it. Each conversation has its own link, so you can bookmark or share one with a teammate on the account.
* **Pin** the conversations you return to often so they stay at the top of the list.
* **Rename** a conversation when the auto-title isn't how you think of it.
* **Delete** a conversation you're done with. Deleting also removes any files you attached to it.

If the Agent is still working when you open your history or switch views, the run keeps going — you can jump back into the conversation and watch it finish.

{% hint style="success" %}
**Tip:** Long-running analyses make great pinned conversations — keep your weekly performance review thread pinned and just ask "same review for this week" each Monday. The Agent carries the context forward.
{% endhint %}

{% hint style="info" %}
If you're having trouble and require technical assistance, feel free to reach out to <support@corraldata.com>.
{% 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.corraldata.com/kb/chat-with-your-data/conversation-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.
