{"version":"2.1.283","anchor":"auto-mode-decision-telemetry-records-chrome-pointer-press-an","canonical_anchor":"auto-mode-decision-telemetry-records-chrome-pointer-press-an","heading":"Auto mode usage data records more about Chrome clicks","tier":"internal","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/auto-mode-decision-telemetry-records-chrome-pointer-press-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Auto mode usage data records more about Chrome clicks\n\nUsage data from auto mode decisions now notes whether a Chrome action was a pointer press and whether a click was routed\n\n**Unclear.** It is not clear whether auto mode's actual decisions changed or only what it records.\n\n**What**\n\nAuto mode is a permission mode in which Claude Code decides for itself whether to allow an action. Each decision sends a record to Anthropic's usage data. When Claude Code is controlling the Chrome browser, that record now carries two more details:\n\n- Whether the action was a pointer press\n\n- Whether a click was routed\n\nThe pointer-press detail is also sent on the quicker decision paths used when file edits are auto-approved and when a request is forwarded from the desktop app. It is filled in only for Chrome actions.\n\n**Why**\n\nThis suggests auto mode now handles pointer presses and routed clicks in Chrome as separate cases.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}