[FEATURE] Per-Conversation Export
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
User Story
As a Claude Pro user of the Mac desktop application, I want to export an individual thread/conversation so that I can retain a copy of the conversation to read again in the future.
Proposed Solution
Acceptance Criteria
- A UI affordance for exporting the current thread exists on the conversation-specific view.
- In less than two clicks, I can trigger an export of the current conversation.
- The exported file format is .pdf.
- I can confirm and/or change the exported file location. Note: default to user’s local “Downloads” directory.
- Upon The export file is downloaded to the specified local directory.
- The exported file is named: “YYYY-MM-DD-{conversation_title}.pdf”
- The exported file replicates the structure, order, and formatting of the conversation as it was displayed in the Claude desktop app; i.e. no significant reformatting occurs.
- My (user’s) prompts are included in the export.
- Claude’s responses are included in the export.
- All prompts and responses from the current conversation are included in the export.
- No prompts or responses from previous conversations are included in the export.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
I often want to do my own primary research post-conversation with Claude and/or save the conversation as an artifact that can be uploaded to a file repository (Google Drive, Sharepoint, Confluence) as supporting documentation that forms part of a larger strategic plan. This may be related to my own personal work (e.g. career progression) or my professional work (e.g. research related to numerical weather prediction models), in which case it will be shared with my colleagues who are working on the same product or research.
Additional Context
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗