| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-06-07 | 0.15.38: harden chrome input overlay handling | Tianren Dong | |
| 2026-06-07 | 0.15.37: clarify README installation instructions (#4) | Tianren Dong | |
| 2026-05-17 | chore: release v0.15.27 | Tianren Dong | |
| 2026-05-16 | 0.15.26: update docs for benchmark gates | Tianren Dong | |
| 2026-05-16 | 0.15.25: fix reload after stale singleton | Tianren Dong | |
| 2026-05-16 | 0.15.24: unload Chrome tools when locked | Tianren Dong | |
| 2026-05-16 | 0.15.23: attribute fork features | Tianren Dong | |
| 2026-05-16 | 0.15.22: pull fork improvements | Tianren Dong | |
| 2026-05-16 | feat: lazy-register chrome tools until /chrome authorize | Dani 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. | |||
