Images sent from remote control could be inlined instead of passed as file paths, but that is off.
Inline image blocks for bridge attachments are built but gated on a flag falling back to false, so paths are still used.
tengu_bridge_inline_image_attachments Not enough to sayNothing 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.223: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.223. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Image attachments on bridge and remote-control messages can be downloaded and sent as content blocks instead of @path references, but the path is switched off in this build.
- attachment resolution now returns
{ prefix, imageBlocks }rather than a bare prefix string - gated on
tengu_bridge_inline_image_attachments, whose in-source fallback is false, so absent a server value attachments keep using path references - when inlining fails it falls back to the path reference and reports telemetry
bridge_attachment_inline_imagewith afallback_path_refvariant
tengu_bridge_inline_image_attachments
Strings lifted out of the shipped bundle, so the claim above can be checked against them.