[chrome-devtools-axi / MCP] wait 60000 fails with MCP error -32001: Request timed out (wait 20000 works)

## Observed symptom wait 60000 fails with MCP error -32001: Request timed out `wait 60000` fails with `MCP error -32001: Request timed out` after about a minute, even though the page is fine. Observed on chrome-devtools-axi 0.1.35, macOS 15.6.1, isolated named session. `CHROME_DEVTOOLS_AXI_SESSION=<name> chrome-devtools-axi wait 60000` returned the timeout after roughly 60s. A fresh `snapshot` worked right after, and four successive `wait 20000` calls completed normally; no browser state was lost. So long waits hit a request deadline somewhere between the CLI, the bridge and chrome-devtools-mcp. Expected: either `wait` honours its argument (e.g. by polling in shorter MCP calls), or its help states the effective ceiling and rejects longer values with that message. ## Literal error text ``` MCP error -32001: Request timed out ``` ## Version info 0.1.35, 15.6.1 ## Environment GitHub issue kunchenguid/chrome-devtools-axi #157; state=OPEN ## Trigger / context `wait 60000` fails with `MCP error -32001: Request timed out` after about a minute, even though the page is fine. Observed on chrome-devtools-axi 0.1.35, macOS 15.6.1, isolated named session. `CHROME_DEVTOOLS_AXI_SESSION=<name> chrome-devtools-axi wait 60000` returned the timeout after roughly 60s. A fresh `snapshot` worked right after, and four successive `wait 20000` calls completed normally; no browser state was lost. So long waits hit a request deadline somewhere between the CLI, the bridge and chrome-devtools-mcp. Expected: either `wait` honours its argument (e.g. by polling in shorter MCP calls), or its help states the effective ceiling and rejects longer values with that message. ## Source evidence - https://github.com/kunchenguid/chrome-devtools-axi/issues/157 (2026-09-30T17:39:18Z) — GitHub issue; novelty audit MISSED_NEW ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:33:42Z - scout_id: Ca0a03cebc7 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.