Skip to content

Raistlin has cooked — v0.2 TelegramBot integration#45

Closed
RaistlinMuc wants to merge 2 commits intoDimillian:mainfrom
RaistlinMuc:pr/telegrambot-v0.2
Closed

Raistlin has cooked — v0.2 TelegramBot integration#45
RaistlinMuc wants to merge 2 commits intoDimillian:mainfrom
RaistlinMuc:pr/telegrambot-v0.2

Conversation

@RaistlinMuc
Copy link

Summary

Adds an optional Telegram bot integration to CodexMonitor (desktop builds). It can:

  • Link a Telegram user to CodexMonitor via a short /link <code> handshake.
  • Show a /status overview of workspaces + recent threads (with inline buttons).
  • Let a user pick an agent/thread and send prompts from Telegram.
  • Post optional notifications:
    • app started/stopped
    • agent completed

Setup

  1. Create a bot with @Botfather and copy the bot token.

  2. In CodexMonitor open Settings → Integrations → Telegram.

  3. Toggle Enable Telegram.

  4. Paste the Bot token and click Check token.

  5. Send the displayed message to your bot:

    /link <code>

  6. In Telegram run /status, pick an agent, then start sending messages.

Notes

  • The Telegram runtime uses getUpdates long-polling.
  • “Working…” messages are cleaned up (deleted) once a reply is ready.
  • Long replies are chunked to respect Telegram message length limits.
  • Linking persists by updating the app settings file (allowlist + default chat id).

Security

  • The bot token is stored in the app settings file.
  • Linking uses a per-install pairing secret hashed into a short code.

Testing

  • npm run typecheck
  • cargo check (Rust stable)

@RaistlinMuc RaistlinMuc force-pushed the pr/telegrambot-v0.2 branch 2 times, most recently from 24d8a80 to 7ab9eea Compare January 15, 2026 09:21
@RaistlinMuc
Copy link
Author

Closing in favor of a cleaner, rebased integrations rework PR (NATS/CloudKit/Telegram) with minimal UI changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant