SendFeedback is absent in desktop app sessions, and the docs' exclusion list does not name them

Summary

The SendFeedback tool is never exposed in Claude Code desktop app sessions. It works normally in a terminal session on the same machine, under the same GitHub/Anthropic user, with the feature gate demonstrably enabled.

The documented exclusion list at tools-reference#sendfeedback-tool-behavior does not mention the desktop app, which is what made this look like a defect rather than a design decision.

What happens

In a desktop app session, SendFeedback is absent from the tool roster entirely. It is not deferred and not permission-blocked. Asking Claude to file feedback produces a conversational answer, never a queued draft.

In a terminal session, the same request works: Claude drafts, a review card appears above the prompt, and the draft lands on disk.

Expected

Either the tool is available in desktop sessions, or the docs name the desktop app in the "Sessions without Claude-drafted feedback" list.

That list currently names non-interactive -p runs, Agent SDK sessions, Claude Code on the web, Bedrock / Claude Platform on AWS / Vertex / Microsoft Foundry, sessions with the disabling env vars set, and ZDR organizations. A reader on the desktop app matches none of those descriptions.

If the desktop app is excluded because it runs on the Agent SDK, that is reasonable, but it is not discoverable from the docs. The current text reads as "you qualify," and the observed behavior is the opposite.

Reproduction

1. Open a Claude Code desktop app session.
2. Ask Claude to file feedback about anything.
3. No draft is queued. The tool is not in the roster.
4. Open a terminal session on the same machine, same account.
5. Make the same request. A draft is queued and a review card appears.

Environment

| | Desktop session | Terminal session |
|---|---|---|
| Claude Code version | 2.1.246 | 2.1.247 |
| Binary | C:\Users\<user>\.claude-desktop-4\claude-code\2.1.246\claude.exe | C:\Users\<user>\.local\bin\claude |
| CLAUDE_CODE_ENTRYPOINT | claude-desktop | unset |
| Config dir | .claude-account-4 | .claude-account-2 |
| feedbackDrafts | notify | notify |
| SendFeedback present | no | yes |

OS: Windows 11 Pro 26200.

Things already ruled out

• Version floor. Both builds are past the documented 2.1.238 minimum.
• Setting. feedbackDrafts is explicitly notify in all six config dirs on this machine, not merely defaulted.
• Disabling env vars. None of CLAUDE_CODE_SEND_FEEDBACK, DISABLE_FEEDBACK_COMMAND, or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC are set in either session.
• Managed policy. No managed settings directory exists on this machine.
• The feature gate. The terminal session drafted and sent successfully, so the account-level gate is on.

Caveat on the evidence

The two sessions differ by one patch version, 2.1.246 against 2.1.247. I cannot fully separate "desktop sessions are excluded" from "2.1.246 lacks something 2.1.247 has" from the outside. The docs' Agent SDK exclusion makes the session-type explanation the more likely one, but the version difference is real and worth naming.

Why it is worth fixing either way

Desktop sessions are exactly where a user is most likely to hit a frustrating moment and least likely to switch terminals to report it. Silently having no reporting path there loses the reports you most want. If the exclusion is intentional, one line in the docs would save the diagnosis.