> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/intelligence/chatbot/history.md). # History Find, organize, and manage your saved CRAFTSMAN INTELLIGENCE chats with Favorites, project grouping, search, and per-chat options. Every conversation you have with CRAFTSMAN INTELLIGENCE is saved automatically. The **History** menu is where you go back to those conversations, mark the ones you return to often, and keep the list tidy. ### Opening History Click the **History** button in the chatbot header. The menu opens alongside the chat and lists your saved conversations by name. Click any chat to open it. The menu closes and the conversation loads in the chatbot, with everything from where you left off. Your current chat is saved before you switch, so nothing is lost. {% hint style="info" %} *You do not need to save chats manually. Sending your first message in a new conversation adds it to History right away.* {% endhint %} ### How Chats Are Grouped The History menu sorts your chats into up to three groups, from top to bottom: **Favorites** lists every chat you have marked as a favorite, no matter which project it was started in. This section only appears once you have at least one favorite. Favorited chats also remain in their project or general history group. **Your current project** is labeled with the project's name and lists the chats you started while working inside that project. This section only appears when you are inside a project. **Everything else** sits below, with no label, and lists the rest of your chats. Within each group, the most recently used chat is at the top. Opening a chat or sending a message in it moves it up the list. {% hint style="info" %} *Every chat is available from anywhere. The project group is there to surface the chats most relevant to where you are working, not to hide the others. When you open History inside a project, that project's chats are gathered at the top and everything else sits below. Outside of a project, or in the full-screen chatbot, the same chats appear in one list.* {% endhint %} ### Searching History Click the **Search** icon at the top of the menu, or press **⌘F** (**Ctrl+F** on Windows) while the menu is open, to reveal a search field labeled **Search History...**. The list filters as you type, showing only chats whose names match. Groups with no matching chats are hidden until you clear the search. Closing the menu clears the search as well. ### Managing a Chat Hover over any chat in the list and click the **Options** button that appears on the right. A small menu opens with three choices: **Rename** lets you change the chat's name. The new name appears in the list, and in search results, immediately. Descriptive names such as "End card redesign" or "Q4 variant batch" make chats much easier to find later. **Favorite** adds the chat to the **Favorites** group at the top of the menu. Choosing it again on a chat that is already a favorite removes it from **Favorites**. **Delete** asks for confirmation, then removes the chat from your History. If the chat was a favorite, it is removed from **Favorites** too. Choosing any option, or clicking anywhere outside the menu, closes it. --- # 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.craftsmanplus.com/intelligence/chatbot/history.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.