Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.305entry #15

Claude Code v2.1.305 ·

Google Drive connector can upload local files by reference instead of typed base64

Behind tengu_wobbly_dewdrop, Drive's create_file can take a file reference that Claude Code reads after approval; HIPAA orgs are denied

Group of 3 You'll notice Notable New Features
JSON All of v2.1.305
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MCPArea: what it touches
New FeaturesKind: in v2.1.305,
What probably matters to youSection of the release

What

The Google Drive connector's create_file tool used to need the file's content typed out as base64 (file data written as text). A new path lets Claude pass a reference of the form sha256:<hex>:<path>. After you approve the call, Claude Code reads the file and fills in base64Content itself.

  • The tool's instructions gain a "FILE REFERENCES" section telling Claude to use a reference.
  • Files are limited to 10 MB.
  • It is controlled by the server-controlled switch tengu_wobbly_dewdrop and the policy allow_drive_file_references.
  • It is refused for third-party providers, custom base URLs, HIPAA and diskless sessions.
  • The new policy key is labelled "File references for connectors" (HIPAA-R87) and is denied under hipaa, including when the policy answer is missing or fails.
  • MCP tools marked as accepting file references are handled separately when tools are cached.

Why

Large Drive uploads would no longer pass through Claude's output. HIPAA-scoped organizations have the feature denied by default.

See this entry in the whole of v2.1.305 →

Feedback