claude-code - 💡(How to fix) Fix [FEATURE] Local storage in the ~/.claude dir of feedback sent via the /feedback command [1 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#56434Fetched 2026-05-06 06:28:09
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

There seems to be no local reference created when feedback is sent via /feedback. I assume the input may be captured in session data, however, that data is "up for grabs" & is not persistent if the user decides to delete it. It's also not very convenient for a user to have to search through the session data (which is organized for Anthropic to analyze or for Claude to use, not for a user to find feedback submissions).

Proposed Solution

It seems like it would be quite easy since the logging system is extremely robust for there to be a dir in ~/.claude where atomic uses of the /feedback command could be logged per use.

Alternative Solutions

I have not tried searching the session data but frankly I don't think I should have to work that hard to see my submissions. I think it's a miss that /feedback is not separately logged. A parallel example would be the Feedback Assistant.app on macOS - there is an email like UI for every submission & response.

Priority

Medium - Would be very helpful

Feature Category

File operations

Use Case Example

Example:

  1. invoke /feedback
  2. complete.
  3. A file or folder with a unique identifier / timestamp should be created automatically in a folder in ~/.claude where a user can see the submissions.

Additional Context

Thank you. This is an excellent issue template.

extent analysis

TL;DR

Implement a feature to log feedback submissions in a dedicated directory, such as ~/.claude/feedback, to provide users with easy access to their submissions.

Guidance

  • Consider creating a new directory ~/.claude/feedback to store feedback submissions, with each submission saved as a separate file with a unique identifier or timestamp.
  • Modify the /feedback command to write the input to a file in the designated directory, ensuring persistence and ease of access for users.
  • Review the existing logging system to determine if it can be leveraged or extended to support this new feature, given its robustness.
  • Evaluate the need for a user-friendly interface, similar to the Feedback Assistant.app on macOS, to display and manage feedback submissions.

Example

No code snippet is provided, as the issue does not contain specific technical details about the implementation.

Notes

The proposed solution assumes that the /feedback command is currently not logging submissions in a user-accessible manner, and that the session data is not a suitable solution for users to retrieve their feedback submissions.

Recommendation

Apply workaround: Implement a dedicated logging feature for feedback submissions, as it would provide a more user-friendly and persistent solution for accessing feedback history.

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…

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 [FEATURE] Local storage in the ~/.claude dir of feedback sent via the /feedback command [1 participants]