{"version":"2.1.287","anchor":"chrome-status-gains-at-startup-plugin-directory-telemetry-n","canonical_anchor":"chrome-status-gains-at-startup-plugin-directory-telemetry-n","heading":"Chrome status now says whether Claude in Chrome starts enabled","tier":"internal","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/chrome-status-gains-at-startup-plugin-directory-telemetry-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Chrome status now says whether Claude in Chrome starts enabled\n\nClaude Code's Chrome status now reports whether Claude in Chrome is enabled by default at startup\n\n**Unclear.** What the removed plugin types entry did is not known.\n\n**What**\n\nClaude Code can report the status of its Chrome connection to programs that host it. That status now has an optional `at_startup` field, filled in from whether Claude in Chrome is set to be enabled by default.\n\nTwo smaller changes ship alongside it:\n\n- Claude Code now has names for recording use of a plugin directory: opening its catalog, switching it, and toggling it.\n\n- An entry for plugin types was removed from an internal list.\n\n**Why**\n\nPrograms that host Claude Code read this status, so they may behave differently when the \"Enabled by default\" option for Claude in Chrome is changed.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}