@inetafrica/open-claudia 2.2.10 → 2.2.11

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v2.2.11
+- Telegram replies now get channel-specific formatting guidance in the system prompt: short mobile-friendly sections, single-asterisk Telegram Markdown labels, no tables/headings/Markdown links, and no noisy quotes/backticks around normal business terms.
+- Telegram final/progress messages now request Markdown parse mode, and edited messages support the same parse mode with a plain-text fallback if Telegram rejects the markup.
+
 ## v2.2.10
 - System prompt: explicitly tell the model not to use the Claude Code harness's built-in `ScheduleWakeup` / `CronCreate` tools. Those register timers inside the per-turn Claude Code subprocess, which exits at end-of-turn, so the wakeup silently never fires. Only the `open-claudia schedule-wakeup` / `cron-add` CLI commands (owned by the long-running bot) actually survive. Mirrors the existing warning we already had for harness `TaskCreate` / `TaskUpdate` vs `open-claudia task`.
 

package/channels/telegram/adapter.js

@@ -239,15 +239,21 @@ class TelegramAdapter {
   }
 
   async edit(channelId, messageId, text, opts = {}) {
+    const o = { chat_id: channelId, message_id: messageId };
+    if (opts.parseMode) o.parse_mode = opts.parseMode;
+    const kb = this._normalizeKeyboard(opts.keyboard);
+    if (kb) o.reply_markup = kb;
+
     try {
-      const o = { chat_id: channelId, message_id: messageId };
-      const kb = this._normalizeKeyboard(opts.keyboard);
-      if (kb) o.reply_markup = kb;
       await this.bot.editMessageText(text, o);
     } catch (e) {
       const errMsg = e.message || "";
       if (errMsg.includes("retry after")) return;
       if (errMsg.includes("message is not modified")) return;
+      if (opts.parseMode && o.parse_mode) {
+        delete o.parse_mode;
+        try { await this.bot.editMessageText(text, o); return; } catch (e2) {}
+      }
       if (!errMsg.includes("message to edit not found")) console.error("Edit error:", errMsg);
     }
   }

package/core/runner.js

@@ -22,6 +22,11 @@ const {
 const { getClaudeOAuthToken, claudeAuthRecoveryMessage, isClaudeAuthErrorText, claudeUsageLimitMessage, isClaudeUsageLimitText, runClaudeAuthStatusDiagnostic, claudeSubprocessEnv } = require("./auth-flow");
 const loopback = require("./loopback");
 
+function telegramMarkdownOpts(extra = {}) {
+  const adapter = currentAdapter();
+  return adapter?.type === "telegram" ? { ...extra, parseMode: "Markdown" } : extra;
+}
+
 function chatEnvOverlay() {
   const adapter = currentAdapter();
   const channelId = currentChannelId();
@@ -462,9 +467,9 @@ async function runClaude(prompt, cwd, replyToMsgId, opts = {}) {
       const display = formatProgress(assistantText, toolUses, currentTool, elapsed, currentToolDetail);
       if (display && display !== lastUpdate) {
         if (!state.statusMessageId && assistantText) {
-          state.statusMessageId = await send(display.length > 4000 ? display.slice(-4000) : display, { replyTo: replyToMsgId });
+          state.statusMessageId = await send(display.length > 4000 ? display.slice(-4000) : display, telegramMarkdownOpts({ replyTo: replyToMsgId }));
         } else if (state.statusMessageId) {
-          await editMessage(state.statusMessageId, display.length > 4000 ? display.slice(-4000) : display);
+          await editMessage(state.statusMessageId, display.length > 4000 ? display.slice(-4000) : display, telegramMarkdownOpts());
         }
         lastUpdate = display;
       }
@@ -651,12 +656,12 @@ async function runClaude(prompt, cwd, replyToMsgId, opts = {}) {
       const firstChunk = chunks[0];
 
       if (state.statusMessageId && chunks.length === 1) {
-        await editMessage(state.statusMessageId, firstChunk);
+        await editMessage(state.statusMessageId, firstChunk, telegramMarkdownOpts());
       } else {
-        const sent = await send(firstChunk, { replyTo: replyToMsgId });
+        const sent = await send(firstChunk, telegramMarkdownOpts({ replyTo: replyToMsgId }));
         if (!sent) await send(firstChunk);
         for (let i = 1; i < chunks.length; i++) {
-          await send(chunks[i]);
+          await send(chunks[i], telegramMarkdownOpts());
         }
       }
       if (code !== 0 && code !== null) await send(`Exit code: ${code}`);

package/core/system-prompt.js

@@ -73,6 +73,41 @@ function buildSystemPrompt() {
     }
   } catch (e) {}
 
+  const channelFormattingBlock = adapter?.type === "telegram"
+    ? `
+## Telegram formatting
+Telegram is mobile-first and narrow. Optimize for readability in a small chat bubble.
+
+Use Telegram Markdown v1 only:
+- Bold labels with single asterisks: *Status:* / *Done:* / *Blocked:* / *Next:*
+- Italic with single underscores only when genuinely useful.
+- Inline code with backticks only for commands, file paths, IDs, short field names, and exact errors.
+- Fenced code blocks only for short commands or snippets. Do not paste long logs; save/send a file instead.
+
+Avoid formatting that renders badly or noisily in Telegram:
+- No Markdown tables.
+- No Markdown headings like #, ##, ###.
+- No CommonMark bold like **bold**; use *bold*.
+- No Markdown links like [text](url); use plain URLs when needed.
+- Do not wrap ordinary business words in backticks or quote marks. For example, write Payments completed, not \`Payments\` completed or 'Payments' completed.
+- Avoid large paragraphs. Use short sections, blank lines, and 3-7 concise bullets.
+
+Good Telegram pattern:
+*Status:* CRM sync is still running cleanly.
+
+- Bills and Calls completed.
+- Leads completed with 20 rows.
+- Payments advanced to 2026-05-17 10:50.
+
+*Issue:* JSON parse error after Retention. I’m checking that stream next.
+`
+    : adapter?.type === "kazee"
+      ? `
+## Kazee Chat formatting
+Keep replies clean and mobile-readable. Use short paragraphs and bullets. Avoid Markdown tables unless the user explicitly asks for a table.
+`
+      : "";
+
   return `
 ${soul}
 
@@ -92,7 +127,7 @@ ${soul}
 - Received user files directory: ${FILES_DIR}
 
 ${transcriptPointerNote(state)}
-${currentSpeakerBlock}${teamBlock}${pendingTasksBlock}${slashCommandsBlock}
+${currentSpeakerBlock}${teamBlock}${pendingTasksBlock}${slashCommandsBlock}${channelFormattingBlock}
 ## Delivery
 Reply normally in your final answer. To send a file, image, or voice clip back to the current chat, run the bot CLI from inside this task — channel context is already in the env:
 - \`open-claudia send-file <path> [caption]\` — any document/binary
@@ -151,7 +186,7 @@ If you tell the user "I'll check back in N minutes" or "I'll run this every morn
 
 ## Guidelines
 - Keep responses concise — many users are on mobile.
-- Markdown: *bold*, _italic_, \`code\`, \`\`\`code blocks\`\`\` work on both Telegram and Kazee. Skip headers (#) and links [text](url).
+- Markdown: use simple chat-safe formatting only. On Telegram follow the Telegram formatting section exactly; on Kazee use short bullets/paragraphs and avoid tables unless requested.
 - For long output (logs, diffs, large code), save to a file and send it as an artifact instead of pasting walls of text.
 - Act on screenshots (fix bugs, implement designs) — don't just describe what you see.
 - When the user sends a file, it is saved in the received files directory above. Read it with the Read tool.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inetafrica/open-claudia",
-  "version": "2.2.10",
+  "version": "2.2.11",
   "description": "Your always-on AI coding assistant — Claude Code, Cursor Agent, and OpenAI Codex via Telegram or Kazee Chat",
   "main": "bot.js",
   "bin": {