Description
On Windows, a single webcmd read works reliably, but a burst of sequential reads (e.g. twitter timeline followed by one twitter profile per author) closes the Cloak browser context partway through. Every subsequent read then fails with browserContext.newPage: Target page, context or browser has been closed until webcmd daemon restart is run. The context does not auto-respawn.
Steps to Reproduce
webcmd daemon restartwebcmd browser default open https://x.com → works, returns a pagewebcmd twitter timeline --type for-you --limit 5 -f json → works, clean JSON- Run a script that calls
webcmd twitter profile <handle> for ~15 handles back to back (this is what the engagement scanner does after pulling the timeline)
- Context dies a few calls into the loop; every call from there errors:
Expected Behavior
The browser context survives sequential reads, or auto-reconnects when torn down, instead of erroring until a manual daemon restart.
webcmd Version
0.2.3
Node.js Version
Other
Operating System
Windows
Logs / Screenshots
Description
On Windows, a single webcmd read works reliably, but a burst of sequential reads (e.g.
twitter timelinefollowed by onetwitter profileper author) closes the Cloak browser context partway through. Every subsequent read then fails withbrowserContext.newPage: Target page, context or browser has been closeduntilwebcmd daemon restartis run. The context does not auto-respawn.Steps to Reproduce
webcmd daemon restartwebcmd browser default open https://x.com→ works, returns a pagewebcmd twitter timeline --type for-you --limit 5 -f json→ works, clean JSONwebcmd twitter profile <handle>for ~15 handles back to back (this is what the engagement scanner does after pulling the timeline)Expected Behavior
The browser context survives sequential reads, or auto-reconnects when torn down, instead of erroring until a manual
daemon restart.webcmd Version
0.2.3
Node.js Version
Other
Operating System
Windows
Logs / Screenshots