Storing DuckAI chat history

The simple answer to this is that one just downloads the files listed on the Duck.ai page and that is just a matter of remembering to do that after each chat. However it prompted the question as to just where is this information stored. As the blog post point's out, the information is only stored locally, so just how is the list on the page managed? A question that I was helped to solved in that chat.

The chat itself needed some help in giving the right answers and I do not believe that Mistral actually has the right information IN it's training data. The identified storage name was 'chatHistory' but in Firefox at least it's 'savedAIChats'. Mistral keeps saying this can be downloaded from the developers screen (the F12 button pop-up) but this is not the case. The only way I managed to download the raw data from the storage database was via a javascript script which at some point I think I can create a local web page to handle this although how I access the https://duckduckgo.com section is the next question. The script is :-

// Get the savedAIChats data from local storage
const savedAIChats = localStorage.getItem('savedAIChats');

// Log the data to the console
console.log(savedAIChats);

// Optionally, you can also parse the JSON data if needed
const chatHistory = JSON.parse(savedAIChats);
console.log(chatHistory);

As you can see Mistral keeps it's own name for the data as 'chatHistory'.

I can then copy the raw JSON data and save as a file, but this is a raw single line of text, so Kate has a problem with handling it until you allow the larger line length to be loaded. I still need to establish a tidy save process, but while Kate was enabled to display JSON data it did not do so until I saved it as a .jq file at which point it added missing line feeds and produced a more formatted structure in the saved file. No need to call upon the jq program directly as Kate had already been set up to do that processing.

In Kate, Settings -> Configure Kate brings up the configuration window.
Open/Save has a tab for Modes and Filetypes which show just how each file extension are to be handled, but I'm not sure on the entry for JSON
The final section is Formatting and the second tab for Default Settings has a set of what looks like json settings including the enabling of jq in relation to processing JSON files and I presume this is what picked up the .jq extension save.

Just where any of this material is ACTUALLY stored in openSUSE on a KDE desktop is still not fully identified as yet. None of the files Mistral states as the location exist on my machine so I need to dig further, which should be easier now I know some of the text I am looking for.