v2 /export saves to /tmp/ instead of current working dir like v1 #53748

Activity

1. github-actions

   assigned

   nexxeln

   on Oct 7, 2026
2. opencode-agent commented on Oct 7, 2026

   

   opencode-agentBot

   on Oct 7, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report. I was able to reproduce this on v2.0.24 (Linux):

   1. Start opencode2 in a project directory and have a short conversation.
   2. Run /export, keep Markdown and choose the save option.
   3. The "Session exported" dialog shows a path like /tmp/session-<uuid>.md. Nothing is written to the working directory.

   With the default umask (0022), the exported file is created as -rw-r--r--, so other local users can read the transcript, as you pointed out. In v2 the save path comes from the system temp directory and no file mode is set. I've passed this on to the maintainers.
3. jgforbes commented on Oct 13, 2026

   

   jgforbes

   on Oct 13, 2026

   More actions

   Properly located session exports are quite important to have. Having to move from /tmp is considerable work flow breakage.
4. maatthias commented on Oct 20, 2026

   

   maatthias

   on Oct 20, 2026

   More actions

   I too prefer the v1 behavior of session transcript exporting to current working directory and 👍 this. Note that the above is not correct about where the opencode v2 TUI exports to. While the TUI reports /tmp/session-{uuid} this is just its sandboxed view. To get the export on disk:

   # get the opencode pid
   pgrep opencode
   
   ls -al /proc/{pid}/root/tmp/
5. Tarquinen

   closed this as completedin #62253on Nov 7, 2026