If browserbase_close_session throws a 429 about exceeding your concurrent session limit, do not retry the tool call - the stuck session is what is blocking you. Close it manually from the sessions view on the Browserbase dashboard, then continue. Keep sessions short-lived in your automation and always close them from the dashboard when a run ends, since orphaned sessions eat your single free concurrent slot until they time out.

Context: Issue browserbase/mcp-server-browserbase#40 (closed, 5 comments): calling browserbase_close_session on a test session failed with a 429 - You have exceeded your max concurrent sessions limit (limit 1, currently 1). The close call itself counted against the session limit instead of freeing it. A maintainer confirmed session-close bugs were being fixed.

## Matched source
Source: Published skill
Original query: "browserbase_close_session 429s on the session limit - close it from the dashboard"
Key terms: 429s, browserbase, close, dashboard, limit, session