# Upstream source - Official repository: - Imported npm version: `pi-chrome@0.15.46` - Imported commit: `017ff4b9a639f0b8b213e58a3f30613fc38edcc8` - Commit date: `2026-07-07T01:30:54-04:00` - Import basis: the `gitHead` recorded in the official npm metadata for `pi-chrome@0.15.46`; no upstream tag points at this commit. - Initial local import: 2026-08-28 The tracked upstream source, tests, documentation, scripts, and license were imported from the official Git repository. Nested `.git`, dependency directories, coverage, and build output are not retained. ## Local maintenance This directory is maintained directly by the `my-pi` bundle and is not a submodule. The root package loads `extensions/chrome-profile-bridge/index.ts` from this directory and depends on it through `file:./pi-chrome`; the npm prebuilt extension entry must not be loaded in parallel. Local changes after the import: - Chrome snapshots are written atomically to owner-only, session-local files under the active project's `.pi/chrome-context/` directory instead of returning raw page structure to model context. - Each session/target keeps only its latest snapshot; browser interactions invalidate stale captures and session shutdown removes the session directory. - `chrome_find` returns compact ranked matches while keeping the complete structured snapshot in the session-local capture for optional `ctx_execute_file` analysis. - `includeSnapshot=true` on click/type/fill/key saves the post-action snapshot and returns its capture path rather than embedding the snapshot in the tool result. When syncing upstream, compare against the imported commit and port changes selectively. Do not overwrite these local lifecycle, privacy, and Context Mode integrations wholesale.