@deadragdoll/tellymcp 0.0.12 → 0.0.13

package/docs/STANDALONE-ru.md

@@ -31,6 +31,8 @@ npm install -g @deadragdoll/tellymcp
 
 ```bash
 tellymcp browser install
+tellymcp extension firefox
+tellymcp extension chrome
 tellymcp codex-plugin install
 ```
 
@@ -91,7 +93,41 @@ TELLYMCP_SESSION_ID=NEW
 TELLYMCP_SESSION_LABEL=NEW
 ```
 
-## 5. Запуск
+## 5. Attach extensions для браузера
+
+Если нужно attach'иться к уже открытому Firefox или Chrome на агентской машине, включи локальный attach bridge в env этого агента:
+
+```env
+BROWSER_ATTACH_ENABLED=true
+BROWSER_ATTACH_WS_HOST=127.0.0.1
+BROWSER_ATTACH_WS_PORT=9999
+BROWSER_ATTACH_WS_PATH=/browser-attach/ws
+```
+
+Выгрузи unpacked extension bundle из установленного пакета:
+
+```bash
+tellymcp extension firefox
+tellymcp extension chrome
+```
+
+Команда создаст один из каталогов:
+
+- `./tellymcp-firefox-attach`
+- `./tellymcp-chrome-attach`
+
+Дальше загрузи его в локальный браузер:
+
+- Firefox: `about:debugging#/runtime/this-firefox` -> `Load Temporary Add-on` -> выбрать `manifest.json`
+- Chrome: `chrome://extensions` -> включить Developer mode -> `Load unpacked` -> выбрать выгруженный каталог
+
+После этого browser control panel умеет:
+
+- attach'ить текущую agent-сессию к живой вкладке
+- запускать и останавливать structured recording bundles в `.mcp-xchange/web/...`
+- инжектить helper scripts в attached tab
+
+## 6. Запуск
 
 Gateway:
 
@@ -111,7 +147,7 @@ tellymcp run --env .env -s NEW
 tellymcp run
 ```
 
-## 6. Webhook
+## 7. Webhook
 
 Gateway поддерживает polling и webhook.
 
@@ -131,7 +167,7 @@ TELEGRAM_WEBHOOK_SECRET=change_me_webhook_secret
 - `/api/webapp`
 - `/api/healthz`
 
-## 7. MCP
+## 8. MCP
 
 Локальный client-mode MCP endpoint:
 
@@ -141,7 +177,7 @@ http://127.0.0.1:8787/mcp
 
 Используй MCP HTTP endpoint, который поднимает `tellymcp run`.
 
-## 8. Проверки
+## 9. Проверки
 
 ```bash
 tellymcp doctor --env .env
@@ -153,7 +189,7 @@ tellymcp doctor --env .env
 tellymcp system-prune --env .env --yes
 ```
 
-## 9. Операционные заметки
+## 10. Операционные заметки
 
 - gateway-бот — это основной user-facing control plane
 - консоли видны из gateway live registry
@@ -162,7 +198,7 @@ tellymcp system-prune --env .env --yes
 - browser screenshot для человека лучше отправлять через `browser_screenshot(send_to_telegram=true)`
 - файлы между консолями лучше отправлять через `send_partner_file`
 
-## 10. Чего не делать в новых setup
+## 11. Чего не делать в новых setup
 
 Не строй новые setup вокруг:
 

package/docs/STANDALONE.md

@@ -31,6 +31,8 @@ Optional:
 
 ```bash
 tellymcp browser install
+tellymcp extension firefox
+tellymcp extension chrome
 tellymcp codex-plugin install
 ```
 
@@ -91,7 +93,41 @@ TELLYMCP_SESSION_ID=NEW
 TELLYMCP_SESSION_LABEL=NEW
 ```
 
-## 5. Run
+## 5. Attached Browser Extensions
+
+If you want to attach TellyMCP to an already running Firefox or Chrome tab on an agent machine, enable the local attach bridge in that agent env:
+
+```env
+BROWSER_ATTACH_ENABLED=true
+BROWSER_ATTACH_WS_HOST=127.0.0.1
+BROWSER_ATTACH_WS_PORT=9999
+BROWSER_ATTACH_WS_PATH=/browser-attach/ws
+```
+
+Export the unpacked extension bundle from the installed package:
+
+```bash
+tellymcp extension firefox
+tellymcp extension chrome
+```
+
+This creates one of:
+
+- `./tellymcp-firefox-attach`
+- `./tellymcp-chrome-attach`
+
+Load it into the local browser:
+
+- Firefox: `about:debugging#/runtime/this-firefox` -> `Load Temporary Add-on` -> choose `manifest.json`
+- Chrome: `chrome://extensions` -> enable Developer mode -> `Load unpacked` -> choose the exported directory
+
+After that the browser control panel can:
+
+- attach the current agent session to a live browser tab
+- start and stop structured recording bundles in `.mcp-xchange/web/...`
+- inject helper scripts into the attached tab
+
+## 6. Run
 
 Gateway:
 
@@ -111,7 +147,7 @@ After `.mcpsession.json` is created in the workspace, later runs can usually use
 tellymcp run
 ```
 
-## 6. Webhook
+## 7. Webhook
 
 Gateway supports polling and webhook.
 
@@ -131,7 +167,7 @@ If nginx already proxies `location /api/ { ... }` to the standalone listener, th
 - `/api/webapp`
 - `/api/healthz`
 
-## 7. MCP
+## 8. MCP
 
 Local client-mode MCP:
 
@@ -141,7 +177,7 @@ http://127.0.0.1:8787/mcp
 
 Use the MCP HTTP endpoint exposed by `tellymcp run`.
 
-## 8. Health Checks
+## 9. Health Checks
 
 ```bash
 tellymcp doctor --env .env
@@ -153,7 +189,7 @@ Destructive cleanup:
 tellymcp system-prune --env .env --yes
 ```
 
-## 9. Operational Notes
+## 10. Operational Notes
 
 - the gateway bot is the user-facing control plane
 - consoles are discovered from the gateway live registry
@@ -162,7 +198,7 @@ tellymcp system-prune --env .env --yes
 - browser screenshot replies to humans should use `browser_screenshot(send_to_telegram=true)`
 - file results between consoles should use `send_partner_file`
 
-## 10. Legacy Concepts To Avoid
+## 11. Legacy Concepts To Avoid
 
 Do not build new setups around:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deadragdoll/tellymcp",
-  "version": "0.0.12",
+  "version": "0.0.13",
   "description": "TellyMCP - Telegram control plane for MCP-connected coding agents",
   "main": "dist/services/features/telegram-mcp/runtime.service.js",
   "bin": {
@@ -8,6 +8,8 @@
   },
   "files": [
     "dist",
+    "packages/firefox-attach-extension/dist",
+    "packages/chrome-attach-extension/dist",
     "scripts",
     "config/templates",
     "config/codex",
@@ -36,8 +38,9 @@
   },
   "scripts": {
     "postinstall": "node ./scripts/postinstall.js",
-    "prepack": "yarn build",
-    "prepublishOnly": "yarn build && yarn lint && yarn test",
+    "build:extensions": "node ./packages/firefox-attach-extension/scripts/build.mjs && node ./packages/chrome-attach-extension/scripts/build.mjs",
+    "prepack": "yarn build && yarn build:extensions",
+    "prepublishOnly": "yarn build && yarn build:extensions && yarn lint && yarn test",
     "mcp:local": "codex mcp add telegramHuman --url http://127.0.0.1:8787/mcp",
     "dev:gw": "TS_NODE_TRANSPILE_ONLY=1 TS_NODE_EXPERIMENTAL_RESOLVER=1 NODE_OPTIONS=--openssl-legacy-provider ts-node ./node_modules/moleculer/bin/moleculer-runner.js src/services --config src/moleculer.config.ts --envfile /opt/tellymcp-gateway/.env-gateway --hot --mask \"**/*.service.ts\"",
     "dev:builder": "TS_NODE_TRANSPILE_ONLY=1 TS_NODE_EXPERIMENTAL_RESOLVER=1 NODE_OPTIONS=--openssl-legacy-provider ts-node ./node_modules/moleculer/bin/moleculer-runner.js src/services --config src/moleculer.config.ts --envfile ./.env-builder --hot --mask \"**/*.service.ts\"",