Feedback is disabled for SDK entrypoints

Feedback and bug-report commands are hidden when Claude Code runs through the SDK.

You'll notice No documentation found Improvements

JSON All of v2.1.223

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

0Signal: worth watching, 1 to 5

FeedbackArea: what it touches

ImprovementsKind: in v2.1.223, 05 Aug 26

ImprovementsSection of the release

What

The feedback and bug-report commands are no longer offered when Claude Code is running as an SDK entrypoint.

Details

The feedback availability check now returns false for SDK entrypoints, in addition to the existing DISABLE_FEEDBACK_COMMAND and DISABLE_BUG_COMMAND env checks, the org policy check and the first-party check.
Gated on CLAUDE_CODE_ENTRYPOINT being one of the SDK values (sdk-ts, sdk-py, sdk-cli).

Evidence

sdk-py

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from

The build it came inv2.1.223

5 Aug 2026 · 201 entries, this one is #108.

Either side of it

Open the release →

Names in this entry

envDISABLE_FEEDBACK_COMMAND
Feedback and bug-report commands are hidden when Claude Code runs through the SDK.
envDISABLE_BUG_COMMAND
Temporary probes that checked whether old code paths still ran have been deleted; behaviour is unchanged.
envCLAUDE_CODE_ENTRYPOINT
Waiting for MCP servers before a headless run is tidied up and logs more detail.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.