LLM agents cannot inspect the BrowserSkill debug console

[pleabargain]

Bug report: LLM agents cannot inspect the BrowserSkill debug console

Status: Open — local report; not filed upstream
Severity: Medium — blocks diagnosis of BrowserSkill failures
Component: BrowserSkill CLI, Chrome extension, and Agent Window access controls
Date observed: 2026-09-24
Environment: Windows; PowerShell 7.6.6; Chrome 154.0.0.0; BrowserSkill extension 0.3.1; protocol 1.3

Summary

An LLM agent cannot read BrowserSkill's own extension debug page to diagnose a BrowserSkill connection/session problem. The debug page is a chrome-extension:// URL, which the Agent Window sandbox refuses to observe. The existing user-owned debug tab cannot be borrowed when the confirmation UI is unavailable. The agent receives actionable-looking BrowserSkill errors but has no supported, safe way to inspect the diagnostics needed to explain or debug them.

This report requests a supported read-only diagnostics path. It does not request bypassing borrow confirmation or granting unrestricted access to extension pages.

Reproduction

1. Start the local daemon in PowerShell 7 and connect the BrowserSkill extension.
2. Start a session on the connected instance, for example:
   bsk session start --browser 904c36eb --json
3. List user tabs. The BrowserSkill debug page is visible at:
   chrome-extension://hhcmgoofomhgciiibhipgmgkgnoenaoi/debug.html?session=sgxt
4. Attempt to borrow that user-owned debug tab. Borrowing fails when no tab can display the confirmation request.
5. Create a task-owned Agent Window tab at the same extension URL and try to observe it. The Agent Window sandbox denies access because the URL uses the chrome-extension:// scheme.

Actual behavior

• Borrowing the existing debug tab failed with:

  the browser could not display a confirmation request
  No user tab can display the borrow confirmation
  

• Observing the task-owned debug tab failed with:

  operation denied by the Agent Window sandbox
  tool.observe cannot access ... because its URL is chrome-extension://...
  navigate the Agent Window to a web page first
  

• Consequently, the LLM cannot inspect the debug console or use its contents to troubleshoot BrowserSkill.

Expected behavior

Provide a documented, explicitly authorized, read-only way for an agent to retrieve the relevant BrowserSkill diagnostics, for example:

• a scoped CLI command that exports extension/daemon diagnostics for a session; or
• a narrowly scoped, read-only mechanism for observing the BrowserSkill debug page.

Any diagnostics export should redact credentials, cookies, tokens, and other secrets by default. Existing borrow confirmations and profile boundaries should remain intact.

Impact

When BrowserSkill itself fails, the agent cannot inspect the tool's own diagnostic interface. Troubleshooting becomes dependent on the user manually reading or copying the debug output, even when the user has explicitly requested the agent to inspect it. This increases recovery time and makes otherwise actionable BrowserSkill errors harder to diagnose.

Notes

• No attempt was made to disable borrow confirmation or bypass the Agent Window sandbox.
• The affected debug URL was observed in the user's Profile 15 browser; unrelated user tabs are intentionally omitted.
• A related attempt to navigate to chrome://version/ detached the DevTools session, but that is separate from the debug-console visibility issue.