{"version":"2.1.211","anchor":"auto-front-load-of-tab-context-for-navigate-without-tabid","canonical_anchor":"auto-front-load-of-tab-context-for-navigate-without-tabid","heading":"Auto Front-Load of Tab Context for Navigate Without tabId","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211\/e\/auto-front-load-of-tab-context-for-navigate-without-tabid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211","markdown":"### Auto Front-Load of Tab Context for Navigate Without tabId\n\n**What**\n\nWhen the `navigate` tool is called with a URL but no `tabId`, Claude in Chrome now automatically issues a `tabs_context_mcp` call in the background to acquire a tab, then injects the tab context into the result. The caller no longer needs to call `tabs_context_mcp` first for simple URL navigation.\n\n**Details**\n\n- A short timeout bounds the background lookup; if it exceeds the limit, the tool returns an error instructing the caller to retry or call `tabs_context_mcp` explicitly.\n- `url: \"back\"` and `url: \"forward\"` still require an explicit `tabId` (they have no meaningful default).\n- The tab context JSON (from the front-loaded lookup) is appended to the successful navigate result for reference.\n\n**Evidence**\n\nAuto tab lookup logic (search for `\"The hidden tabs_context_mcp lookup did not respond within\"`)"}