Previously the outbound loop wrote every message to inbox, causing
the homelab bot to process its own responses as new tasks. Now only
explicit claude.ai send_message tool calls write to inbox.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Claude was just echoing raw text. Now messages include framing:
"[MCP Bridge Task from claude.ai] <message>" with instruction
to acknowledge and begin working.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
MCP bot now writes to ~/homelab/telegram/inbox alongside posting
to the group chat, so the homelab bot can process the messages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bot can't see its own messages via Telegram polling. Now logs them
directly after sending so they appear in pull_updates.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Single-process Python app that:
- Runs a Telegram bot in a group chat, logging all messages/files to libsql
- Exposes send_message, pull_updates, queue_status MCP tools over HTTP
- Downloads and stores file attachments with Telegram file_id + local path
- Accessible via NetBird mesh at mgmt.mg:8321 (no auth needed)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
