Repository navigation
Add tab awareness without the debugger banner (AGE-584) - #257
Merged
Merged
Conversation
listTabs, readTab, navigateTab, softClick, and softType use chrome.tabs and chrome.scripting. They do not attach the debugger or change focus. chromeTabId stays separate from the DevTools-connected tabId. Background navigation stays in the visible window and is gated like other input. Soft click and type report worked or needs a real gesture. Co-authored-by: werbel.ted <werbel.ted@gmail.com>
Opening a tab had no live page, so the restricted-page check on navigate did not run. chrome:// and the Web Store are refused there too. An http(s) PDF can still load. Co-authored-by: werbel.ted <werbel.ted@gmail.com>
The submitted page can still be loading when listTabs runs, so the title is the URL. Poll until the title is present. Co-authored-by: werbel.ted <werbel.ted@gmail.com>
cursor
Bot
force-pushed
the
cursor/age-584-tab-awareness-ae3c
branch
from
October 27, 2026 04:36
2861741 to
cfe0346
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tab awareness MVP for AGE-584, on current main. One PR rather than a stack: the five slices share the service worker, connector, and capability gates, and each slice is called out below so it can be reviewed in order.
Chrome debugger banner is never hidden. No silent-debugger flag, policy, or bypass.
listTabs,readTab,navigateTab,softClick, andsoftTypedo not callchrome.debugger. They do not calltabs.update({active:true})orwindows.update({focused:true}).chromeTabId(fromchrome.tabs) and DevTools-connectedtabIdstay separate in the tool descriptions, even when Chrome happens to use the same integer. Existing DevTools tools, includingnavigateBrowser, are unchanged.1. Contracts and ID model
MCP schemas and descriptions live in
browser-tools-mcp/src/tabs/contract.ts.listBrowserTabs/navigateBrowserare labeled as DevTools-connected. The new tools saychromeTabIdis not atabId.Coverage sentence, exact:
2. listTabs
Service worker → connector → MCP → CLI (
browser-tools listTabs) on the same invoke path as the other tools. Metadata only: windows and tabs the browser returns. Incognito is skipped. The exclude list is applied in the extension and again in the connector. Discarded tabs are reported asleep and are not reloaded.3. navigateTab
Background only, gated like input: popup switch plus
--allow-input/ CLI--allow-actions. Creates a tab withactive: falseor updates an existing one with{url, active: false}. Limited to the visible normal window until Arc Spaces are measured (AGE-618). Reports final URL, whether a tab was created, and tabs that opened alongside it.4. readTab
chrome.scripting.executeScriptin the isolated world. No debugger. Discarded → asleep, no reload. Frozen → skip.chrome://, the web store, and pdf are refused. Loopback is already in the manifest (permissions.containsdoes not report those). Other origins need the popup button "Allow reading pages you have open" (<all_urls>), which is a user click. Secrets are scrubbed in the page and again in the connector.5. softClick / softType
Main world so the native value setter and
execCommand('insertText')reach React-style inputs. Outcome isworkedorneeds a real gesture(file picker, clipboard, popup, fullscreen, untrusted submit/link/checkbox, Google Docs/canvas, anti-bot, covered or missing box).trustedis always false. Submit usesform.requestSubmit(), notform.submit().Tests
invokeTool(CLI parity).chrome.debugger.sendCommandfails on both the original tab and the new tab (this extension never attached). Playwright's own CDP session marks targets attached; that is notchrome.debugger.attach.On this branch:
npm run typecheck, unit+integration 583 passed, e2e 73 passed. No npm publish, tag, or release.Arc validation still open (Ted, Mac)
AGE-618 cells are still unmeasured. Until a probe shows
tabs.update({active:false})/tabs.create({active:false})in another Space does not switch Space, background navigate stays in the visible window.listTabsmust not be treated as every open tab: other Spaces, Little Arc, pinned favorites, split-view partners, and slept tabs may be missing. Incognito is skipped. Host access beyond localhost needs the user to click the popup grant. Softworkedmeans untrusted events were delivered, not a trusted user gesture. No background screenshots. Real-input debugger fallback (AGE-614) and agent browser (AGE-615) are out of scope. Security review of the soft-input and navigate gates is still an AGE-584 done-when item.