diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-09-09 23:37:02 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-09-09 23:48:50 -0400 |
| commit | c1f230eeb76aaa50e98d3fe7d838573612b6e36f (patch) | |
| tree | 6e00b9d63a630a674b6a3bf6936bd85f82d4aade /README.md | |
| parent | 641ae30f7963ad962e162ff0dfbd80966b09a516 (diff) | |
Enforce hard background and release 0.15.48
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 10 |
1 files changed, 9 insertions, 1 deletions
@@ -108,13 +108,21 @@ Security details: [`SECURITY.md`](./SECURITY.md). Architecture details: [`docs/A /chrome status # connection + auth + background state /chrome authorize [duration] /chrome revoke -/chrome background on # default: don't steal focus +/chrome background on # default: hard background policy /chrome background off # foreground/watch mode /chrome background status ``` If loaded extension is older than installed `pi-chrome`, `/chrome doctor` tells you to reload it from `chrome://extensions`. +### Background policy + +`/chrome background on` is enforced, not an overridable default. Per-call `background:false` cannot bring Chrome forward, new tabs stay inactive, and `chrome_tab activate` is blocked. Use the existing `/chrome background off` for foreground/watch mode; per-call `background:true` still works when that mode is off. + +Screenshots use CDP without activating background tabs. Debugger/capture failures return errors, never an activation fallback. Reload both Pi and the Chrome companion after upgrading; old companions reject background tab creation/screenshots rather than silently switching tabs. + +This prevents explicit pi-chrome focus/activation, not every Chrome/OS side effect. Trusted input, page popups, native prompts, debugger banners, and macOS Spaces can still affect focus. Inactive pages may throttle rendering or reject focus-gated actions. See [scope and risks](./docs/ARCHITECTURE.md#scope-and-risks). + --- ## Limits |