aboutsummaryrefslogtreecommitdiff
path: root/package-lock.json
AgeCommit message (Collapse)Author
2026-09-10Simplify Chrome status commands and release 0.15.51Tianren Dong
2026-09-10docs: clarify background controls and release 0.15.50Tianren Dong
2026-09-10Improve Chrome input reliability and release 0.15.49Tianren Dong
2026-09-09Enforce hard background and release 0.15.48Tianren Dong
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-25Release v0.15.42Tianren Dong
2026-06-25Release v0.15.41Tianren Dong
2026-06-070.15.38: harden chrome input overlay handlingTianren Dong
2026-06-070.15.37: clarify README installation instructions (#4)Tianren Dong
2026-05-17chore: release v0.15.27Tianren Dong
2026-05-160.15.26: update docs for benchmark gatesTianren Dong
2026-05-160.15.25: fix reload after stale singletonTianren Dong
2026-05-160.15.24: unload Chrome tools when lockedTianren Dong
2026-05-160.15.23: attribute fork featuresTianren Dong
2026-05-160.15.22: pull fork improvementsTianren Dong
2026-05-16feat: lazy-register chrome tools until /chrome authorizeDani Bednarski
Defer all pi.registerTool() calls until /chrome authorize fires. Previously, 18 chrome_* tool definitions + chrome-profile-bridge primer consumed ~5K tokens/turn even when Chrome control locked. Changes: - Add chromeToolsRegistered flag (default false) - Wrap all pi.registerTool() calls in registerChromeTools(pi) - Only register tools when authorizeFor() runs - Make before_agent_start conditional: primer injected only when tools registered AND authorized - No tools exist in context until user explicitly allows it Saves ~5,000 tokens/turn when Chrome control is locked.