anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Add a config option to set a default directory for exported session transcripts #7395

New Issue
Open
opened 2026-02-16 18:07:03 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:07:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @KelvinJRosado on GitHub (Jan 23, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Right now the session transcript default to being exported to the cwd, with the path being set as follows:

            const exportDir = process.cwd()
            const filename = options.filename.trim()
            const filepath = path.join(exportDir, filename)

However, it would be good to allow a base directory for exported transcripts. This can allow for a global transcript location, or for a project-level subfolder. This gives additional flexibility for users as the current behavior requires that the transcripts go to a specific base directory.

My idea for this feature is that the exportDir would stay as-is for default behavior, but if the transcriptExportDir option is set then that value would be used instead.

Originally created by @KelvinJRosado on GitHub (Jan 23, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Right now the session transcript default to being exported to the `cwd`, with the path being set as follows: ``` const exportDir = process.cwd() const filename = options.filename.trim() const filepath = path.join(exportDir, filename) ``` However, it would be good to allow a base directory for exported transcripts. This can allow for a global transcript location, or for a project-level subfolder. This gives additional flexibility for users as the current behavior requires that the transcripts go to a specific base directory. My idea for this feature is that the exportDir would stay as-is for default behavior, but if the `transcriptExportDir` option is set then that value would be used instead.
yindo added the discussion label 2026-02-16 18:07:03 -05:00
yindo commented 2026-02-16 18:07:03 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 23, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10159: [BUG] [FEATURE] /export command only exports visible viewport content, not full session history after compaction - directly requests ability to export transcripts to a specified directory
  • #9387: [FEATURE]: opencode session export to markdown or json - proposes CLI command with output path flag (-o, --output)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 23, 2026): This issue might be a duplicate of existing issues. Please check: - #10159: [BUG] [FEATURE] /export command only exports visible viewport content, not full session history after compaction - directly requests ability to export transcripts to a specified directory - #9387: [FEATURE]: `opencode session export` to markdown or json - proposes CLI command with output path flag (`-o, --output`) Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7395
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?