[FEATURE] /export is braindead

Resolved 💬 3 comments Opened Jan 28, 2026 by 1MikeMakuch Closed Feb 1, 2026

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

I like to use the /export save to a file frequently so that I can easily remember the most recent commands for whenever claude locks up and has to be killed (like when reading files with very long lines for one example). Problem is the /export save to a file doesn't let you set the directory to write to. I'd like to have all the exports in a certain dir. Instead the export writes the file to what ever dir claude happens to be in at that moment. Very inconvenient.

I'd like to be able to set the dir for exports, the file name format to include a timestamp including date and time so that it doesn't overwrite the previous export.

Proposed Solution

Modify the export function to so we can set the dir for exports, the file name format to include a timestamp including date and time so that it doesn't overwrite the previous export.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗