Browserbase connector in ChatGPT: start() succeeds but navigate() fails with “No active session”

Title: Browserbase connector in ChatGPT: start() succeeds but navigate() fails with “No active session”

Body: Hi everyone,

I’m testing the Browserbase Public Web Reader connector in ChatGPT.

The connector appears in the tool list, and start() succeeds, but follow-up calls cannot find the active session.

Repro:

1. Call start()

2. It returns success: true with a sessionId

3. Call navigate("https://example.com")

4. It fails with No active session

5. Calling start({ sessionId }) again also returns success, but navigate() still fails with No active session

Expected: navigate() should use the session created by start(), or the tool should allow sessionId to be passed explicitly.

Actual: The connector appears to lose active session state between tool calls.

Comparison: The same Browserbase account/workflow works in Claude, and Browserbase sessions appear correctly in the Browserbase dashboard.

Question: Is ChatGPT’s MCP/app runtime failing to persist tool session state, or does the Browserbase connector need to expose sessionId on navigate, act, observe, and extract?

Screenshots available:

• Browserbase dashboard showing successful Claude sessions

• ChatGPT start() success with sessionId

• ChatGPT navigate() failure: No active session

Note: I’m intentionally not sharing API keys, full CDP URLs, signing keys, cookies, or other credentials.