[DOCS] `/feedback` docs do not explain that current-session reports include pre-compaction conversation

Open 💬 1 comment Opened May 23, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/data-usage

Section/Topic

Feedback using the /feedback command

Current Documentation

The docs currently say:

When you run the /feedback command, a copy of your conversation history including code is sent to Anthropic. Before submitting, you choose how much history to include: the current session only, which is the default, or also other sessions from the same project over the last 24 hours or 7 days. The data is encrypted in transit via TLS. Optionally, a GitHub issue is created in the public repository. To opt out, set the DISABLE_FEEDBACK_COMMAND environment variable to 1.

There is no note here explaining what happens when the current session has already gone through /compact or automatic context compaction.

What's Wrong or Missing?

Changelog v2.1.149 says:

Improved /feedback reports to include the conversation that happened before context compaction, making issues from earlier in long sessions easier to triage

The current /feedback docs explain session-selection options, but they do not tell users that the default “current session only” report also includes conversation from earlier in the same session before /compact or auto-compaction.

That missing detail matters in long sessions because other docs explain that compaction summarizes earlier conversation. Without an explicit /feedback note, users can reasonably assume a bug report from the current session only will include just the post-compaction summary rather than the earlier turns that led to the problem.

Suggested Improvement

Add one explicit sentence to the /feedback docs wherever report scope is described.

Before:

Before submitting, you choose how much history to include: the current session only, which is the default, or also other sessions from the same project over the last 24 hours or 7 days.

After:

Before submitting, you choose how much history to include: the current session only, which is the default, or also other sessions from the same project over the last 24 hours or 7 days. Current-session reports also include conversation that happened earlier in the same session before /compact or automatic context compaction, so long-session issues can still be investigated.

It would also help to mirror that note on the command reference and error-reporting pages that currently describe /feedback more briefly.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/data-usage | 102 | Defines /feedback history scope but omits pre-compaction behavior |
| https://code.claude.com/docs/en/commands | 29, 68 | /feedback is described only as reporting a bug or sharing conversation |
| https://code.claude.com/docs/en/errors | 644, 656 | Says /feedback includes the transcript, but not that pre-compaction turns are preserved |

Total scope: 3 pages affected

Related compaction behavior is already documented on the context-window pages, so this appears to be a missing /feedback cross-reference and scope note rather than a missing compaction guide.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗