[Feature Request] Persistent feedback preferences configuration for streamlined submissions

Resolved 💬 2 comments Opened Mar 21, 2026 by jordan-of Closed Apr 18, 2026

Bug Description
Feature Request: Feedback Preferences for Streamlined Submissions

From: Jordan Dea-Mattson
GitHub: @jordan-of (OrdinaryFolk), @jordandm (personal)
Email: jordan-of@users.noreply.github.com

Problem

Every /feedback submission starts from scratch. There's no way to set persistent preferences for information that should accompany every report. Users who file feedback regularly end up manually
including the same context each time — contact info, GitHub handles, plan type, consent preferences — or worse, forgetting to include it and filing inconsistent reports.

Requested Behavior

Add a feedback preferences configuration at ~/.claude/feedback-preferences.json (or a section in ~/.claude/settings.json) that is automatically included with every /feedback submission.

Suggested preference fields:

{
"feedback": {
"identity": {
"name": "Jordan Dea-Mattson",
"email": "jordan-of@users.noreply.github.com",
"github": ["jordan-of", "jordandm"],
"organization": "OrdinaryFolk",
"plan": "Claude Enterprise"
},
"consent": {
"contact_me": true,
"share_session_data": true,
"share_transcript_excerpt": true,
"include_system_info": true
},
"defaults": {
"include_claude_code_version": true,
"include_os_version": true,
"include_model": true,
"include_session_id": true,
"include_project_context": true,
"archive": "both"
}
}
}

How it would work:

  • On first /feedback use, prompt the user to set up preferences (one-time setup)
  • On subsequent uses, auto-attach the configured identity and context — no manual entry
  • Consent fields control what Anthropic can do with the submission (contact, share, etc.)
  • Defaults control what system info is automatically included
  • All preferences editable via /feedback preferences or by editing the JSON directly
  • Preferences are user-level (not per-project) since they represent the person, not the codebase

Why This Matters

  • Reduces friction — filing feedback should be fast, not a form-filling exercise
  • Consistency — every report has the same baseline context, making it easier for Anthropic to triage
  • Privacy control — explicit, persistent consent preferences instead of per-submission guesswork
  • Encourages reporting — the easier it is to file feedback, the more feedback Anthropic gets

Active users who file multiple reports per week feel this friction acutely. A one-time preference setup eliminates repetitive overhead on every subsequent submission.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.80
  • Feedback ID: ec067225-deea-42d3-baa5-4dc57b287d47

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/jordan_of/.local/share/claude/versions/2.1.80 (expected in multi-process scenarios)\n    at YST (/$bunfs/root/src/entrypoints/cli.js:2903:2174)\n    at fBq (/$bunfs/root/src/entrypoints/cli.js:2903:1318)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T06:22:33.390Z"},{"error":"MaxFileReadTokenExceededError: File content (10820 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at z_9 (/$bunfs/root/src/entrypoints/cli.js:4268:23437)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T06:36:03.196Z"},{"error":"MaxFileReadTokenExceededError: File content (17524 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at z_9 (/$bunfs/root/src/entrypoints/cli.js:4268:23437)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T06:39:17.705Z"},{"error":"MaxFileReadTokenExceededError: File content (14803 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at z_9 (/$bunfs/root/src/entrypoints/cli.js:4268:23437)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T06:39:20.137Z"},{"error":"MaxFileReadTokenExceededError: File content (20579 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at z_9 (/$bunfs/root/src/entrypoints/cli.js:4268:23437)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T06:58:34.461Z"},{"error":…

Note: Content was truncated.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗