Export Menu with Fine-grained Detail Toggles [code diffs, tool calls, thinking tokens, code blocks]]

Feature request for product/service

Chat

Describe the request

A menu giving fine grained control of what and how to export:

Choose what to export: (radio)
- selected chat tab
- all open chat tabs
- all history since beginning of time

include: (checkboxes)
- code diffs
- tool calls
- code blocks
- thinking tokens
- edited files list
- stats:

  • token count
  • model type
  • timestamps

Detail and reasoning:

Is it possible to export the thinking token, tool calls and other specific chat data? this is really valuable information, key to store in my repo, so future me and new team members can trace the assumptions made during implementation. Additionally, constant model switching means sometimes using the wrong model, basing an important architecture decision a weaker model made. I want ot be able to look back at old tickets/bugs/arch decisions and know “who” made it, like an LLM blame.

The ability to export the entire chat history: exporting one by one after a long sprint is tedious. Even more so, I want a global documentation store I can search by keyword and exporting one by one is not feasible.

Can we have an option to toggle the diffs in the export? Imagine a long conversion that filled the entire context window, somewhere between 15-20k LOC. Now I want to start a new chat and resume as accurately as possible.

The auto summarization is not nearly detailed enough, just a paragraph or a small list is useless. I want to give ie the full conversation, the meat of what was done, what challenges/roadblocks we hit, key errors, how we solved it, and where to go next in my next chat. This conversation log is usually only 5 to 10% of the entire context window, ~ 1 to 1.5k tokens on a 200k context window chat

To do that, I need to export my maxxed out chat, scroll the whole file, manually, carefully read and think, select any code blocks, save as new file, name it properly, move it to the right folder, drag it in.. this takes a lot of time and energy, and kills flow.


Bottom line: all of this data is sitting locked up in my user directory app data store. Clearly it’s saved, bc I can open old chats, with all the detail there.

Many folks have written scripts and hacks to get this data out, but we can’t keep up with the fast changing db schemas, and we dont have access to past schemas.

please help us with this and adopt a local-first mindset like Obsidian.