neo MCP: `wait for="time"` silently clamps to 30 s — larger `value` / `timeout` are accepted and ignored
Author: gboz17Created Sep 17, 2026Updated Sep 17, 2026
What I did: wait for="time" value=75000 timeout=80000.
Expected: a 75 s wait, or a validation error naming the cap.
Actual: returned waited 30000ms. A caller pacing a long in-page loop under-waits and re-polls. Same class as #2670, on wait.
Suggested fix: lift the clamp for wait for="time" (no page work runs during it), or reject values over the cap with the cap in the message.
Environment: BrowserOS neo 0.49.5.0 · Chromium 148.0.7988.97 (arm64) · macOS · client = Claude over MCP.
Source: browseros-ai/BrowserOS