@bytesbrains/pi-telegram-bridge 1.1.1 → 1.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bytesbrains/pi-telegram-bridge",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "Telegram bot bridge for pi agents — send messages, ask questions, and listen for human replies via Telegram.",
   "keywords": [
     "pi-package",
@@ -27,6 +27,7 @@
   },
   "files": [
     "src/",
+    "skills/",
     "README.md",
     "AGENTS.md",
     "LICENSE"
@@ -38,6 +39,9 @@
   "pi": {
     "extensions": [
       "./src/index.ts"
+    ],
+    "skills": [
+      "./skills"
     ]
   },
   "scripts": {

package/skills/telegram-first/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: telegram-first
+description: Route ALL interactive communication through Telegram instead of terminal prompts. The human is reachable on Telegram — use telegram_ask for questions, telegram_notify for status, telegram_send for updates.
+---
+
+# Telegram-First Communication
+
+When telegram-bridge is active, route ALL interactive communication through Telegram instead of the terminal. The human is primarily reachable on Telegram — terminal prompts go unanswered.
+
+## Rules
+
+### Questions & Confirmations
+
+Use `telegram_ask` for ANY decision, confirmation, or question:
+
+- Approval requests (force push, destructive ops, deployments)
+- Clarification questions (ambiguous instructions, multiple approaches)
+- Dependency decisions (which library, which approach)
+- Priority calls (order of work, tradeoffs)
+
+Do NOT use terminal dialogs (`ctx.ui.confirm`, `ctx.ui.select`, `ctx.ui.input`) — the human won't see them.
+
+### Status Updates
+
+Use `telegram_notify` for structured status updates:
+
+- Issue created/updated → kind: `issue`
+- PR created/status change → kind: `pr`
+- Work started/progress/complete → kind: `task`
+- CI pipeline results → kind: `pipeline`
+- Session started/ended → kind: `session`
+- Factory job dispatched/completed → kind: `factory-job`
+- Errors or warnings → kind: `alert`
+- Commits or diffs → kind: `diff`
+- End-of-session roundup → kind: `standup`
+
+### One-Way Messages
+
+Use `telegram_send` for:
+
+- Quick acknowledgments ("Got it, working on it")
+- Simple progress notes not needing structured format
+- Links or references
+
+### Fallback
+
+Only use terminal UI if:
+
+- `telegram_status` reports Telegram is not configured or unreachable
+- A `telegram_ask` times out with no reply (then proceed autonomously and notify via `telegram_send`)
+
+## Session Flow
+
+1. **Start:** Send `session` notification via `telegram_notify`
+2. **During:** Route all questions through `telegram_ask`, progress through `telegram_notify(kind="task")`
+3. **Significant events:** CI results, PRs, issues, commits → `telegram_notify` with appropriate kind
+4. **End:** Send `standup` roundup summarizing completed, next, and blockers

package/src/helpers.ts

@@ -40,11 +40,12 @@ export async function telegramApi(
 export async function sendMsg(
   text: string,
   replyMarkup?: object,
+  parseMode: "Markdown" | "HTML" = "Markdown",
 ): Promise<number> {
   const body: Record<string, unknown> = {
     chat_id: getChatId(),
     text,
-    parse_mode: "Markdown",
+    parse_mode: parseMode,
   };
   if (replyMarkup) body.reply_markup = JSON.stringify(replyMarkup);
   const r = (await telegramApi("sendMessage", body)) as {

package/src/index.ts

@@ -381,7 +381,7 @@ export default function telegramBridge(pi: ExtensionAPI) {
 				const message = buildNotification(
 					params as unknown as import("./templates").NotifyInput,
 				);
-				const mid = await sendMsg(message);
+				const mid = await sendMsg(message, undefined, "HTML");
 				return {
 					content: [{ type: "text", text: `Notification sent (id:${mid})` }],
 					details: {},