aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2026-09-25ship the pi side we actually run, not a different arrangementIgor Soarez
The README told pi users to install pi-chrome directly and run /chrome authorize every session. That is not how this is used: pi reaches the same MCP server through pi-mcp-adapter, with pi's own pi-chrome switched off, which is why nobody types /chrome authorize. pi/browser-gate.ts is that setup's missing piece, generalised from the one in use: it answers pi-mcp-adapter's approval broker for one server, asking once per session instead of once per call (the adapter's own grant only covers identical arguments, so for a browser it asks nearly every time). /browser authorize, /browser revoke, and PI_BROWSER_AUTHORIZE for headless runs. approveTools stays on in mcp.json as the backstop if the gate does not load. The README now leads with that: install the adapter, register the server in mcp.json, copy the gate. Installing pi-chrome in pi is kept as the alternative, with what it costs - two definitions of the browser, /chrome authorize per session, and the trap of loading the extension twice. Tested on an isolated pi config against a stand-in browser: with PI_BROWSER_AUTHORIZE the call reaches the browser, without it the gate denies it.
2026-10-14FORK.md: what the fork changes, setup, upstream releasesIgor Soarez
2026-10-14feat(remote): drive a companion extension on another host through a brokerIgor Soarez
PI_CHROME_REMOTE=host:port sends every command to a broker/broker.mjs there, with its bearer token, instead of binding a bridge on this machine. Unset, the extension behaves as upstream. A remote session never binds or takes over a port: when the broker is unreachable the tools fail rather than drive some other browser. A pi-chrome-remote prompt section says which browser chrome_* drives and how files move to and from its host; chrome_upload_file wants absolute paths there. PI_CHROME_AUTHORIZE grants every session up front.
2026-10-14broker: a standalone bridge for the browser's hostIgor Soarez
Upstream's bridge lives inside whichever pi session started first on the machine running the browser, and only serves that machine. The broker takes its place permanently: upstream's HTTP contract to the extension on loopback, and /command and /status on a second, private address for other hosts, behind a bearer token (PI_CHROME_TOKEN, or PI_CHROME_TOKEN_COMMAND).
2026-09-28Release 0.15.57 (#28)Tianren Dong
2026-09-28Drop the full-screen tab rule for automation targets (#27)Tianren Dong
0.15.54 opened Pi's automation target as a tab in the user's window while it was full screen, assuming macOS would merge a new window into it as a hidden window tab. Chrome disables automatic window tabbing (app_controller_mac.mm), so that never happens; the hidden tabs came from the tab-group bug fixed in 0.15.56. Always prefer Pi's own window.
2026-09-28Report hidden Pi tab in /chrome doctor (#26)Tianren Dong
Chrome ignores clicks and typing in hidden pages. Doctor now asks the worker whether this session's own tab is visible (automation.status includeVisibility, which never creates or activates a tab) and reports the reason and fix when it is hidden.
2026-09-28Keep tab ownership across extension reloads (#25)Tianren Dong
storage.session is wiped when the extension reloads, which it does on every pi-chrome update, so Pi lost track of its automation window and session tabs and left them behind. Mirror ownership to storage.local, restore it only when the session copy is missing, re-check every restored tab (same window; adopted tabs still in Pi's group), and drop the local copy on browser startup.
2026-09-28Merge pull request #24 from tianrendong/fix/fill-textarea-and-new-tab-captureTianren Dong
Fill whole textareas; cover new tabs' first page with early capture
2026-09-28Create session tab groups in the tab's own windowTianren Dong
chrome.tabs.group without createProperties.windowId creates the group in the current (user's) window and moves the tab there, so a session's automation tab left its dedicated window and became a hidden inactive tab. Make the unit mock match Chrome's behavior.
2026-09-28Release 0.15.56Tianren Dong
2026-09-28Fill whole textareas; cover new tabs' first page with early captureTianren Dong
chrome_fill's triple-click selected one line of a multi-line textarea, so fill replaced only that line. Select value fields with the selectAll editing command before deleting. Early capture now waits for in-flight tab.new creations, so a first page that commits before the tab is tracked is still captured.
2026-09-26Release 0.15.55Tianren Dong
2026-09-26Merge pull request #23 from tianrendong/fix/cache-friendly-primerTianren Dong
Make Chrome primer and authorization log prompt-cache friendly
2026-09-26Make Chrome primer and authorization log prompt-cache friendlyTianren Dong
- Contribute the primer as a structured prompt section instead of forcing systemPrompt. - Log pi-chrome-tool-change as a rendered custom entry that is not sent to the model.
2026-09-26Merge pull request #22 from tianrendong/fix/early-capture-scopeTianren Dong
Stop console capture from tripping DevTools detection; scope early capture to Pi tabs
2026-09-26Stop console capture from tripping DevTools detection; scope early capture ↵Tianren Dong
to Pi tabs Fixes #9. Sites like BOSS Zhipin log an object with a getter/toString trap and close the tab if it is read. Store captured console args raw and serialize them on read without running page code (data properties only, accessors as [getter], built-ins via native getters). Inject document-start capture only into Pi's automation tab and session-tracked tabs.
2026-09-26Merge pull request #21 from tianrendong/fix/hidden-input-uploads-screenshotsTianren Dong
Report hidden-tab input, append targeted typing, smarter uploads, prune screenshots; release 0.15.54
2026-09-26Report hidden-tab input, append targeted typing, smarter uploads, prune ↵Tianren Dong
screenshots; release 0.15.54 - Check page visibility before trusted input: Chrome drops input to hidden pages (inactive tabs, covered/minimized windows, macOS window tabs behind full screen). Type/key/hover/scroll/tap/drag fail fast with the reason; click/fill use their DOM fallback immediately (or reject with domFallback:false). - Use an inactive tab instead of a new window for the automation target while the user's window is full screen. - chrome_type with uid/selector moves the caret to the end (moveToEndOfDocument) after its focus click. - chrome_upload_file: labels/wrappers resolve to their file input, same-origin iframe search, and intercepted file chooser for upload buttons (trusted click when visible, user-gesture click when hidden); reject multiple paths for single-file inputs; no duplicate change event. - Prune default-folder chrome_screenshot captures (7 days, newest 20 kept, retentionDays override). - input.debug without a target no longer calls tabs.get(-1). - New hidden-input unit suite.
2026-09-26Merge pull request #20 from tianrendong/feat/absorb-fork-featuresTianren Dong
Absorb fork fixes and features; release 0.15.53
2026-09-26Absorb fork fixes and features; release 0.15.53Tianren Dong
Adapted from community forks (ardhiqii, kkunkunya, nihar-oracle, steimerbyte): - Abort stalled /next long polls after 45s; time out, retry, and single-post results. - Fall back to CDP Runtime.evaluate when chrome.scripting is refused (about:blank automation tabs). - Load pi-chrome in same-process subagent sessions as a bridge client; client chrome_launch reports owner status. - Add chrome_cdp (validated raw CDP passthrough, background-guarded, payload summarization) and chrome_cdp_targets. - chrome_type reports before/after values, insertedAt, splice/unchanged warnings; add replace=true. - includeSnapshot waits for navigations started by the action; tab.new reports the settled tab. - CDP timeouts surface as timeouts and are not re-sent after the cleanup detach. - Activate/deactivate chrome_find and chrome_inspect with the rest of the chrome_* tools. - New unit suites: bridge-resilience, cdp-passthrough, type-evidence.
2026-09-10Merge pull request #17 from tianrendong/refactor/chrome-command-surfaceTianren Dong
Simplify Chrome status commands and release 0.15.51
2026-09-10Simplify Chrome status commands and release 0.15.51Tianren Dong
2026-09-10Merge pull request #16 from tianrendong/docs/readme-0.15.50Tianren Dong
docs: clarify background controls and release 0.15.50
2026-09-10docs: clarify background controls and release 0.15.50Tianren Dong
2026-09-10Merge pull request #15 from tianrendong/docs/readme-onboardingTianren Dong
docs: improve pi-chrome README and onboarding
2026-09-10docs: improve pi-chrome README and onboardingTianren Dong
2026-09-10Merge pull request #14 from tianrendong/fix/input-reliabilityTianren Dong
Improve Chrome input reliability and release 0.15.49
2026-09-10Improve Chrome input reliability and release 0.15.49Tianren Dong
2026-09-09Merge pull request #13 from tianrendong/fix/hard-background-policyTianren Dong
Enforce hard background and release 0.15.48
2026-09-09Enforce hard background and release 0.15.48Tianren Dong
2026-09-09Merge pull request #12 from tianrendong/fix/session-cleanup-safetyTianren Dong
Fix session cleanup and release 0.15.47
2026-09-09Fix session cleanup and release 0.15.47Tianren Dong
2026-07-07Fix Chrome authorization update loggingTianren Dong
2026-07-07Record Chrome tool authorization state explicitlyTianren Dong
2026-07-07Log Chrome tool authorization changesTianren Dong
2026-06-25Release v0.15.43Tianren Dong
2026-06-25Make README capabilities user-facingTianren Dong
2026-06-25Release v0.15.42Tianren Dong
2026-06-25Remove README quick start sectionTianren Dong
2026-06-25Release v0.15.41Tianren Dong
2026-06-25Shorten README and move architecture docsTianren Dong
2026-06-220.15.40: keep automation targets in session groupTianren Dong
2026-06-22Keep Pi-created tabs in one session groupTianren Dong
2026-06-220.15.39: dedicated pi-chrome automation tab/window isolation (#6)TJ Dong
Stop pi-chrome from hijacking the user's active tab. Page/navigation actions with no explicit target now route to a dedicated automation window owned by the calling Pi session (falling back to a dedicated tab if a window can't be made), instead of overwriting whatever the user has open. - Session-scoped ownership: Map<sessionKey, target> in the service worker, keyed by a sessionKey forwarded from index.ts, so concurrent sessions (one shared extension) never fight over a window or close each other's tabs. - Persistence: ownership mirrored to chrome.storage.session so a service-worker restart re-hydrates and reuses the window instead of orphaning it. Cleared on full browser restart; restored windows are then left alone (never reclaimed). - getTabByParams default branch resolves the owned target; tab.activate/close/ group/ungroup pass createOwnedTarget:false so management never auto-creates a throwaway tab or falls back to the user's active tab. - Session-group integration: the dedicated-window tab still joins this session's tab group, in its own window; grouping stays best-effort. - Lifecycle: cleanup on /chrome revoke and real session end (not /reload); fire-and-forget so it never blocks /quit, /reload, or shutdown. - Tests: new test-suite/unit/automation-target.test.mjs (isolation, reuse, concurrency, restart/reconnect re-hydration, guarded tab.*, group integration, window->tab fallback, robust cleanup). Docs + CHANGELOG updated.
2026-06-08feat: show remaining auth time in Chrome Bridge status bar (#5)TJ Dong
* 0.15.36: richer chrome_snapshot + chrome_find/chrome_inspect (ported from foxfirecodes fork) - chrome_snapshot returns a concise observation (layout, hints, actions, forms, page map, query matches, diff) with mode/query/maxTextChars params - new chrome_find (query -> ranked uids) and chrome_inspect (deep element context, with page.inspect fallback) - includeSnapshot on click/type/fill/key now embeds the formatted snapshot - snapshot/inspect logic shipped as eval-free packaged snapshot_injected.js, sharing window.__PI_CHROME_STATE__ (el- uid scheme) with existing input helpers * feat: show remaining auth time in Chrome Bridge status bar Before: ● Chrome Bridge After: ● Chrome Bridge (14m) ● Chrome Bridge (indefinite) Changes: - authCountdownLabel() computes remaining minutes from chromeAuthorizedUntil - updateChromeStatus appends the label to the status line - startCountdownTicker() runs setInterval every 60s to refresh the display while a timed authorization is active; no-ops for indefinite auth - clearCountdownInterval() called in lockChromeControl and session_shutdown so no interval leaks on revoke or reload - scheduleAuthExpiry calls startCountdownTicker so the ticker starts whenever authorization is granted or restored after /reload --------- Co-authored-by: Tianren Dong <tianrendong.dtr@gmail.com>
2026-06-070.15.38: harden chrome input overlay handlingTianren Dong
2026-06-070.15.37: harden Chrome input targetingTianren Dong
2026-06-070.15.37: clarify README installation instructions (#4)Tianren Dong
2026-06-07Clarify README installation instructions (#4)TJ Dong