From ae0e6d4ea16c8232957d84c226c9c874c7c5f1c1 Mon Sep 17 00:00:00 2001
From: Dani Bednarski <49581958+DaniBedz@users.noreply.github.com>
Date: Sun, 17 May 2026 00:24:02 +1000
Subject: feat: lazy-register chrome tools until /chrome authorize

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.
---
 package-lock.json | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 package-lock.json

(limited to 'package-lock.json')

diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 0000000..2d590fa
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,25 @@
+{
+	"name": "pi-chrome",
+	"version": "0.15.21",
+	"lockfileVersion": 3,
+	"requires": true,
+	"packages": {
+		"": {
+			"name": "pi-chrome",
+			"version": "0.15.21",
+			"license": "MIT",
+			"peerDependencies": {
+				"@earendil-works/pi-coding-agent": "*",
+				"typebox": "*"
+			},
+			"peerDependenciesMeta": {
+				"@earendil-works/pi-coding-agent": {
+					"optional": true
+				},
+				"typebox": {
+					"optional": true
+				}
+			}
+		}
+	}
+}
-- 
cgit v1.2.3