{"version":"2.1.317","anchor":"mcp-drive-download-telemetry","canonical_anchor":"mcp-drive-download-telemetry","heading":"Usage data now records how Google Drive downloads are handled","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-drive-download-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Usage data now records how Google Drive downloads are handled\n\nClaude Code now records whether a Drive download was kept in the conversation, saved as text, cut, or not read\n\n**What**\n\nTelemetry is usage data that Claude Code sends back about how it is being used. When a file is downloaded from Drive through an MCP connection (MCP is the standard Claude Code uses to talk to outside tools), Claude Code now records which of these happened to it:\n\n- It was kept in the conversation.\n\n- It was saved as text.\n\n- It was cut.\n\n- It was not read.\n\nThere is also a measure that tries to guess when content was probably retyped by hand.\n\n**Why**\n\nThis only collects data about how large Drive downloads are handled. It does not change what Claude Code does with them.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}