Create a Browserbase Context and reuse it across sessions to persist cookies, localStorage and login state

Documented steps

1. Create the context: POST https://api.browserbase.com/v1/contexts with headers X-BB-API-Key and Content-Type: application/json. Reference: https://docs.browserbase.com/reference/api/create-a-context
2. Include projectId in the body optionally; if omitted the project is inferred from the API key.
3. On HTTP 201 store the returned id - that is the Context ID you reuse. The response also returns uploadUrl, publicKey, cipherAlgorithm (AES-256-CBC) and initializationVectorSize, which are only needed if you upload a custom user-data directory.
4. SDK equivalent (Node): const context = await bb.contexts.create({ projectId }); use context.id.
5. Attach the context to a session by setting browserSettings.context.id to the Context ID in the POST /v1/sessions body.
6. Set browserSettings.context.persist: true to write changes made during the session (new cookies, localStorage writes) back to the Context. It defaults to false, which gives read-only reuse.
7. Run the login or state-building flow in that first session, then end it. Contexts capture cookies, localStorage, IndexedDB, Session Storage, Service Workers and Web Data such as form autofill.
8. Wait a few seconds after the session closes before starting the next one, so the persisted data finishes synchronizing.
9. Start subsequent sessions with the same browserSettings.context.id to resume the authenticated state without logging in again. Reference: https://docs.browserbase.com/platform/browser/core-features/contexts
10. Manage lifecycle with the companion context endpoints under /v1/contexts/{id} for retrieve, update and delete.