Commit Graph

1 Commits

Author SHA1 Message Date
usulpro 80c918d282 telegram: move session secrets to .env, launch MCP via wrapper
- .mcp.json: both telegram servers now start via scripts/telegram-mcp.sh
  <usulsu|helper> instead of hardcoding session strings — config is now
  secret-free and safe to commit.
- scripts/telegram-mcp.sh: sources .env, selects the per-account session
  string (TELEGRAM_SESSION_STRING / TELEGRAM_SESSION_STRING_HELPER), execs
  the telegram-mcp binary (path overridable via TELEGRAM_MCP_BIN).
- scripts/regen_telegram_session.sh: rewritten — captures the generated
  string, saves it to .secrets/session_<account>.txt, and upserts it into
  .env. Fixes the broken /projects/... generator path.
- package.json: tg:session:usulsu / tg:session:helper npm scripts.
- .gitignore: ignore .secrets/.

Root cause of the dead session: hardcoded strings lived in git, so laptop
and VPS shared one auth_key across two IPs and Telegram revoked it. Strings
now live only in local, gitignored files — one per device/account.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-08 00:44:06 +07:00