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
parent 0c7534d9b2
commit 42560b56fc
1 changed files with 8 additions and 0 deletions
@@ -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