@deadragdoll/tellymcp 0.0.13 → 0.0.15

package/README.md

@@ -27,6 +27,7 @@ The current model is gateway-first:
 
 - exposes MCP tools for human Telegram interaction
 - lets one agent ask another agent to do work and return files or notes
+- lets MCP chat clients retrieve project text, images, and artifacts from a selected console
 - stores structured xchange records in `.mcp-xchange`
 - supports browser automation with Playwright
 - can attach to an already running Firefox or Chrome tab through bundled local extensions
@@ -66,6 +67,7 @@ Human-facing:
 - `telegram_message` records
 - `notify_telegram`
 - `browser_screenshot(send_to_telegram=true)`
+- `get_file` for returning screenshots and artifacts to MCP chat clients
 
 Agent-to-agent:
 
@@ -74,6 +76,10 @@ Agent-to-agent:
 - `send_partner_file`
 - `list_gateway_sessions`
 
+Diagnostics:
+
+- `get_runtime_diagnostics` for safe end-to-end gateway/client health checks
+
 Browser:
 
 - `browser_open`
@@ -87,6 +93,15 @@ Browser:
 - `browser_recording_stop`
 - `browser_recording_status`
 
+Files:
+
+- `get_file_list(source=..., limit=...)`
+- `get_file(file_path=..., type="url")`
+- `get_file(file_path=..., type="image")`
+- `get_file(file_path=..., type="text")`
+- `get_file(file_path=..., type="base64")`
+- `get_file(selector="latest_screenshot")`
+
 Tools sync:
 
 - `refresh_tools_markdown`
@@ -95,17 +110,38 @@ Tools sync:
 ## Requirements
 
 - Node.js `>= 24`
-- Redis
+- Python 3, `make`, and a C/C++ toolchain on Linux so `node-pty` can build its native addon; npm lifecycle scripts must be enabled
+- Redis for gateway and `both` modes only; clients do not use Redis
 - PostgreSQL for gateway mode
 - optional RabbitMQ for durable gateway fanout
 - Playwright browser binaries if you use browser tools
 
 ## Installation
 
+On Debian/Ubuntu, install the native PTY build prerequisites first:
+
+```bash
+sudo apt install -y python3 make g++
+npm config set ignore-scripts false
+```
+
+```bash
+npm install -g @deadragdoll/tellymcp --foreground-scripts
+```
+
+The published `node-pty` dependency does not provide a Linux ARM64 binary, so
+the install lifecycle builds `pty.node` locally. If a previous installation
+completed without it, repair the global package with:
+
 ```bash
-npm install -g @deadragdoll/tellymcp
+npm rebuild -g @deadragdoll/tellymcp --foreground-scripts
+tellymcp doctor --env <file>
 ```
 
+`tellymcp --help` and setup commands do not load the native PTY module. Runtime
+startup validates it and prints the same recovery instructions instead of a
+raw native-module stack trace.
+
 Optional browser runtime:
 
 ```bash
@@ -139,9 +175,20 @@ Create a gateway workspace and env:
 ```bash
 mkdir -p ~/telly-gateway
 cd ~/telly-gateway
-tellymcp init gateway
+tellymcp configure
 ```
 
+This opens a token-protected local page on `127.0.0.1`. Choose `Gateway` in the
+wizard, fill and validate the settings, then save `.env-gateway` through the
+normal browser download flow. Set its permissions to `0600` before use. Use
+`tellymcp init gateway` when you specifically want a commented template for
+manual editing.
+
+Enter the public origin or API base only once. The wizard derives gateway HTTP,
+WebSocket, Mini App, webhook, root-prefix, and optional OAuth connector URLs.
+The key stages include live connection checks for Telegram, Redis, PostgreSQL,
+the gateway HTTP/WebSocket endpoints, and optional RabbitMQ.
+
 Or copy the sample from this package:
 
 - [.env.example.gateway](./.env.example.gateway)
@@ -156,7 +203,8 @@ Required gateway values:
 - `DB_NAME`
 - `GATEWAY_PUBLIC_URL`
 - `GATEWAY_WS_URL`
-- `GATEWAY_TOKEN`
+- `GATEWAY_SCOPE_TOKEN`
+- `GATEWAY_AUTH_TOKEN`
 
 Then run:
 
@@ -171,9 +219,17 @@ Create one workspace per agent console:
 ```bash
 mkdir -p ~/agent-a
 cd ~/agent-a
-tellymcp init client
+tellymcp configure
 ```
 
+Choose `Client` in the wizard. The form includes the gateway connection, local
+console identity, terminal, browser, MCP, and advanced runtime settings.
+After validation the browser downloads `.env-client`. Use `--no-open` to print
+the local URL without opening a browser automatically.
+
+For clients, the same Public base URL automatically produces
+`GATEWAY_PUBLIC_URL`, `GATEWAY_WS_URL`, and `GATEWAY_WS_PATH`.
+
 Or copy:
 
 - [.env.example.client](./.env.example.client)
@@ -182,7 +238,8 @@ Required client values:
 
 - `GATEWAY_PUBLIC_URL`
 - `GATEWAY_WS_URL`
-- `GATEWAY_TOKEN`
+- `GATEWAY_SCOPE_TOKEN`
+- `GATEWAY_AUTH_TOKEN` (the same transport token configured on the gateway)
 - `GATEWAY_USER_UUID` if this console should be scoped to a specific Telegram owner
 
 Recommended:
@@ -201,6 +258,10 @@ After that, `.mcpsession.json` stores:
 - `local_session_id`
 - `session_label`
 - `env_file`
+- `gateway_client_uuid`
+
+Client runtime state is local and does not require Redis. The persisted
+`gateway_client_uuid` keeps the client identity stable across restarts.
 
 So later the same workspace can usually start with:
 
@@ -339,6 +400,7 @@ Expected agent behavior:
 
 Use the shipped samples as the canonical starting point:
 
+- [Environment contract and migration guide](./docs/ENVIRONMENT.md)
 - [.env.example.gateway](./.env.example.gateway)
 - [.env.example.client](./.env.example.client)
 
@@ -354,6 +416,8 @@ The samples were cleaned to match the current runtime:
 - removed obsolete pairing-oriented wording
 - removed unused secrets like `SESSION_SECRET`
 - removed unused `APP_NAME`
+- renamed ambiguous legacy keys to `TERMINAL_*`, `GATEWAY_SCOPE_TOKEN`,
+  `TELEGRAM_REQUEST_MODE`, `DB_SCHEMA`, and `LOGFEED_ENABLED`
 
 ## Operational Commands
 
@@ -369,11 +433,21 @@ Destructive local+gateway cleanup:
 tellymcp system-prune --env .env --yes
 ```
 
+Normalize an older env file to the current role-aware contract:
+
+```bash
+tellymcp migrate-env ./old.env > ./.migrated-env
+```
+
+The runtime does not fall back to the old schema. If legacy keys are detected,
+startup stops and prints the migration command.
+
 ## Documentation Map
 
 - [README-ru.md](./README-ru.md)
 - [STANDALONE.md](./docs/STANDALONE.md)
 - [STANDALONE-ru.md](./docs/STANDALONE-ru.md)
+- [CHAT_CONNECTOR.md](./docs/CHAT_CONNECTOR.md) — ChatGPT/Claude OAuth connector
 - [TOOLS.md](./TOOLS.md)
 - [screenshots/README.md](./screenshots/README.md)
 

package/TOOLS.md

@@ -1,6 +1,6 @@
 # Tools
 
-Version: `2026-06-06.1`
+Version: `2026-06-06.2`
 
 Gateway/client runtime compatibility:
 
@@ -18,6 +18,9 @@ Browser tools:
 
 - `browser_list_attached_instances`
 - `browser_list_tabs`
+- `browser_attach_active_tab`
+- `browser_attach_tab`
+- `browser_detach_tab`
 - `browser_recording_start`
 - `browser_recording_stop`
 - `browser_recording_status`
@@ -44,8 +47,8 @@ Browser runtime rule:
   - attached browser tab backend for a real user Firefox or Chrome session
   - isolated Playwright Chromium backend
 - `browser_open` is only for the isolated Playwright backend.
-- `browser_list_attached_instances` and `browser_list_tabs` are for the attached browser backend.
-- if the local attach extension is connected and a tab was selected from the browser control panel, `browser_click`, `browser_fill`, `browser_inject_script`, `browser_press`, `browser_dom`, and `browser_screenshot` use that attached browser tab for the current session without requiring `browser_open`
+- `browser_list_attached_instances`, `browser_list_tabs`, `browser_attach_active_tab`, `browser_attach_tab`, and `browser_detach_tab` are for the attached browser backend.
+- after a tab is attached for the current session, `browser_click`, `browser_fill`, `browser_inject_script`, `browser_press`, `browser_wait_for`, `browser_wait_for_url`, `browser_dom`, `browser_computed_style`, `browser_reload`, `browser_screenshot`, `browser_console`, `browser_errors`, `browser_network_failures`, `browser_clear_logs`, and `browser_close` use that attached browser tab without requiring `browser_open`
 - `browser_recording_start`, `browser_recording_stop`, and `browser_recording_status` are also for the attached browser backend
 - browser recordings are written under `.mcp-xchange/web/{tab-title-slug}-{timestamp}/`
 - each recording bundle contains `session.json`, `timeline.ndjson`, `pages/`, `network/`, and `console/`
@@ -80,13 +83,16 @@ Collaboration tools:
 
 Utility tools:
 
+- `get_file_list`
+- `get_file`
 - `refresh_tools_markdown`
 
 ## Console model
 
 Gateway-first runtime model:
 
-- agents register themselves on the gateway automatically through `GATEWAY_TOKEN`
+- agents authenticate the gateway HTTP/WS transport through `GATEWAY_AUTH_TOKEN`
+  and register into their gateway scope through `GATEWAY_SCOPE_TOKEN`
 - Telegram no longer links sessions with pair codes
 - `/menu` in the gateway bot shows available remote consoles directly
 - one running agent console is one logical session/console target
@@ -111,7 +117,18 @@ Preferred order for cross-console work:
    - `send_partner_note`
    - `send_partner_file`
    - browser tools
-   with explicit `session_id` for the current console or explicit target routing fields for another console.
+     with explicit `session_id` for the current console or explicit target routing fields for another console.
+
+Preferred file-return flow for MCP chat clients:
+
+1. Resolve the selected live console and keep its canonical `session_id`.
+2. If the user refers to an existing managed file without an exact path, call `get_file_list` and select the matching `file_path`.
+3. If creating a screenshot now, call `browser_screenshot` and keep its returned `file_path`.
+4. For an exact Markdown, source-code, or other UTF-8 project path, call `get_file(type = "text")`; arbitrary project files are not discovered by `get_file_list`.
+5. For binary files, call `get_file` with the selected or newly returned `file_path`; default to `type = "url"`.
+6. If the chat cannot fetch an image URL, repeat the same call with `type = "image"` for a native inline MCP image block.
+7. If a host such as Claude.ai replaces the native block with `[image]`, retry with `type = "base64"`; this host-independent fallback returns the complete JSON, including raw `data`, in a regular MCP text block.
+8. If the user asks for the most recent existing screenshot, `get_file(selector = "latest_screenshot")` is the direct shortcut.
 
 ## `set_session_context`
 
@@ -190,6 +207,136 @@ Output:
 - `terminal?`
   Terminal runtime metadata for the console.
 
+## `get_runtime_diagnostics`
+
+Purpose:
+
+- Run safe, read-only health checks for one console through the same gateway route used by normal tools.
+- Diagnose configuration, runtime state storage, PTY state, version/protocol metadata, and gateway-to-client relay without returning secrets or raw connection strings.
+- Redis is probed only for gateway/`both` runtimes. On a client, the `redis` compatibility check reports that Redis is not required and process-local state is active.
+- Return a structured degraded result when relay fails instead of a deeply nested backend exception.
+
+Input:
+
+- `session_id?`
+  In gateway mode, use the canonical `session_id` returned by `list_gateway_sessions`.
+
+Output:
+
+- `status`
+  - `ok`
+  - `degraded`
+- `checked_at`
+- `session_id`
+- `runtime`
+  - `mode`
+  - `package_version`
+  - `protocol_version`
+  - `node_id?`
+- `checks`
+  - `configuration`
+  - `redis`
+  - `session_store`
+  - `terminal`
+  - `gateway_configuration`
+  - `relay`
+
+Each check contains only `status` and a redacted human-readable `message`.
+
+## `get_file_list`
+
+Purpose:
+
+- List managed files available in a selected console workspace before calling `get_file`.
+- Return exact `file_path` values accepted by `get_file`.
+
+Input:
+
+- `session_id`
+- `source?`
+  - `telegram-upload`
+  - `browser-screenshot`
+  - `partner-artifact`
+- `limit?`
+  - default: `50`
+  - maximum: `200`
+
+Output:
+
+- `total`
+- `files[]`
+  - `file_path`
+  - `filename`
+  - `mimetype`
+  - `source`
+  - `size_bytes?`
+  - `created_at`
+
+Behavior:
+
+- results are ordered newest first
+- `total` is the number of matching managed files before `limit` is applied
+- this tool lists TellyMCP-managed Telegram uploads, browser screenshots, and partner artifacts; it does not recursively enumerate arbitrary source files in the workspace
+- in gateway mode, always pass the canonical `session_id = client_uuid:local_session_id`
+- pass the chosen `files[].file_path` unchanged to `get_file`
+
+## `get_file`
+
+Purpose:
+
+- Return the actual content of a file from a selected console workspace to an MCP chat client.
+- URL mode creates a bounded temporary gateway copy; text and base64 modes relay content directly.
+
+Input:
+
+- `session_id`
+- `type?`
+  - `url` (default)
+  - `image` (native inline image plus download URL)
+  - `text` (native UTF-8 MCP text content)
+  - `base64` (fallback)
+- exactly one of:
+  - `file_path`
+  - `selector = "latest_screenshot"`
+
+Output:
+
+- `type`
+- `data`
+  - short-lived HTTPS URL when `type = "url"`
+  - short-lived HTTPS URL when `type = "image"`; the actual pixels are in the native MCP image content block
+  - decoded UTF-8 file content when `type = "text"`
+  - base64 payload when `type = "base64"`
+- `mimetype`
+- `filename`
+- `size_bytes`
+- `expires_at?`
+
+Behavior:
+
+- in gateway mode, always pass the canonical `session_id = client_uuid:local_session_id` returned by `list_gateway_sessions`
+- `file_path` may be the exact path returned by `browser_screenshot`, so the human does not need to know generated filenames
+- `selector = "latest_screenshot"` selects the newest file metadata with `source = "browser-screenshot"` for that session
+- file reads are limited to the selected console workspace, including after symlink resolution
+- exact project-relative paths such as `README.md` or `src/test.ts` are accepted even though `get_file_list` only discovers managed artifacts
+- text mode returns the decoded file directly as a native MCP text content block and rejects invalid UTF-8 or binary NUL content
+- source extensions such as `.ts` and `.tsx` use text MIME overrides instead of the generic MPEG/octet-stream mappings
+- sensitive paths including live `.env` files, credential stores, private-key extensions, and secret directories are rejected server-side; documented `.env.example`/`.env.sample`/`.env.template` files remain readable
+- URL mode uploads the file as a binary stream to `.tellymcp/tmp/file-links` on the gateway and returns a link valid for 10 minutes
+- temporary-link filenames are sanitized before storage and download headers: control and filesystem-reserved characters are replaced, while a safe basename is preserved
+- image mode is explicit: `structuredContent.type` is `image`, `structuredContent.data` contains the URL, and the native top-level MCP `image` is the first content block without duplicating base64 into structured output
+- image mode accepts only `image/*` files up to the safe native-inline limit; use `url` for larger images
+- URL links allow up to three GET downloads; HEAD requests do not consume the limit
+- if URL fetching fails for an image, retry with `type = "image"`
+- base64 mode is the compatibility fallback for hosts that replace native images with `[image]` or hide `structuredContent`: it returns the complete JSON payload, including raw base64 in `data`, as a regular MCP text block and does not emit a native image
+- base64 mode is bounded by the final MCP response body limit
+- do not attempt to bypass the sensitive-file policy or retrieve renamed secrets
+
+Screenshot examples:
+
+- "take a screenshot and send it": call `browser_screenshot`, then pass its returned `file_path` to `get_file`
+- "send the latest screenshot": call `get_file` with `selector = "latest_screenshot"`
+
 ## `refresh_tools_markdown`
 
 Purpose:
@@ -447,7 +594,7 @@ Required agent practice:
   - "tell frontend what changed"
   - "send the error to your teammate"
   - "tell the other agent what's new"
-  then the correct path is `send_partner_note`
+    then the correct path is `send_partner_note`
 
 How to find the partner correctly:
 
@@ -507,7 +654,7 @@ Reply rule for project asks:
   - `Reply project_uuid: ...`
   - `Reply target_client_uuid: ...`
   - `Reply target_local_session_id: ...`
-  or a `Reply Params` section with the same data
+    or a `Reply Params` section with the same data
 - then reply with those exact values
 - if `in_reply_to` is available, prefer `Reply message_uuid`
 - if only the note `share_id` is available, gateway now also accepts that value in `in_reply_to`
@@ -608,7 +755,7 @@ How the receiving agent must react:
   - `проверь xchange records`
   - `telegram_message`
   - `partner_note`
-  then do not start with a legacy inbox-specific tool
+    then do not start with a legacy inbox-specific tool
 - instead:
   1. call `list_xchange_records`
   2. identify the newest relevant record by category:
@@ -836,10 +983,68 @@ Output:
 Notes:
 
 - if only one attached browser instance is connected, `instance_id` can be omitted
-- current tab selection for the attach backend is done from the browser extension control panel
+- tab selection for the attach backend can be done either from the browser extension control panel or through `browser_attach_active_tab` / `browser_attach_tab`
 - `active=true` means the tab is active in its browser window; there may be more than one such tab across multiple windows
 - for the tab currently selected for this MCP session, prefer `selected=true`
 
+## `browser_attach_active_tab`
+
+Purpose:
+
+- attach the current MCP session to the active tab of a connected attached browser instance
+
+Input:
+
+- `session_id?`
+- `instance_id?`
+
+Output:
+
+- `session_id`
+- `backend`
+- `instance_id`
+- `tab_id`
+- `attached_at`
+- `title?`
+- `url?`
+
+## `browser_attach_tab`
+
+Purpose:
+
+- attach the current MCP session to a specific attached browser tab by `tab_id`
+
+Input:
+
+- `session_id?`
+- `instance_id?`
+- `tab_id`
+
+Output:
+
+- `session_id`
+- `backend`
+- `instance_id`
+- `tab_id`
+- `attached_at`
+- `title?`
+- `url?`
+
+## `browser_detach_tab`
+
+Purpose:
+
+- detach the current MCP session from the currently selected attached browser tab
+
+Input:
+
+- `session_id?`
+
+Output:
+
+- `session_id`
+- `detached`
+
 ## `browser_recording_start`
 
 Purpose:
@@ -1227,6 +1432,8 @@ Output:
 Purpose:
 
 - inspect computed styles and box metrics for a DOM element in the session browser tab
+- if the session has a selected attached browser tab, inspect that real browser tab
+- otherwise inspect the isolated Playwright page
 
 Input:
 
@@ -1284,7 +1491,9 @@ Notes:
 
 Purpose:
 
-- close the isolated browser context for the current session
+- close the current browser target for the session
+- if the session has a selected attached browser tab, close that real browser tab and clear the attach state
+- otherwise close the isolated Playwright browser context
 
 Input:
 

package/config/templates/env.both.template

@@ -19,8 +19,7 @@ REDIS_HOST=127.0.0.1
 REDIS_PORT=6379
 REDIS_DB=1
 
-MODE=reject
-PAIR_CODE_TTL_SECONDS=300
+TELEGRAM_REQUEST_MODE=reject
 
 MCP_HTTP_HOST=127.0.0.1
 MCP_HTTP_PORT=8787
@@ -29,13 +28,27 @@ MCP_HTTP_PATH=/mcp
 MCP_HTTP_ENABLE_DEBUG_ROUTES=false
 MCP_HTTP_ENABLE_PRUNE_ROUTE=false
 
+# ChatGPT / Claude OAuth connector. Setting any OAuth value enables the facade.
+# TELLYMCP_PUBLIC_URL=https://your-domain.example/api
+# TELLYMCP_OAUTH_ISSUER=https://your-domain.example/api
+# TELLYMCP_OAUTH_AUDIENCE=https://your-domain.example/api
+# TELLYMCP_MAGIC_TOKEN=change_me_private_connector_token
+# TELLYMCP_MAGIC_TOKEN_HASH=sha256:<hex>
+# TELLYMCP_OAUTH_CLIENT_ID=tellymcp
+# TELLYMCP_OAUTH_CLIENT_SECRET=
+# TELLYMCP_ALLOWED_REDIRECT_URIS=https://chatgpt.com/connector/oauth/...,https://claude.ai/api/mcp/auth_callback
+# TELLYMCP_OAUTH_PRIVATE_KEY_PEM="-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n"
+# TELLYMCP_AUTH_CODE_TTL_SECONDS=300
+# TELLYMCP_OAUTH_SCOPES=tellymcp:read tellymcp:write
+# TELLYMCP_OAUTH_KEY_ID=tellymcp-oauth
+
 DISTRIBUTED_MODE=both
 GATEWAY_PUBLIC_URL=
 GATEWAY_WS_URL=
 GATEWAY_WS_PATH=/api/gateway/ws
-GATEWAY_TOKEN=
+GATEWAY_SCOPE_TOKEN=
 GATEWAY_USER_UUID=
-# GATEWAY_AUTH_TOKEN=
+GATEWAY_AUTH_TOKEN=
 
 ROOT_PREFIX=/api
 PORT=8080
@@ -47,7 +60,7 @@ DB_PORT=5432
 DB_USER=
 DB_PASSWORD=
 DB_NAME=
-DB_SCHEME=mcp
+DB_SCHEMA=mcp
 
 # RMQ_HOST=127.0.0.1
 # RMQ_PORT=5672
@@ -63,7 +76,6 @@ WEBAPP_INITDATA_TTL_SECONDS=300
 WEBAPP_SESSION_TTL_SECONDS=900
 WEBAPP_LAUNCH_MODE=fullscreen
 WEBAPP_VISIBLE_SCREENS=10
-WEBAPP_POLL_INTERVAL_MS=2000
 WEBAPP_ACTION_COOLDOWN_MS=150
 
 MCP_XCHANGE_DIR=.mcp-xchange
@@ -100,4 +112,4 @@ BROWSER_SLOW_MO_MS=0
 LOG_LEVEL=info
 LOG_FILE_ENABLED=false
 LOG_FILE_PATH=.tellymcp/log.jsonl
-ENABLE_LOGFEED=0
+LOGFEED_ENABLED=0

package/config/templates/env.client.template

@@ -4,12 +4,8 @@
 # TELLYMCP_SESSION_ID=NEW
 # TELLYMCP_SESSION_LABEL=NEW
 
-REDIS_HOST=127.0.0.1
-REDIS_PORT=6379
-REDIS_DB=1
-
-MODE=reject
-PAIR_CODE_TTL_SECONDS=300
+# Client state is process-local. Redis is gateway-only.
+TELEGRAM_REQUEST_MODE=reject
 
 MCP_HTTP_HOST=127.0.0.1
 MCP_HTTP_PORT=8787
@@ -22,9 +18,9 @@ DISTRIBUTED_MODE=client
 GATEWAY_PUBLIC_URL=
 GATEWAY_WS_URL=
 GATEWAY_WS_PATH=/api/gateway/ws
-GATEWAY_TOKEN=
+GATEWAY_SCOPE_TOKEN=
 GATEWAY_USER_UUID=
-# GATEWAY_AUTH_TOKEN=
+GATEWAY_AUTH_TOKEN=
 
 TERMINAL_SHELL=bash
 TERMINAL_COLS=120
@@ -44,16 +40,6 @@ TERMINAL_PROMPT_SCAN_INTERVAL_SECONDS=15
 TERMINAL_PROMPT_SCAN_COOLDOWN_SECONDS=120
 TERMINAL_PROMPT_SCAN_STRATEGY=strict
 TERMINAL_PROMPT_SCAN_MIN_SCORE=5
-WEBAPP_ENABLED=true
-WEBAPP_BASE_PATH=/webapp
-WEBAPP_PUBLIC_URL=
-WEBAPP_INITDATA_TTL_SECONDS=300
-WEBAPP_SESSION_TTL_SECONDS=900
-WEBAPP_LAUNCH_MODE=fullscreen
-WEBAPP_VISIBLE_SCREENS=10
-WEBAPP_POLL_INTERVAL_MS=2000
-WEBAPP_ACTION_COOLDOWN_MS=150
-
 MCP_XCHANGE_DIR=.mcp-xchange
 
 BROWSER_ENABLED=true
@@ -66,6 +52,10 @@ BROWSER_WAIT_UNTIL=load
 # BROWSER_EXECUTABLE_PATH=
 # BROWSER_CHANNEL=chrome
 BROWSER_SLOW_MO_MS=0
+# BROWSER_ATTACH_ENABLED=true
+# BROWSER_ATTACH_WS_HOST=127.0.0.1
+# BROWSER_ATTACH_WS_PORT=9999
+# BROWSER_ATTACH_WS_PATH=/browser-attach/ws
 
 NAMESPACE=mcp
 NODE_ID=agent
@@ -73,4 +63,4 @@ NODE_ID=agent
 LOG_LEVEL=info
 LOG_FILE_ENABLED=false
 LOG_FILE_PATH=.tellymcp/log.jsonl
-ENABLE_LOGFEED=0
+LOGFEED_ENABLED=0