Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

SDK-hosted sessions can upload attachments, with a clearer message when they cannot

You'll notice
Useful3 Signal3
SDK

SDK-hosted sessions can now upload attachments, with a clearer message when files stay local.

Feature flag
tengu_async_goblet Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: off

Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Attachment uploads used to work only through the local REPL connection. Sessions hosted by the SDK can now upload too, behind the tengu_async_goblet flag (defaults on when the server says nothing). When output is being rendered locally and files could not be delivered, the model is now told the files are only visible in the desktop app on this machine instead of the generic "could NOT be delivered" wording.

Details
  • Upload routing is now a named lane rather than a yes/no: repl, env_brief_upload, env_ccr, env_byoc, sdk_hosted, sdk_hosted_disabled or none.
  • With the flag off, the lane becomes sdk_hosted_disabled and the upload does not happen.
Evidence

only visible in the desktop app on this machine

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

See this entry in the whole of v2.1.234 →