diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-09-09 22:54:22 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-09-09 23:14:15 -0400 |
| commit | 1ec29fc90b84517322bf5994245368f0e59eff61 (patch) | |
| tree | 5a8ba52d06a1c96d93540cfe1b34f699cd447c68 /docs | |
| parent | 017ff4b9a639f0b8b213e58a3f30613fc38edcc8 (diff) | |
Fix session cleanup and release 0.15.47
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ARCHITECTURE.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 4b2a561..2e21499 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -30,7 +30,10 @@ Each Pi session owns its own automation target: - If separate window cannot be created, pi-chrome falls back to dedicated tab. - Target survives `/reload` and Chrome service-worker restarts. - Ownership is tracked by id and mirrored to `chrome.storage.session`. -- Cleanup closes only calling session's own target, never user tabs/windows or other sessions' targets. +- Cleanup closes calling session's automation target and every tab it created through `tab.new`. +- Existing user tabs adopted into a session group are preserved, and ungrouped only if still in that group. +- Cleanup removes individual owned tabs, never whole windows. User/other-session tabs moved into a Pi window remain open; Chrome closes a window automatically when its final tab is removed. +- Shutdown waits at most two seconds for cleanup before stopping the bridge. `/reload` preserves resources; revoke starts cleanup without blocking. Hard process termination or unavailable Chrome can still leave owned tabs open. To point pi-chrome at an existing tab, pass `targetId`, `urlIncludes`, or `titleIncludes`. |