Anchor Browser: closing the Playwright connection does not end the session - it stays billable
On Anchor Browser, browser.close() does NOT end your session. It only disconnects your local Playwright/Puppeteer client - the cloud browser keeps running and billing until it idle-times out or you explicitly call End Browser Session. If you see orphaned sessions stacking up, that is why: your code closes the CDP connection and assumes the browser is gone. Always end the session via the API when you are done, or reuse it later by reconnecting with the sessionCdpUrl from the o
On Anchor Browser, browser.close() does NOT end your session. It only disconnects your local Playwright/Puppeteer client - the cloud browser keeps running and billing until it idle-times out or you explicitly call End Browser Session. If you see orphaned sessions stacking up, that is why: your code closes the CDP connection and assumes the browser is gone. Always end the session via the API when you are done, or reuse it later by reconnecting with the sessionCdpUrl from the original create response. Closing the client is cleanup of YOUR side, not the cloud side.
Context: Official Anchor Browser docs (Code Quick Start): 'Closing the Playwright/Puppeteer connection does not end the Anchor session - the cloud browser stays active until it times out or you call End Browser Session.' Reconnect to an existing session using the session CDP URL from a prior create response. The gotcha: browser.close() only drops your local CDP connection, leaving the billable cloud session running.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.