> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/chat/managing-chats.md). # Managing your chats Start new chats, search your history, edit or regenerate answers, and stop a reply. > **Beta** — opened on request. Contact to request access. ## Starting and finding chats Start a fresh conversation with **New chat**. Your past chats are listed in the sidebar by title and date — click one to reopen it. **Search** finds chats and messages across your history, so you can get back to an earlier answer. You can **rename** a chat to keep the list tidy, or **archive** one you no longer need. ## Editing, regenerating, and other versions You can **edit** a question you already asked and re-send it, or **regenerate** an answer to get a fresh reply. When you edit or regenerate, Chat keeps the previous reply as an alternate **version**, so you can move between versions to compare them. ## Stopping and copying While Chat is answering, **Stop** ends the reply where it is and keeps whatever it had already written. **Copy** puts an answer on your clipboard to paste elsewhere. --- # 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://support.sayprimer.com/primer/chat/managing-chats.md?ask=&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.