Skip to content

v0.2.3

Choose a tag to compare

@hamzahamidi hamzahamidi released this 17 Aug 20:29
· 61 commits to main since this release
e9ea47b

Documentation correction: the browser-routing guidance now matches how the tools actually behave.

  • The Claude in Chrome bridge sees only tabs inside the extension's native Chrome tab group. Windows are irrelevant, and no bridge tool adopts a tab from outside the group. Re-open the URL in a group tab, or use Chrome's tab context menu when the original tab itself matters.
  • Read-only questions about what is open can be answered from Chrome's on-disk session file without remote debugging.
  • chrome-devtools is not sessionless by default: it launches a persistent profile whose cookies survive between runs. --isolated is the throwaway mode, and two servers launching against the default profile cannot run concurrently.
  • Remote debugging with --autoConnect is reserved for reaching tabs already open in the user's daily Chrome. A stale DevToolsActivePort file is not proof that debugging is enabled; check for a live listener instead.

Documentation only; no runtime behavior or MCP tools changed.