Problem
Qoder Desktop currently provides no practical way to export, copy, download, or manually update project memory using existing chat history.
I have a long-running project with important discussions, decisions, implementation details, and project context dating back to December 2025. I can still browse and read these conversations in Qoder Desktop, so the data clearly exists.
However, Qoder’s memory/search appears to only have access to conversations from approximately July 2026 onward. When I ask Qoder to retrieve information from older project conversations, it cannot find or access them.
There is also no option to:
- Export or download the complete chat history
- Copy an entire conversation easily
- Add selected conversations to project memory
- Rebuild or refresh project memory from historical chats
- Ask Qoder to generate a project memory/documentation file from all existing project chats
This is becoming a significant blocker because some of the project’s architecture decisions, previous implementation details, discussions, requirements, and reasoning are contained in those older conversations. Recreating that information manually would require going through months of work again.
Solution
Qoder Desktop should provide a way to import existing conversations into project memory and/or export the complete project chat history.
Ideally, there should be several options:
-
Add Chat to Project Memory
Allow users to select one or more conversations and add their contents to the project’s persistent memory. -
Rebuild / Refresh Project Memory
Provide an option such as:“Rebuild Project Memory from All Chats”
Qoder could scan all conversations associated with the project, extract important information, and generate/update files such as:
PROJECT_MEMORY.mdARCHITECTURE.mdDECISIONS.mdROADMAP.mdCHANGELOG.md
-
Export Chat History
Allow complete conversations, or all conversations within a project, to be downloaded as Markdown, TXT, JSON, or another machine-readable format. -
Copy Entire Conversation
Add a simple option to copy the full conversation instead of manually selecting individual messages. -
Manual Memory Import
Allow a user to provide exported chat data and tell Qoder:“Use these conversations to update this project’s memory.”
Most importantly, if historical conversations are still visible inside Qoder Desktop, Qoder’s agent should ideally be able to access and process those same conversations when explicitly requested by the user.
Use Case
This is particularly important for long-running software projects where Qoder has been used for several months.
For example, my project has conversations going back to December 2025 containing:
- Architecture decisions
- Feature requirements
- Previous bugs and fixes
- Database and API decisions
- Deployment discussions
- Technical compromises
- Roadmap decisions
- Implementation history
- Reasons behind certain design choices
I can manually browse these chats, but Qoder itself cannot retrieve that information when working on the project.
If I could export the conversations or ask Qoder to ingest them into a PROJECT_MEMORY.md file, I could restore a large amount of missing project context immediately.
This would also prevent users from having to repeatedly explain old decisions to the AI when the information already exists inside Qoder.
Priority
High - Blocking issue
This is currently blocking parts of my project work because older project context cannot be accessed by Qoder, despite the conversations still being visible in the application.
For long-running projects, reliable access to historical project knowledge is essential. Without it, the usefulness of persistent memory is significantly reduced.
Additional Info
In my case:
- Project conversations exist from approximately December 2025 onward
- I can manually browse and read the older conversations
- Qoder appears able to access/search memory only from around July 2026 onward
- Qoder cannot retrieve important information from the older conversations
- There is currently no obvious way to download/export the project chat history
- There is no way to tell Qoder to ingest selected historical chats into project memory
A feature similar to “Export Project Conversations”, “Add to Project Memory”, or “Rebuild Memory from Chat History” would solve a major part of this problem.
I would actually also emphasize the slightly strange part of the bug: the UI can display the December 2025 conversations, but the AI cannot access them. That makes this more than just a feature request—it may indicate that Qoder has two separate stores/indexes for chat history?? and agent memory, and the older data was never indexed into the newer memory system. Putting this out so that you can make distinction and help your engineering team identify the problem faster.
