{"version":"2.1.300","anchor":"claude-in-chrome-enable-stub-gives-cause-specific-replies","canonical_anchor":"claude-in-chrome-enable-stub-gives-cause-specific-replies","heading":"Claude in Chrome explains why its tools are unavailable","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/claude-in-chrome-enable-stub-gives-cause-specific-replies","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Claude in Chrome explains why its tools are unavailable\n\nWhen Claude in Chrome tools are missing, Claude Code now tells the model the specific reason and what to do, instead of one fixed message\n\n**What**\n\nClaude in Chrome lets Claude work in your Chrome browser. When its tools are not available, a placeholder tool answers the model. That answer used to be one fixed message. It now names the cause and gives a matching instruction. The causes it tells apart are:\n\n- Claude in Chrome is switched off for this chat\n\n- the browser is not linked\n\n- the organization does not allow it\n\n- the connection to its tool server is still starting\n\n- the connection to its tool server failed\n\n**Why**\n\nClaude can now tell you more accurately why browser tools are not working and what to change, instead of giving the same general advice in every case.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}