6 Commits

Author	SHA1	Message	Date
Greg Scher	753c6766a0	Remove text truncation limits from Telegram posts ... Posts were being cut to 300 chars (source ingestion) and 150 chars (alert evaluation), losing valuable OSINT context. The sendMessage chunker already handles the 4096-char Telegram API limit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-20 16:49:58 -04:00
satoshipanic	801293356c	fix(telegram): restore command auth boundary and scope command registration ... Restrict command handling to TELEGRAM_CHAT_ID again to prevent arbitrary private chats from executing privileged bot commands. Keep reply routing, @BotName parsing, and long-message chunking while scoping setMyCommands to the configured chat only. Made-with: Cursor	2026-03-18 08:20:32 +01:00
satoshipanic	28121298cf	fix(telegram): split long messages at 4096 chars to avoid truncation ... - Add TELEGRAM_MAX_TEXT and _chunkText(); send multiple messages when over limit - Prefer newline boundaries to avoid breaking Markdown Made-with: Cursor	2026-03-17 14:41:47 +01:00
satoshipanic	2a0b73e5a6	fix(telegram): register slash commands and support DM/group two-way bot ... - Call setMyCommands on startup for private and group chat scopes - Parse /cmd@BotName in groups; reply to originating chat - Allow sendMessage chatId override for command replies Made-with: Cursor	2026-03-17 14:41:47 +01:00
calesthio	3674fcb4f7	Crucix — agent with dashboard, delta engine, Telegram/Discord bots	2026-03-14 00:35:31 -07:00
calesthio	ef2c6470fb	Initial release — Crucix Intelligence Engine v2.0.0 ... 26-source OSINT intelligence engine with live Jarvis dashboard, auto-refresh via SSE, optional LLM layer (4 providers), delta/memory system, and Telegram breaking news alerts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-12 23:45:46 -07:00