SDK feedback can be saved as a local bundle, and hosts learn the feedback mode up front

What

The SDK lets other programs, such as the IDE and desktop apps, run Claude Code and offer its /feedback report. Two internal additions change how that works.

• feedback_mode: a new field on the SDK's start-up message tells the host how this session handles a submit_feedback report: "post" sends it to Anthropic, "bundle" writes a redacted zip on this machine, "share" is the internal-build upload, and "disabled" means it is refused. It is left out when the only refusal is organisation policy.
• "bundle" is chosen when the API provider is not Anthropic's own (cause "provider") or when there are no Anthropic credentials ("no Anthropic credentials"). The description now separates "disabled" (organisation policy, an environment kill switch) from "cannot be sent".
• save_locally: a new option on the submit_feedback request. The report is written to a redacted zip on this machine and nothing is sent. The response carries bundle_path, with feedback_id set to the bundle id, or failure_reason: "bundle_write_failed" if the write fails.
• save_locally still applies if the mode has since become "post" or "share", for example after signing in mid-session, but "disabled" still refuses it. It is ignored when a draft_id is given.
• A report without a draft, submitted before any turn has happened, now returns unavailable_reason "no turn received yet".
• Both the control-request path and the bridge path use the new local writer.

Why

Apps built on the SDK can warn users before they write feedback whether it will be sent, saved locally or refused, and can offer a local-only report that is never uploaded. People using Claude through Bedrock, Vertex or a gateway get a way to produce a report in these apps.