chore(release): 0.27.0-fork.49 — embed stealth-status + multi-agent skill guidance

docs(skill): concurrent agents must use distinct --session (issue #6 )
Within a session, commands are pinned to the agent's opened tab (fork.47). But two agents on the same (default) session share one daemon + active tab and clobber each other. Document that each concurrent agent must use a unique --session — which gives it its own isolated tab group on the shared real Chrome.
2026-06-11 23:36:14 +09:00 · 2026-06-11 23:35:03 +09:00
4 changed files with 11 additions and 3 deletions
@@ -45,7 +45,7 @@ dependencies = [

 [[package]]
 name = "agent-browser-stealth"
-version = "0.27.0-fork.48"
+version = "0.27.0-fork.49"
 dependencies = [
 "aes-gcm",
 "async-trait",
@@ -1,6 +1,6 @@
 [package]
 name = "agent-browser-stealth"
-version = "0.27.0-fork.48"
+version = "0.27.0-fork.49"
 edition = "2021"
 description = "Fast browser automation CLI for AI agents"
 license = "Apache-2.0"
@@ -1,6 +1,6 @@
 {
  "name": "agent-browser-stealth",
-  "version": "0.27.0-fork.48",
+  "version": "0.27.0-fork.49",
  "description": "Browser automation CLI for AI agents — stealth fork with anti-detection",
  "type": "module",
  "packageManager": "pnpm@11.1.3",
@@ -451,6 +451,14 @@ agent-browser --session b fill @e1 "bob@test.com"
 `AGENT_BROWSER_SESSION=myapp` sets the default session for the current
 shell.

+**Concurrent agents MUST each use a distinct `--session <name>`.** Within one
+session, commands are pinned to the tab you opened (by target_id, so a foreign
+tab can't drift your `eval`/`screenshot`). But two agents sharing the *same*
+session (e.g. both on the bare default) share one daemon and one active tab —
+they will clobber each other's tab/eval context. A unique session per agent gives
+each its own isolated tab group (own cookies, tabs, pin) on the one real Chrome,
+with no cross-talk.
+
 ### Mock network requests

 ```bash
Author	SHA1	Message	Date
leeguooooo	31ef0d7e6a	chore(release): 0.27.0-fork.49 — embed stealth-status + multi-agent skill guidance Release binaries / Build macOS ARM64 (push) Has been cancelled Release binaries / Build macOS x64 (push) Has been cancelled Release binaries / Build Linux ARM64 (push) Has been cancelled Release binaries / Build Linux musl ARM64 (push) Has been cancelled Release binaries / Build Linux musl x64 (push) Has been cancelled Release binaries / Build Linux x64 (push) Has been cancelled Release binaries / Build Windows x64 (push) Has been cancelled Release binaries / Attach binaries to GitHub Release (push) Has been cancelled	2026-06-11 23:36:14 +09:00
leeguooooo	42560b56fc	docs(skill): concurrent agents must use distinct --session (issue #6 ) Within a session, commands are pinned to the agent's opened tab (fork.47). But two agents on the same (default) session share one daemon + active tab and clobber each other. Document that each concurrent agent must use a unique --session — which gives it its own isolated tab group on the shared real Chrome.	2026-06-11 23:35:03 +09:00