[FEATURE] /export command should generate unique filenames to prevent overwrites
Resolved 💬 2 comments Opened Dec 3, 2025 by ShaneDugas Closed Dec 4, 2025
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
Description:
The /export command currently generates filenames that may overwrite previous exports from the
same session or conversation topic.
Current Behavior:
/exportcreates files like2025-12-03-continue-with-plan.txt- Subsequent exports in the same session may reuse similar filenames
- Risk of accidentally overwriting previous exports
Proposed Solution
Desired Behavior:
- Each
/exportshould generate a unique filename - Options could include:
- Append timestamp:
2025-12-03T00-45-30-continue-with-plan.txt - Append sequence number that auto-increments:
...-plan-001.txt,...-plan-002.txt - Prompt user for filename confirmation before saving
- Check for existing file and auto-increment if collision detected
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
Use Case:
During long sessions with multiple export points, I want to preserve all exports without manually
managing filenames or risking data loss from overwrites.
Additional Context
Environment:
- Claude Code CLI version: [2.0.56]
- Platform: Linux
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗