[Feature Request] Add "GREAT!" option to "How's Claude doing?" survey

Resolved 💬 1 comment Opened Feb 21, 2026 by prefrontalsys Closed Feb 21, 2026

Bug Description
you need to include a GREAT! option above Good in the "how's claude doing" survey pops.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.49
  • Feedback ID: e0b6e10e-d474-496c-91d7-e57eab74391d

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/sc/.local/share/claude/versions/2.1.49 (expected in multi-process scenarios)\n    at PFR (/$bunfs/root/claude:2599:2098)\n    at iyA (/$bunfs/root/claude:2599:1209)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-20T03:34:44.187Z"},{"error":"TelemetrySafeError: Error calling tool 'create_event': **ACTION REQUIRED: Google Authentication Needed for Google Calendar for 'sr4001@gmail.com'**\n\nTo proceed, the user must authorize this application for Google Calendar access using all required permissions.\n**LLM, please present this exact authorization URL to the user as a clickable hyperlink:**\nAuthorization URL: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=862589435692-c7tg90l2qstj40p7h8hdakksg9rkckj9.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8000%2Foauth2callback&scope=openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.events+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.readonly+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&state=4de530a25be79eac0c23f6948a404a6f&access_type=offline&prompt=consent\nMarkdown for hyperlink: [Click here to authorize Google Calendar access](https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=862589435692-c7tg90l2qstj40p7h8hdakksg9rkckj9.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8000%2Foauth2callback&scope=openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.events+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.readonly+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&state=4de530a25be79eac0c23f6948a404a6f&access_type=offline&prompt=consent)\n\n**LLM, after presenting the link, instruct the user as follows:**\n1. Click the link and complete the authorization in their browser.\n2. After successful authorization, **retry their original command**.\n\nThe application will use the new credentials. If 'sr4001@gmail.com' was provided, it must match the authenticated account.\n    at Jt_ (/$bunfs/root/claude:1906:17019)\n    at async zw7 (/$bunfs/root/claude:1906:14513)\n    at async call (/$bunfs/root/claude:1906:33616)\n    at async wb7 (/$bunfs/root/claude:2004:15028)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-20T03:35:56.442Z"},{"error":"TelemetrySafeError: Error calling tool 'create_event': **ACTION REQUIRED: Google Authentication Needed for Google Calendar for 'sr4001@gmail.com'**\n\nTo proceed, the user must authorize this application for Google Calendar access using all required permissions.\n**LLM, please present this exact authorization URL to the user as a clickable hyperlink:**\nAuthorization URL: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=862589435692-c7tg90l2qstj40p7h8hdakksg9rkckj9.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8000%2Foauth2callback&scope=openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.events+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.readonly+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&state=c040097c07ab3ee6b35c7b01fd158ffd&access_type=offline&prompt=consent\nMarkdown for hyperlink: [Click here to authorize Google Calendar access](https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=862589435692-c7tg90l2qstj40p7h8hdakksg9rkckj9.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8000%2Foauth2callback&scope=openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.events+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.readonly+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&state=c040097c07ab3ee6b35c7b01fd158ffd&access_type=offline&prompt=consent)\n\n**LLM, after presenting the link, instruct the user as follows:**\n1. Click the link and complete the authorization in their browser.\n2. After successful authorization, **retry their original command**.\n\nThe application will use the new credentials. If 'sr4001@gmail.com' was provided, it must match the authenticated account.\n    at Jt_ (/$bunfs/root/claude:1906:17019)\n    at async zw7 (/$bunfs/root/claude:1906:14513)\n    at async call (/$bunfs/root/claude:1906:33616)\n    at async wb7 (/$bunfs/root/claude:2004:15028)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-20T03:37:36.375Z"},{"error":"Error\n    at Fj (/$bunfs/root/claude:92:1144)\n    at <anonymous> (/$bunfs/root/claude:93:10097)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/…

Note: Content was truncated.

View original on GitHub ↗

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