polygram 0.7.2 → 0.7.3

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Multi-bot, multi-chat, per-topic isolation; SQLite transcripts; inline-keyboard approvals. Bundles /polygram:status|logs|pair-code|approvals admin commands and a history skill.",
   "keywords": [
     "telegram",

package/config.example.json

@@ -15,6 +15,8 @@
       "attachmentConcurrency": 6,
       "queueWarnThreshold": 20,
       "replayWindowMs": 180000,
+      "_comment_chrome": "Opt-in to Claude Code's Chrome-extension browser-automation integration. Default false. Requires the 'Claude in Chrome' extension installed in the daemon-user's Chrome browser AND a live GUI session (Chrome must be running). See https://code.claude.com/docs/en/chrome. Per-chat override via `config.chats.<id>.chrome`.",
+      "chrome": false,
       "_comment_pairedChatDefaults": "When a user sends /pair <CODE> from a private chat that isn't in config.chats yet, polygram auto-creates a chat entry using these defaults (merged over top-level `defaults`). Leave out `cwd` at your peril — without it, auto-onboarded DMs have no working directory and pairing will fail.",
       "pairedChatDefaults": {
         "agent": "admin",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Telegram daemon for Claude Code that preserves the OpenClaw per-chat session model. Migration path for OpenClaw users moving to Claude Code.",
   "main": "lib/ipc-client.js",
   "bin": {

package/polygram.js

@@ -640,6 +640,19 @@ let pm = null; // ProcessManager, created in main()
 
 function spawnClaude(sessionKey, ctx) {
   const { chatConfig, existingSessionId, label, chatId } = ctx;
+  // 0.7.3: Claude Code's Chrome-extension integration (browser
+  // automation via the "Claude in Chrome" extension) is OPT-IN and
+  // NOT enabled by default in `claude`. Polygram lets chats turn it
+  // on via `config.chats.<id>.chrome: true` (chat-level wins) or
+  // `config.bot.chrome: true` (per-bot default). When opting in, the
+  // extension must be installed in the daemon-user's Chrome and the
+  // user must have a live Aqua session (so Chrome is running). Falls
+  // back to --no-chrome for chats that don't opt in (matches our
+  // pre-0.7.3 default — defensive against any "enabled by default"
+  // that might have been set in claude's persistent state).
+  const wantChrome = chatConfig.chrome != null
+    ? chatConfig.chrome === true
+    : config.bot?.chrome === true;
   const args = [
     '-p',
     '--input-format', 'stream-json',
@@ -648,7 +661,7 @@ function spawnClaude(sessionKey, ctx) {
     '--model', chatConfig.model || config.defaults.model,
     '--effort', chatConfig.effort || config.defaults.effort,
     '--permission-mode', 'bypassPermissions',
-    '--no-chrome',
+    wantChrome ? '--chrome' : '--no-chrome',
   ];
   if (chatConfig.agent) args.push('--agent', chatConfig.agent);
   if (existingSessionId) args.push('--resume', existingSessionId);