@deadragdoll/tellymcp 0.0.10 → 0.0.12

package/VERSION.md

@@ -28,7 +28,7 @@ For detailed engineering history, refactors, and internal development notes, see
   - inbox/session flows
   - project/collab flows
   - live approval prompts
-  - tmux and operational bot notices
+  - terminal and operational bot notices
 
 ## 0.0.9
 
@@ -55,8 +55,8 @@ For detailed engineering history, refactors, and internal development notes, see
   - expired in-process WebApp sessions (`401/403`) trigger automatic re-bootstrap
   - reopening the Mini App is no longer required in the normal restart case
 - Runtime MCP metadata now reports the actual package version instead of stale hardcoded version data.
-- Successful tmux nudges no longer overwrite `tmuxPaneId` with non-pane targets such as `backend:0.0`.
-- If tmux itself is unavailable for a paired session with a saved tmux target, Telegram now receives an operational warning instead of leaving the signal only in backend logs.
+- Successful terminal nudges no longer overwrite stale target metadata with non-target values such as `backend:0.0`.
+- If the terminal runtime itself is unavailable for a paired session with a saved terminal target, Telegram now receives an operational warning instead of leaving the signal only in backend logs.
 
 ## 0.0.8
 
@@ -66,8 +66,8 @@ For detailed engineering history, refactors, and internal development notes, see
   - optional JSONL file sink for Alloy or other collectors
   - `LOG_FILE_ENABLED=true`
   - `LOG_FILE_PATH=.tellymcp/log.jsonl`
-- Better tmux recovery behavior:
-  - when a saved pane target becomes stale after tmux recreation, TellyMCP now tries to recover the live pane automatically from stored tmux session/window/pane hints
+- Better terminal target recovery behavior:
+  - when a saved target becomes stale after terminal recreation, TellyMCP now tries to recover the live terminal automatically from stored terminal hints
   - if auto-recovery fails, Telegram sends a clear operational warning instead of leaving the problem only in logs
 - Stronger `Share` execution guidance:
   - the current session must do the work itself
@@ -83,8 +83,8 @@ For detailed engineering history, refactors, and internal development notes, see
   - optional `LogFeed` buffer for UI diagnostics
 
 ### Fixed
-- Stale tmux pane ids like `%1 -> %2` no longer require manual user understanding before the service can try to wake the session again.
-- Broken tmux nudge targets are now visible to the user in Telegram, not only in backend logs.
+- Stale terminal target ids no longer require manual user understanding before the service can try to wake the session again.
+- Broken terminal nudge targets are now visible to the user in Telegram, not only in backend logs.
 - `Share` inbox instructions are now explicit enough to reduce the chance that one agent re-delegates the task back into the collaboration graph.
 - `Live` Mini App now survives a normal gateway restart much better:
   - short `502/503` periods recover through polling
@@ -100,8 +100,8 @@ For detailed engineering history, refactors, and internal development notes, see
   - `tellymcp doctor`
   - `tellymcp mcp --help`
 - Standalone and public installation guides:
-  - [STANDALONE.md](STANDALONE.md)
-  - [STANDALONE-ru.md](STANDALONE-ru.md)
+  - [STANDALONE.md](docs/STANDALONE.md)
+  - [STANDALONE-ru.md](docs/STANDALONE-ru.md)
 - Browser runtime helper:
   - `tellymcp browser install`
 - Public README set for GitHub and npm:
@@ -116,13 +116,13 @@ For detailed engineering history, refactors, and internal development notes, see
   - MCP/WebApp/Gateway endpoints
 - Live text input button:
   - `[txt]`
-  - sends literal text to tmux without pressing `Enter`
+  - sends literal text to the terminal without pressing `Enter`
 
 ### Changed
 - Default installation path is now npm-first:
   - `npm install -g @deadragdoll/tellymcp`
 - Standalone client mode is documented first, before gateway/both deployment.
-- `tmux` is now documented as a strongly recommended prerequisite for the full experience:
+- Built-in PTY terminal control is now documented as the default prerequisite for the full experience:
   - Live View
   - nudges
   - direct terminal control from Telegram
@@ -178,8 +178,8 @@ For detailed engineering history, refactors, and internal development notes, see
 - `TOOLS.md` sync now detects outdated or missing local instructions and asks the session to refresh them.
 
 ### Removed
-- Legacy Go/HTTP tmux proxy path was removed.
-- Direct product path is now local `tmux` only.
+- Legacy Go/HTTP terminal proxy path was removed.
+- Direct product path is now the local built-in terminal runtime only.
 
 ## Next entry template
 

package/config/codex/plugins/telly-workflows/.codex-plugin/plugin.json

@@ -0,0 +1,18 @@
+{
+  "name": "telly-workflows",
+  "version": "0.1.0+codex.20260522215959",
+  "description": "Static workflows and operational rules for telegram_mcp consoles.",
+  "author": {
+    "name": "Local developer"
+  },
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Telly Workflows",
+    "shortDescription": "Stable workflows for telegram_mcp sessions.",
+    "longDescription": "Telly Workflows adds static Codex skills for partner-note execution, human Telegram replies, browser screenshots, and artifact-return paths without relying on ad-hoc polling or route guessing.",
+    "developerName": "Local developer",
+    "category": "Productivity",
+    "capabilities": [],
+    "defaultPrompt": "Use the telly-workflows skills when working through telegram_mcp, especially for partner-note execution, browser screenshots, and human Telegram replies."
+  }
+}

package/config/codex/plugins/telly-workflows/references/invariants.md

@@ -0,0 +1,10 @@
+# Operational Invariants
+
+1. Do not stop at inspection when a request requires a real outbound action.
+2. Do not call `mark_xchange_record_read` before the required outbound tool succeeds.
+3. Do not use `sleep` plus repeated `list_xchange_records` polling in the same turn after sending a partner request.
+4. For inter-session work, the target console returns results to the source console, not directly to the human Telegram chat.
+5. For human screenshot requests, prefer `browser_open` plus `browser_screenshot(send_to_telegram=true)` when the current console owns the browser runtime.
+6. For partner screenshot requests, prefer `browser_open` plus `browser_screenshot`, then `send_partner_file` back to the source console.
+7. Prefer `send_partner_file` over `send_partner_note` whenever the result is a real local file.
+8. Do not invent routing or route-guessing fallbacks when the canonical path is known.

package/config/codex/plugins/telly-workflows/skills/telly-browser-screenshot/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: telly-browser-screenshot
+description: Use when a telegram_mcp task says to open a webpage, use browser_open, take a screenshot with browser_screenshot, send a screenshot to Telegram with send_to_telegram=true, or return a screenshot artifact to another console with send_partner_file. Prefer this over shell Playwright fallbacks for browser screenshot work.
+---
+
+# Telly Browser Screenshot
+
+Use this skill when the task says to open a webpage and make a screenshot.
+
+## Rules
+
+- Prefer `browser_open` and `browser_screenshot`.
+- Do not replace the browser workflow with shell Playwright unless browser tools actually fail.
+- If the screenshot must go straight back to the human Telegram chat from this console, set `send_to_telegram=true`.
+- If the screenshot must go to another console, save the PNG through `browser_screenshot`, then return it with `send_partner_file`.
+- Do not dig through sqlite or session context to guess delivery routes when the requested flow is already known.
+
+## Preferred patterns
+
+Human-facing screenshot:
+1. `browser_open`
+2. `browser_screenshot(send_to_telegram=true)`
+
+Partner-facing screenshot:
+1. `browser_open`
+2. `browser_screenshot`
+3. `send_partner_file`

package/config/codex/plugins/telly-workflows/skills/telly-collab-artifact/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: telly-collab-artifact
+description: Use when a telegram_mcp collab or partner_note task must return a real file or artifact such as a screenshot, html file, txt file, report, or generated output. Prefer send_partner_file over send_partner_note when the result exists as a local file, and return the artifact to the source console before any human Telegram reply.
+---
+
+# Telly Collab Artifact
+
+Use this skill when the result must include a real file.
+
+## Rules
+
+- Prefer `send_partner_file` whenever the result already exists as a local file.
+- Do not paste file contents into `send_partner_note` if a real file path is available.
+- For inter-session work, return the artifact to the source console, then let the source console handle the human-facing reply.
+- Only fall back to `send_partner_note` without `send_partner_file` when the result is purely textual.
+
+## Preferred pattern
+
+1. Produce the local file in the current console.
+2. Verify the path exists in the current workspace.
+3. Call `send_partner_file`.
+4. Only after success, call `mark_xchange_record_read` if the incoming note required a reply.

package/config/codex/plugins/telly-workflows/skills/telly-human-telegram/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: telly-human-telegram
+description: Use when the current console received a human telegram_message, needs to reply through notify_telegram, or needs to open a page and send a browser screenshot back to the human with browser_screenshot(send_to_telegram=true). This skill covers direct human-facing telegram_mcp requests, not partner-to-partner return paths.
+---
+
+# Telly Human Telegram
+
+Use this skill when the current console received a human Telegram request through `telegram_message`.
+
+## Rules
+
+- Start with `get_xchange_record` for the newest relevant `telegram_message`.
+- If the request needs a text reply, finish with `notify_telegram`.
+- If the request needs a browser screenshot sent to the human, use `browser_open` and then `browser_screenshot` with `send_to_telegram=true`.
+- Do not save a screenshot locally and then search sqlite, route metadata, or session context just to deliver it.
+- Do not stop at analysis or a summary.
+- Call `mark_xchange_record_read` only after the required outbound tool succeeds.
+
+## Preferred patterns
+
+Text reply:
+1. `get_xchange_record`
+2. do the work
+3. `notify_telegram`
+4. `mark_xchange_record_read`
+
+Browser screenshot reply:
+1. `get_xchange_record`
+2. `browser_open`
+3. `browser_screenshot(send_to_telegram=true)`
+4. `mark_xchange_record_read`

package/config/codex/plugins/telly-workflows/skills/telly-partner-note/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: telly-partner-note
+description: Use when the current console received an incoming partner_note, xchange partner request, inter-session task, collab ask/share request, or agent-to-agent reply path. Start with get_xchange_record, do the work in this console, return the result with send_partner_note or send_partner_file, and only then call mark_xchange_record_read.
+---
+
+# Telly Partner Note
+
+Use this skill when the current console received an incoming `partner_note`.
+
+## Rules
+
+- Start with `get_xchange_record`.
+- Read whether the note is a `request`, `question`, `reply`, or `handoff`.
+- If the note requires a reply, the task is not complete until `send_partner_note` or `send_partner_file` succeeds.
+- Do not stop at reading the note, listing files, or summarizing the task.
+- Do not call `mark_xchange_record_read` before the outbound reply succeeds.
+- If the newest note is `kind=reply` and does not require a reply, process the result and do not create another reply loop.
+
+## Return path
+
+- Return the result to the source console.
+- Do not send the result directly to the human Telegram chat from the target console unless the instruction explicitly says this console is the human-facing endpoint.
+
+## Preferred patterns
+
+Text result:
+1. `get_xchange_record`
+2. do the work in this console
+3. `send_partner_note`
+4. `mark_xchange_record_read`
+
+Artifact result:
+1. `get_xchange_record`
+2. do the work in this console
+3. `send_partner_file`
+4. `mark_xchange_record_read`

package/config/templates/env.both.template

@@ -2,15 +2,25 @@
 
 TELEGRAM_BOT_TOKEN=
 TELEGRAM_BOT_USERNAME=
+# ADMIN_TOKEN=
 # DEBUG_LANGUAGE=ru
-PROJECT_NAME=
+# TELEGRAM_WEBHOOK_ENABLED=true
+# TELEGRAM_WEBHOOK_PATH=/telegram/webhook
+# TELEGRAM_WEBHOOK_PUBLIC_URL=https://your-domain.example/api/telegram/webhook
+# TELEGRAM_WEBHOOK_SECRET=change_me_webhook_secret
+# TELEGRAM_WEBHOOK_TRACE=false
+# TELEGRAM_WEBHOOK_DROP_PENDING_UPDATES=false
+
+# PROJECT_NAME=
+# TELLYMCP_SESSION_ID=NEW
+# TELLYMCP_SESSION_LABEL=NEW
 
 REDIS_HOST=127.0.0.1
 REDIS_PORT=6379
 REDIS_DB=1
 
-MODE=queue
-PAIR_CODE_TTL_SECONDS=600
+MODE=reject
+PAIR_CODE_TTL_SECONDS=300
 
 MCP_HTTP_HOST=127.0.0.1
 MCP_HTTP_PORT=8787
@@ -23,13 +33,14 @@ DISTRIBUTED_MODE=both
 GATEWAY_PUBLIC_URL=
 GATEWAY_WS_URL=
 GATEWAY_WS_PATH=/api/gateway/ws
-GATEWAY_AUTH_TOKEN=
+GATEWAY_TOKEN=
+GATEWAY_USER_UUID=
+# GATEWAY_AUTH_TOKEN=
 
 ROOT_PREFIX=/api
-APP_NAME=tellymcp
+PORT=8080
 NAMESPACE=mcp
 NODE_ID=both
-PORT=8080
 
 DB_HOST=127.0.0.1
 DB_PORT=5432
@@ -43,7 +54,7 @@ DB_SCHEME=mcp
 # RMQ_USER=
 # RMQ_PASSWORD=
 # RMQ_VHOST=/
-# RMQ_EXCHANGE=tellymcp
+# RMQ_EXCHANGE=telegram_mcp.gateway
 
 WEBAPP_ENABLED=true
 WEBAPP_BASE_PATH=/webapp
@@ -51,25 +62,34 @@ WEBAPP_PUBLIC_URL=
 WEBAPP_INITDATA_TTL_SECONDS=300
 WEBAPP_SESSION_TTL_SECONDS=900
 WEBAPP_LAUNCH_MODE=fullscreen
-WEBAPP_VISIBLE_SCREENS=2
+WEBAPP_VISIBLE_SCREENS=10
 WEBAPP_POLL_INTERVAL_MS=2000
 WEBAPP_ACTION_COOLDOWN_MS=150
 
 MCP_XCHANGE_DIR=.mcp-xchange
 
-TMUX_NUDGE_ENABLED=true
-TMUX_NUDGE_DEBOUNCE_SECONDS=10
-TMUX_NUDGE_COOLDOWN_SECONDS=30
-TMUX_NUDGE_MESSAGE=проверь inbox
-TMUX_PARTNER_NUDGE_MESSAGE=не inbox: прочитай SHARED_INDEX.md и partner note
-TMUX_CAPTURE_MODE=visible
-TMUX_CAPTURE_LINES=300
-# TMUX_SOCKET_PATH=
+TERMINAL_SHELL=bash
+TERMINAL_COLS=120
+TERMINAL_ROWS=40
+TERMINAL_SCROLLBACK_LINES=4000
 
+TERMINAL_NUDGE_ENABLED=true
+TERMINAL_NUDGE_DEBOUNCE_SECONDS=10
+TERMINAL_NUDGE_COOLDOWN_SECONDS=30
+TERMINAL_NUDGE_MESSAGE=получи newest telegram_message через list_xchange_records/get_xchange_record, выполни запрос и ответь человеку через notify_telegram; не останавливайся на анализе
+TERMINAL_PARTNER_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record, выполни задачу в текущей консоли и обязательно отправь результат через send_partner_note или send_partner_file; только потом mark_xchange_record_read
+TERMINAL_PARTNER_REPLY_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record; если newest note имеет kind=reply или не требует ответа, не отправляй новый send_partner_note/send_partner_file без явного нового запроса. Если этот reply завершает задачу от человека, сразу отправь финальный результат в Telegram через notify_telegram или send_file_to_telegram; только потом mark_xchange_record_read
+TERMINAL_CAPTURE_MODE=visible
+TERMINAL_CAPTURE_LINES=300
+TERMINAL_PROMPT_SCAN_ENABLED=true
+TERMINAL_PROMPT_SCAN_INTERVAL_SECONDS=15
+TERMINAL_PROMPT_SCAN_COOLDOWN_SECONDS=120
+TERMINAL_PROMPT_SCAN_STRATEGY=strict
+TERMINAL_PROMPT_SCAN_MIN_SCORE=5
 BROWSER_ENABLED=true
 BROWSER_HEADLESS=false
 BROWSER_DEVTOOLS=false
-BROWSER_ADDRESS=http://localhost:5173
+# BROWSER_ADDRESS=http://localhost:5173
 BROWSER_TIMEOUT_MS=20000
 BROWSER_MAX_EVENTS=200
 BROWSER_WAIT_UNTIL=load
@@ -78,7 +98,6 @@ BROWSER_WAIT_UNTIL=load
 BROWSER_SLOW_MO_MS=0
 
 LOG_LEVEL=info
-ENABLE_LOGFEED=0
 LOG_FILE_ENABLED=false
-SESSION_SECRET=change_me_session_secret
-TOKEN_BINDING_SECRET=change_me_token_binding_secret
+LOG_FILE_PATH=.tellymcp/log.jsonl
+ENABLE_LOGFEED=0

package/config/templates/env.client.template

@@ -1,16 +1,15 @@
 # TellyMCP client node
 
-TELEGRAM_BOT_TOKEN=
-TELEGRAM_BOT_USERNAME=
-# DEBUG_LANGUAGE=ru
-PROJECT_NAME=
+# PROJECT_NAME=
+# TELLYMCP_SESSION_ID=NEW
+# TELLYMCP_SESSION_LABEL=NEW
 
 REDIS_HOST=127.0.0.1
 REDIS_PORT=6379
 REDIS_DB=1
 
-MODE=queue
-PAIR_CODE_TTL_SECONDS=600
+MODE=reject
+PAIR_CODE_TTL_SECONDS=300
 
 MCP_HTTP_HOST=127.0.0.1
 MCP_HTTP_PORT=8787
@@ -23,33 +22,44 @@ DISTRIBUTED_MODE=client
 GATEWAY_PUBLIC_URL=
 GATEWAY_WS_URL=
 GATEWAY_WS_PATH=/api/gateway/ws
-GATEWAY_AUTH_TOKEN=
+GATEWAY_TOKEN=
+GATEWAY_USER_UUID=
+# GATEWAY_AUTH_TOKEN=
 
+TERMINAL_SHELL=bash
+TERMINAL_COLS=120
+TERMINAL_ROWS=40
+TERMINAL_SCROLLBACK_LINES=4000
+
+TERMINAL_NUDGE_ENABLED=true
+TERMINAL_NUDGE_DEBOUNCE_SECONDS=10
+TERMINAL_NUDGE_COOLDOWN_SECONDS=30
+TERMINAL_NUDGE_MESSAGE=получи newest telegram_message через list_xchange_records/get_xchange_record, выполни запрос и ответь человеку через notify_telegram; не останавливайся на анализе
+TERMINAL_PARTNER_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record, выполни задачу в текущей консоли и обязательно отправь результат через send_partner_note или send_partner_file; только потом mark_xchange_record_read
+TERMINAL_PARTNER_REPLY_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record; если newest note имеет kind=reply или не требует ответа, не отправляй новый send_partner_note/send_partner_file без явного нового запроса. Если этот reply завершает задачу от человека, сразу отправь финальный результат в Telegram через notify_telegram или send_file_to_telegram; только потом mark_xchange_record_read
+TERMINAL_CAPTURE_MODE=visible
+TERMINAL_CAPTURE_LINES=300
+TERMINAL_PROMPT_SCAN_ENABLED=true
+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_PUBLIC_URL=
 WEBAPP_INITDATA_TTL_SECONDS=300
 WEBAPP_SESSION_TTL_SECONDS=900
 WEBAPP_LAUNCH_MODE=fullscreen
-WEBAPP_VISIBLE_SCREENS=2
+WEBAPP_VISIBLE_SCREENS=10
 WEBAPP_POLL_INTERVAL_MS=2000
 WEBAPP_ACTION_COOLDOWN_MS=150
 
 MCP_XCHANGE_DIR=.mcp-xchange
 
-TMUX_NUDGE_ENABLED=true
-TMUX_NUDGE_DEBOUNCE_SECONDS=10
-TMUX_NUDGE_COOLDOWN_SECONDS=30
-TMUX_NUDGE_MESSAGE=проверь inbox
-TMUX_PARTNER_NUDGE_MESSAGE=не inbox: прочитай SHARED_INDEX.md и partner note
-TMUX_CAPTURE_MODE=visible
-TMUX_CAPTURE_LINES=300
-# TMUX_SOCKET_PATH=
-
 BROWSER_ENABLED=true
 BROWSER_HEADLESS=false
 BROWSER_DEVTOOLS=false
-BROWSER_ADDRESS=http://localhost:5173
+# BROWSER_ADDRESS=http://localhost:5173
 BROWSER_TIMEOUT_MS=20000
 BROWSER_MAX_EVENTS=200
 BROWSER_WAIT_UNTIL=load
@@ -57,5 +67,10 @@ BROWSER_WAIT_UNTIL=load
 # BROWSER_CHANNEL=chrome
 BROWSER_SLOW_MO_MS=0
 
+NAMESPACE=mcp
+NODE_ID=agent
+
 LOG_LEVEL=info
+LOG_FILE_ENABLED=false
+LOG_FILE_PATH=.tellymcp/log.jsonl
 ENABLE_LOGFEED=0

package/config/templates/env.gateway.template

@@ -2,15 +2,21 @@
 
 TELEGRAM_BOT_TOKEN=
 TELEGRAM_BOT_USERNAME=
+# ADMIN_TOKEN=
 # DEBUG_LANGUAGE=ru
-PROJECT_NAME=
+# TELEGRAM_WEBHOOK_ENABLED=true
+# TELEGRAM_WEBHOOK_PATH=/telegram/webhook
+# TELEGRAM_WEBHOOK_PUBLIC_URL=https://your-domain.example/api/telegram/webhook
+# TELEGRAM_WEBHOOK_SECRET=change_me_webhook_secret
+# TELEGRAM_WEBHOOK_TRACE=false
+# TELEGRAM_WEBHOOK_DROP_PENDING_UPDATES=false
 
 REDIS_HOST=127.0.0.1
 REDIS_PORT=6379
 REDIS_DB=1
 
-MODE=queue
-PAIR_CODE_TTL_SECONDS=600
+MODE=reject
+PAIR_CODE_TTL_SECONDS=300
 
 MCP_HTTP_HOST=127.0.0.1
 MCP_HTTP_PORT=8787
@@ -21,14 +27,15 @@ MCP_HTTP_ENABLE_PRUNE_ROUTE=false
 
 DISTRIBUTED_MODE=gateway
 GATEWAY_PUBLIC_URL=
+GATEWAY_WS_URL=
 GATEWAY_WS_PATH=/api/gateway/ws
-GATEWAY_AUTH_TOKEN=
+GATEWAY_TOKEN=
+# GATEWAY_AUTH_TOKEN=
 
 ROOT_PREFIX=/api
-APP_NAME=tellymcp-gateway
-NAMESPACE=mcp
-NODE_ID=gateway
 PORT=8080
+NAMESPACE=mcp
+NODE_ID=GWAY
 
 DB_HOST=127.0.0.1
 DB_PORT=5432
@@ -42,7 +49,7 @@ DB_SCHEME=mcp
 # RMQ_USER=
 # RMQ_PASSWORD=
 # RMQ_VHOST=/
-# RMQ_EXCHANGE=tellymcp
+# RMQ_EXCHANGE=telegram_mcp.gateway
 
 WEBAPP_ENABLED=true
 WEBAPP_BASE_PATH=/webapp
@@ -50,25 +57,34 @@ WEBAPP_PUBLIC_URL=
 WEBAPP_INITDATA_TTL_SECONDS=300
 WEBAPP_SESSION_TTL_SECONDS=900
 WEBAPP_LAUNCH_MODE=fullscreen
-WEBAPP_VISIBLE_SCREENS=2
+WEBAPP_VISIBLE_SCREENS=10
 WEBAPP_POLL_INTERVAL_MS=2000
 WEBAPP_ACTION_COOLDOWN_MS=150
 
 MCP_XCHANGE_DIR=.mcp-xchange
 
-TMUX_NUDGE_ENABLED=true
-TMUX_NUDGE_DEBOUNCE_SECONDS=10
-TMUX_NUDGE_COOLDOWN_SECONDS=30
-TMUX_NUDGE_MESSAGE=проверь inbox
-TMUX_PARTNER_NUDGE_MESSAGE=не inbox: прочитай SHARED_INDEX.md и partner note
-TMUX_CAPTURE_MODE=visible
-TMUX_CAPTURE_LINES=300
-# TMUX_SOCKET_PATH=
+TERMINAL_SHELL=bash
+TERMINAL_COLS=120
+TERMINAL_ROWS=40
+TERMINAL_SCROLLBACK_LINES=4000
 
-BROWSER_ENABLED=true
+TERMINAL_NUDGE_ENABLED=true
+TERMINAL_NUDGE_DEBOUNCE_SECONDS=10
+TERMINAL_NUDGE_COOLDOWN_SECONDS=30
+TERMINAL_NUDGE_MESSAGE=получи newest telegram_message через list_xchange_records/get_xchange_record, выполни запрос и ответь человеку через notify_telegram; не останавливайся на анализе
+TERMINAL_PARTNER_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record, выполни задачу в текущей консоли и обязательно отправь результат через send_partner_note или send_partner_file; только потом mark_xchange_record_read
+TERMINAL_PARTNER_REPLY_NUDGE_MESSAGE=получи newest partner_note через list_xchange_records/get_xchange_record; если newest note имеет kind=reply или не требует ответа, не отправляй новый send_partner_note/send_partner_file без явного нового запроса. Если этот reply завершает задачу от человека, сразу отправь финальный результат в Telegram через notify_telegram или send_file_to_telegram; только потом mark_xchange_record_read
+TERMINAL_CAPTURE_MODE=visible
+TERMINAL_CAPTURE_LINES=300
+TERMINAL_PROMPT_SCAN_ENABLED=false
+TERMINAL_PROMPT_SCAN_INTERVAL_SECONDS=15
+TERMINAL_PROMPT_SCAN_COOLDOWN_SECONDS=120
+TERMINAL_PROMPT_SCAN_STRATEGY=strict
+TERMINAL_PROMPT_SCAN_MIN_SCORE=5
+BROWSER_ENABLED=false
 BROWSER_HEADLESS=false
 BROWSER_DEVTOOLS=false
-BROWSER_ADDRESS=http://localhost:5173
+# BROWSER_ADDRESS=http://localhost:5173
 BROWSER_TIMEOUT_MS=20000
 BROWSER_MAX_EVENTS=200
 BROWSER_WAIT_UNTIL=load
@@ -77,7 +93,6 @@ BROWSER_WAIT_UNTIL=load
 BROWSER_SLOW_MO_MS=0
 
 LOG_LEVEL=info
-ENABLE_LOGFEED=0
 LOG_FILE_ENABLED=false
-SESSION_SECRET=change_me_session_secret
-TOKEN_BINDING_SECRET=change_me_token_binding_secret
+LOG_FILE_PATH=.tellymcp/log.jsonl
+ENABLE_LOGFEED=0