Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE]: Add /export to save session history as Markdown

Open
#465 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, rust, typescript
Domain
cli

Research direction

Start with agent-sdk/src/bridge/history.ts to see how saved history is loaded and how the existing resume translation maps it, then check src/app/slash/executors.rs for how slash commands are dispatched. The export should reuse that mapping rather than add a second parser. Done means /export and /export ./session-notes.md write a Markdown file with messages, tool results and metadata, never overwrite existing files, add -2, -3 suffixes on default-name collisions, and report the destination or the error.

Written by the indexing model from the issue text.

Description

area: agent-sdk area: core good first issue help wanted type: feature
Problem Statement

Users need to save a conversation for later reading or sharing, including saved history no longer retained in the visible chat.

Proposed Solution
  • Add /export [path], reading SDK-visible persisted session history.
  • Write Markdown containing user messages, assistant responses, tool results/diffs and available session metadata.
  • Without a path, write export-<session-id>-<YYYYMMDDTHHMMSSZ>.md in the session directory, using the full session UUID and UTC export time. Resolve explicit relative paths there and support paths containing spaces.
  • Never overwrite an existing file. For a default-name collision, add -2, -3, etc. before .md; for an existing explicit destination, report an error. Make omissions/truncation explicit and report the written destination or failure.

Examples: /export and /export ./session-notes.md.

Example default filename: export-11d785e2-d277-406c-9f99-31d840a3705b-20261013T123045Z.md.

Start with agent-sdk/src/bridge/history.ts for saved-history loading and the existing resume translation, and src/app/slash/executors.rs for command dispatch. Reuse the history mapping rather than introducing a second transcript parser.

Alternatives Considered

Copying individual responses or terminal scrollback does not provide a complete saved-session export.

Checklist
  • I have searched existing issues and discussions to ensure this is not a duplicate.
Dominant language
Rust
Stars
261
Forks
57
Avg merge
10h 15m
Merged PRs (30d)
58

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from srothgan/claude-code-rust

All issues in srothgan/claude-code-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.