[DOCS] `/feedback` docs omit recent-session attachment options for cross-session issues

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

/feedback command entry and related guidance about what session data the command can attach

Current Documentation

The docs currently say:

When something is wrong. /rewind rolls code and conversation back to a checkpoint. /doctor and /debug diagnose install and runtime issues, and /feedback reports a bug with session context attached.

| /feedback [report] | Submit feedback about Claude Code. Alias: /bug |

When users run the /feedback command, a copy of their full conversation history including code is sent to Anthropic. The data is encrypted in transit via TLS. Optionally, a GitHub issue is created in the public repository.

Run /feedback inside Claude Code to send the transcript and a description to Anthropic. The command also offers to open a prefilled GitHub issue.

What's Wrong or Missing?

The v2.1.141 release adds /feedback support for issues that span more than the current session by letting users include recent sessions from the last 24 hours or 7 days.

The current docs do not explain that behavior anywhere. They only describe /feedback in terms of the current session's context, transcript, or conversation history.

That leaves two gaps:

A. Missing feature guidance

Users are not told that /feedback can include recent sessions when a problem spans multiple sessions, or that the available ranges are the last 24 hours and last 7 days.

B. Missing data-sharing detail

The data-usage and error-reporting docs do not clarify that /feedback may now offer multi-session transcript attachment, so users cannot tell from the docs what extra session history may be shared when they choose that option.

Suggested Improvement

Update the /feedback documentation to describe the multi-session flow introduced in v2.1.141.

Minimum fix:

1. In the /feedback command reference, explain that Claude Code can offer recent-session attachment when the issue spans more than the current session.
2. List the available scopes: current session only, recent sessions from the last 24 hours, and recent sessions from the last 7 days.
3. In the data-usage and error-reporting pages, clarify what transcript/session data is attached for each choice so the privacy implications are explicit.

Suggested wording for the command docs:

If the issue spans more than the current session, /feedback can also include recent sessions. Claude Code may offer attachments from the last 24 hours or the last 7 days so you can report regressions that reproduce across resumed or separate sessions.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/commands | 29, 68 | /feedback is documented only as bug reporting with session context attached |
| https://code.claude.com/docs/en/data-usage | 24, 102 | Describes /feedback transcript upload, but not recent-session attachment options |
| https://code.claude.com/docs/en/errors | 587, 599 | Error-reporting guidance mentions sending the transcript, but not multi-session reporting |

Total scope: 3 pages affected

Reported against changelog version v2.1.141.