Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] /export command docs omit actual-conversation model behavior [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52622•Fetched 2026-04-24 06:02:12
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeekgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

/export [filename] command entry

Current Documentation

The commands reference currently says:

/export [filename] | Export the current conversation as plain text. With a filename, writes directly to that file. Without, opens a dialog to copy to clipboard or save to a file

Related session/model docs currently say:

"The resumed conversation starts with the same model and configuration as the original"

"You can see which model you're currently using in several ways:

  1. In status line (if configured)
  2. In /status, which also displays your account information."

No /export documentation currently explains whether exported text includes model information, or whether that value comes from the exported conversation versus the user's current default model.

What's Wrong or Missing?

Changelog v2.1.119 says:

Fixed /export showing the current default model instead of the model the conversation actually used

This reveals a user-visible /export behavior that the docs do not currently cover: exported conversations include model information, and the intended value is the model associated with the conversation being exported rather than whatever model is currently configured as the default. Without that explanation, users cannot tell whether an exported transcript is expected to preserve the original session model or reflect current settings.

Suggested Improvement

Expand the /export command description to document what export metadata is preserved. At minimum, clarify that the model shown in the exported conversation reflects the conversation being exported, not the user's current default model.

If the export writes a model line or metadata block near the top of the file, include a short example so users can see where that value appears.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/commands/export [filename] entry currently describes only plain-text export, not how exported model information is derived

Total scope: 1 page affected

Related documentation context:

Source: Changelog v2.1.119

Changelog entry: Fixed /export showing the current default model instead of the model the conversation actually used

extent analysis

TL;DR

Update the /export [filename] command documentation to clarify that the exported conversation includes model information reflecting the conversation being exported, not the user's current default model.

Guidance

  • Review the current documentation for the /export [filename] command and identify areas where model information and export metadata are not clearly explained.
  • Expand the command description to include details on what export metadata is preserved, specifically addressing how the model shown in the exported conversation is determined.
  • Consider adding a short example to illustrate where model information appears in the exported file, if applicable.
  • Verify the updated documentation against the changelog entry in v2.1.119 to ensure accuracy.

Example

No code snippet is necessary for this documentation update, but an example of the revised documentation could be:

/export [filename] | Export the current conversation as plain text, including model information associated with the conversation. With a filename, writes directly to that file. Without, opens a dialog to copy to clipboard or save to a file. The exported model information reflects the model used in the conversation, not the user's current default model.

Notes

The documentation update should focus on clarifying the behavior of the /export command regarding model information to avoid user confusion.

Recommendation

Apply workaround: Update the documentation to reflect the correct behavior of the /export command, as this will improve user understanding and reduce confusion about the feature's functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] /export command docs omit actual-conversation model behavior [1 comments, 2 participants]