stagehand 4.3.0a0.dev1628__tar.gz → 4.3.1a0.dev1654__tar.gz

{stagehand-4.3.0a0.dev1628 → stagehand-4.3.1a0.dev1654}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stagehand
-Version: 4.3.0a0.dev1628
+Version: 4.3.1a0.dev1654
 Summary: Browserbase's SDK for building browser agents
 Keywords: ai,agent,ai-agent,browser,browser-agent,browser-automation,computer-use,headless,playwright,cdp,llm,automation,web-scraping,testing
 Author: Browserbase
@@ -142,13 +142,8 @@ See [`examples`](examples) for action, extraction, observation, and custom LLM u
 
 For hosted browsers, import `browserbase` from `stagehand` and use
 `browserbase.launch(api_key=...)` or `browserbase.connect(api_key=..., session_id=...)` instead of
-`local_browser`. A launched session is released when you `close()` the browser handle, except with
-`keep_alive=True`: that handle's `close()` only disconnects, and the session keeps running until it
-is released out of band (Browserbase dashboard or API) or reaches its configured timeout. The
-Stagehand extension that `launch()` uploaded for that session is retained on the account for the
-same reason, so a `keep_alive=True` workflow that launches repeatedly accumulates extensions until
-they are deleted out of band. Sessions reached through `browserbase.connect()` are never released by
-`close()` — whoever created the session owns it.
+`local_browser`. Calling `close()` on the browser handle releases the Browserbase session. To keep
+a `keep_alive=True` session for later, call `stagehand.close()` without `browser.close()`.
 
 The same `browserbase` facade exposes Browserbase Search and Fetch without launching a browser:
 

{stagehand-4.3.0a0.dev1628 → stagehand-4.3.1a0.dev1654}/README.md

@@ -110,13 +110,8 @@ See [`examples`](examples) for action, extraction, observation, and custom LLM u
 
 For hosted browsers, import `browserbase` from `stagehand` and use
 `browserbase.launch(api_key=...)` or `browserbase.connect(api_key=..., session_id=...)` instead of
-`local_browser`. A launched session is released when you `close()` the browser handle, except with
-`keep_alive=True`: that handle's `close()` only disconnects, and the session keeps running until it
-is released out of band (Browserbase dashboard or API) or reaches its configured timeout. The
-Stagehand extension that `launch()` uploaded for that session is retained on the account for the
-same reason, so a `keep_alive=True` workflow that launches repeatedly accumulates extensions until
-they are deleted out of band. Sessions reached through `browserbase.connect()` are never released by
-`close()` — whoever created the session owns it.
+`local_browser`. Calling `close()` on the browser handle releases the Browserbase session. To keep
+a `keep_alive=True` session for later, call `stagehand.close()` without `browser.close()`.
 
 The same `browserbase` facade exposes Browserbase Search and Fetch without launching a browser:
 

{stagehand-4.3.0a0.dev1628 → stagehand-4.3.1a0.dev1654}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "stagehand"
-version = "4.3.0a0.dev1628"
+version = "4.3.1a0.dev1654"
 description = "Browserbase's SDK for building browser agents"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -85,7 +85,7 @@ strict = true
 
 [dependency-groups]
 dev = [
-  "datamodel-code-generator==0.68.1",
+  "datamodel-code-generator==0.81.0",
   "openai>=2,<3",
   "pytest==9.0.3",
   "pytest-asyncio==1.3.0",

{stagehand-4.3.0a0.dev1628 → stagehand-4.3.1a0.dev1654}/src/stagehand/_extension/manifest.json

@@ -31,5 +31,5 @@
     }
   ],
   "options_page": "wake-service-worker.html",
-  "version": "1.2.0"
+  "version": "1.2.1"
 }