{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicedipjdlgqhxsienv37mstci7qvd6qfaaxioju2msg5c7yvem4ry",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlviauu5ja52"
  },
  "path": "/t/browserbase-connector-in-chatgpt-start-succeeds-but-navigate-fails-with-no-active-session/1381004#post_1",
  "publishedAt": "2026-05-15T13:05:41.000Z",
  "site": "https://community.openai.com",
  "textContent": "Title: Browserbase connector in ChatGPT: start() succeeds but navigate() fails with “No active session”\n\nBody: Hi everyone,\n\nI’m testing the Browserbase Public Web Reader connector in ChatGPT.\n\nThe connector appears in the tool list, and `start()` succeeds, but follow-up calls cannot find the active session.\n\nRepro:\n\n  1. Call `start()`\n\n  2. It returns `success: true` with a `sessionId`\n\n  3. Call `navigate(\"https://example.com\")`\n\n  4. It fails with `No active session`\n\n  5. Calling `start({ sessionId })` again also returns success, but `navigate()` still fails with `No active session`\n\n\n\n\nExpected: `navigate()` should use the session created by `start()`, or the tool should allow `sessionId` to be passed explicitly.\n\nActual: The connector appears to lose active session state between tool calls.\n\nComparison: The same Browserbase account/workflow works in Claude, and Browserbase sessions appear correctly in the Browserbase dashboard.\n\nQuestion: 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`?\n\nScreenshots available:\n\n  * Browserbase dashboard showing successful Claude sessions\n\n  * ChatGPT `start()` success with `sessionId`\n\n  * ChatGPT `navigate()` failure: `No active session`\n\n\n\n\nNote: I’m intentionally not sharing API keys, full CDP URLs, signing keys, cookies, or other credentials.",
  "title": "Browserbase connector in ChatGPT: start() succeeds but navigate() fails with “No active session”"
}