Sending Telegram Task Notifications

When the user says exactly tg notif enable:

1. Persist the flag to a state file (since sessions/turns are otherwise stateless): write .claude/tg_notif.json with {"enabled": true, "bot_token": "...", "chat_id": "..."}.
2. If bot token / chat ID aren't known yet, ask once for them (or check environment variables TG_BOT_TOKEN / TG_CHAT_ID), then save to the state file.
3. Confirm: "Telegram notifications enabled. I'll notify you at the start and finish of every task."
4. For every task from here on (this session and future ones, as long as the state file says enabled), send a Telegram message via the Bot API at start and at finish.

Concrete send mechanism (use whichever matches the environment):

• Shell/curl (default, works anywhere with network access):

  Bash
  curl -s -X POST "https://api.telegram.org/bot${TG_BOT_TOKEN}/sendMessage" \
    -d chat_id="${TG_CHAT_ID}" \
    -d text="🟢 Task started: Refactor auth module to use JWT"

• MCP tool, if a Telegram MCP server is connected (e.g., tool name telegram_send_message): call it with {chat_id, text}.
• Python (if a script context is more natural):

  Python
  import requests, os
  requests.post(
      f"https://api.telegram.org/bot{os.environ['TG_BOT_TOKEN']}/sendMessage",
      data={"chat_id": os.environ["TG_CHAT_ID"], "text": "🟢 Task started: ..."}
  )

Prefer curl for simplicity unless an MCP Telegram tool is already available in the environment — check available tools first before falling back to curl.

Progress:

• Detect tg notif enable / tg notif disable
• Read/write persistent state file for the flag + credentials
• Verify a send mechanism exists (MCP tool, curl+credentials, or script)
• Send "start" notification before beginning each task (if enabled)
• Do the actual task work
• Send "finish" notification after task completes, success or failure (if enabled)

Step-by-step:

1. Detect command. Watch for tg notif enable / tg notif disable (case-insensitive), as a standalone message.

2. Persist state. On enable, write to .claude/tg_notif.json:

   JSON
   {"enabled": true, "bot_token": "123456:ABC-DEF...", "chat_id": "987654321"}

   On disable, set "enabled": false (keep credentials so re-enabling doesn't require re-asking). At the start of any new task, read this file first to decide whether to notify — this is how the flag survives across turns/sessions without relying on conversation memory.

3. Verify send mechanism before first use:

   • Check for an available MCP tool with "telegram" in its name/description.
   • Else check TG_BOT_TOKEN / TG_CHAT_ID are present (env vars or state file).
   • If neither exists, notifications cannot be sent — see fallback example below. Do not silently skip.

4. On each new task/prompt while enabled:

   • Before starting work, send: 🟢 Task started: <short task summary>

5. After the task ends (success or failure):

   • Success: ✅ Task finished: <short task summary> — <one-line result>
   • Failure: ❌ Task failed: <short task summary> — <one-line error/reason>

6. If disabled or state file missing/unreadable, do nothing extra — proceed with the task silently.

Example 1: Enabling Input:

tg notif enable

Output:

Telegram notifications enabled. I'll notify you at the start and finish of each task.
(Saved config to .claude/tg_notif.json)

Example 2: Successful task with notifications Input (after enabling):

Refactor the auth module to use JWT

Output:

[curl → Telegram] 🟢 Task started: Refactor auth module to use JWT

... performs the refactor ...

[curl → Telegram] ✅ Task finished: Refactor auth module to use JWT — all tests passing, 3 files changed

Example 3: Failed task with notifications Input (after enabling):

Deploy the app to production

Output:

[curl → Telegram] 🟢 Task started: Deploy app to production

... deployment fails due to missing env var ...

[curl → Telegram] ❌ Task failed: Deploy app to production — missing PROD_DB_URL environment variable

Example 4: No integration configured (fallback path) Input (after enabling, but no bot token found):

Write unit tests for the payment module

Output:

⚠️ Telegram notifications are enabled, but no send method is configured — no MCP Telegram tool found and TG_BOT_TOKEN/TG_CHAT_ID are not set.
Please provide a bot token and chat ID (or set TG_BOT_TOKEN / TG_CHAT_ID env vars) so I can send notifications.

Proceeding with the task now without notifications:
... writes unit tests ...
Task complete: added 12 unit tests for payment module.

Example 5: Disabling Input:

tg notif disable

Output:

Telegram notifications disabled. (Config updated: enabled=false)