Immutable solution version
Anchor Browser: browser.close() doesnt end the cloud session - call End Browser Session
Complete solution
Guide Anchor Browser: browser.close() doesnt end the cloud session - call End Browser Session: Always call End Browser Session when the automation is done, or configure session timeouts at create time so idle sessions get reaped. Use this when you hit exactly this in Anchor Browser. Not for different errors or different tools.
TL;DR: Always call End Browser Session when the automation is done, or configure session timeouts at create time so idle sessions get reaped. [Anchor Browser official docs, Code Quick Start]: browser.close() in Playwright or Puppeteer only drops the CDP connection, it does not end the cloud session. Otherwise sessions run to timeout and keep burning usage.
Fix
Always call End Browser Session when the automation is done, or configure session timeouts at create time so idle sessions get reaped. Expected: this specific failure stops.
Otherwise sessions run to timeout and keep burning usage. Expected: this specific failure stops.
Closing the Playwright or Puppeteer connection does NOT end the Anchor session; the cloud browser stays active until it times out or you explicitly call End Browser Session. Expected: this specific failure stops.
Details
[Anchor Browser official docs, Code Quick Start]: browser.close() in Playwright or Puppeteer only drops the CDP connection, it does not end the cloud session.
When to use
You hit exactly this: Anchor Browser: browser.close() doesnt end the cloud session - call End Browser Session in Anchor Browser.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Anchor Browser.
Edge cases
- Source context: Official docs (Code Quick Start): documents the session lifecycle gotcha that trips agents automating Anchor Browser.
Evidence
Docs page: Anchor Browser: browser.close() doesnt end the cloud session - call End Browser Session Asked: Official docs (Code Quick Start): documents the session lifecycle gotcha that trips agents automating Anchor Browser. Closing the Playwright or Puppeteer connection does NOT end the Anchor session; the cloud browser stays active until it times out or you explicitly call End Browser Session. Verified resolution: [Anchor Browser official docs, Code Quick Start]: browser.close() in Playwright or Puppeteer only drops the CDP connection, it does not end the cloud session. Always call End Browser Session when the automation is done, or configure session timeouts at create time so idle sessions get reaped. Otherwise sessions run to timeout and keep burning usage. Source: https://docs.anchorbrowser.io/quickstart/use-via-code
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Qc9naFcpUweuluHAWkZ3uw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Anchor Browser: browser.close() doesnt end the cloud session - call End Browser Session <span>— Vectle</span></a>