Reverse engineer anything with agents, from app behavior down to native binaries.
TypeScript agent-skillsai-agentsbinary-analysisclaude-codeclicodexcordisdecompilerdeveloper-toolsdshdsh-pluginghidrahopperllmmcpmodel-context-protocolreareverse-engineeringstatic-analysistouhou
fix(browser): bypass desktop keyrings in verification fixtures
morlutoc57e759ae6ee
diff --git a/docs/browser-observation.md b/docs/browser-observation.mdindex ca793ac5b..3cdac5aa1 100644--- a/docs/browser-observation.md+++ b/docs/browser-observation.md@@ -53,6 +53,12 @@ google-chrome \REA does not launch, own, or terminate this browser. Use a dedicated profile and stop it yourself when the investigation is complete. Do not expose the debugging port on a non-loopback interface.+On Linux, a reachable but locked desktop keyring can stall Chrome before its+first navigation. For a dedicated investigation profile, add+`--password-store=basic` to bypass that keyring. Empty or placeholder frame URLs+then describe an unloaded page; REA continues to require an allowed, committed+URL. See [the startup investigation](https://github.com/morluto/rea/issues/1384#issuecomment-6093781686).+## Request boundaryCDP connections enforce the shared 64 MiB limit per WebSocket message. A largerdiff --git a/docs/testing.md b/docs/testing.mdindex 3c05df096..3f91188e8 100644--- a/docs/testing.md+++ b/docs/testing.md@@ -391,6 +391,12 @@ regressions until a real fixture establishes equivalent coverage.`verify:browser` exercises source-map failure isolation and expanded-output limits through the compiled CLI and stdio MCP with real Chrome. It also submits five 2 MiB source-map annotations, checks retained script identities and explicit map omissions, and closes its owned fixture target. Replacement and document-reset behavior has separate producer-boundary coverage.+The raw Chrome fixture launchers use `--password-store=basic` so Linux startup+does not wait for an unlock prompt from a reachable but locked desktop keyring.+Such a stall leaves the initial page unloaded with empty or placeholder CDP URLs;+it does not establish permission to capture that page. See+[the keyring diagnosis](https://github.com/morluto/rea/issues/1384#issuecomment-6093781686).+`verify:browser` also captures a source-owned noise canvas as a real PNG above8 MiB through the CLI and stdio MCP, with complete byte/digest parity and real PNGdecoding. Its SDK client explicitly permits the larger inline JSON response;diff --git a/scripts/lib/browser-runtime-fixture-lifecycle.mjs b/scripts/lib/browser-runtime-fixture-lifecycle.mjsindex 2ab048cf2..24b88c793 100644--- a/scripts/lib/browser-runtime-fixture-lifecycle.mjs+++ b/scripts/lib/browser-runtime-fixture-lifecycle.mjs@@ -18,6 +18,7 @@ export async function startRuntimeFixtureBrowser(executable, origin) {command: executable,arguments: ["--headless=new",+ "--password-store=basic",...(process.env.REA_BROWSER_NO_SANDBOX === "true"? ["--no-sandbox"]: []),diff --git a/scripts/verify-real-browser.mjs b/scripts/verify-real-browser.mjsindex 4dd492854..a63024b49 100644--- a/scripts/verify-real-browser.mjs+++ b/scripts/verify-real-browser.mjs@@ -64,6 +64,7 @@ try {executable,["--headless=new",+ "--password-store=basic",...(process.env.REA_BROWSER_NO_SANDBOX === "true"? ["--no-sandbox"]: []),