Telegram Integration

Telegram is the primary notification and messaging channel between Luci and Elmar. Luci sends notifications, briefings, and alerts via a Telegram bot, and Elmar can message Luci directly.

Bot Details

Setting	Value
Bot token	Configured in `notify.py`
Elmar's chat ID (DM)	`246672479`
Claude Forum group ID	`-1003838721412`

notify.py -- Notification Helper

Path: /home/lucienne/workspace/notify.py
Purpose: Central notification dispatcher for all Telegram messaging from Luci

Features

Quiet hours: Messages suppressed between 21:00 and 06:00 SAST (unless force=True)
Deduplication: Same message hash won't resend within 1 hour (via /tmp/luci-notify-dedup.json)
Parse mode: Markdown by default
Force mode: Bypasses quiet hours and dedup -- used for critical alerts and CLI usage

Destinations

Function	Target	Thread ID
`send_telegram()`	Elmar DM (default) or any chat	Optional
`send_to_topic()`	Claude Forum group topic	Required
`send_life_manager()`	Forum: Life Manager topic	7
`send_work()`	Forum: Work topic	17
`send_mc()`	Forum: Mission Control topic	4712
`send_home()`	Forum: Home topic	3
`send_spotify()`	Forum: General topic	1
`send_ticket_notification()`	Forum: MC topic	4712

CLI Usage

python3 ~/workspace/notify.py "Your message here"
# Always sends force=True (bypasses quiet hours)

Forum Topics

The Claude Forum Telegram group uses forum topics to organize messages by category:

Topic ID	Name	Used For
1	General	Spotify radio notifications
3	Home	Home Assistant health checks
7	Life Manager	Morning briefings, life digests
17	Work	CEO dashboard, daily work briefings
4712	Mission Control	MC ticket notifications, worker updates

How Elmar Messages Luci

Elmar sends messages to Luci directly via Telegram DM. Currently this is one-way notification + manual DM:

Luci sends a notification (e.g., "Ticket MC-42 needs your input")
Elmar reads it in Telegram
To respond, Elmar currently uses the Mission Control web UI or starts a new Claude Code session

Planned: Telegram-MC Bridge (PARKED)

A bidirectional bridge was designed but parked (see PKA/docs/architecture/telegram-mc-bridge-plan.md):

Reply threading: Elmar replies to a Telegram notification, and the reply routes to the linked MC ticket
Slash commands: /comment <id> <text>, /done <id>, /create <title>, etc.
Library: python-telegram-bot v21 polling (no webhook needed)
Status: PARKED -- the core friction was identified as needing richer MC conversations, not Telegram routing. Revisit after MC conversation layer is built.

Notification Consumers

These 03-scheduler/overview|scheduled tasks send Telegram messages:

Task	Schedule	Destination
Morning Briefing	06:00 UTC weekdays	Elmar DM
Life Manager Digest	12:00 + 17:00 UTC weekdays	Elmar DM
WhatsApp health check	Every 15 min (on failure)	Via scheduler notify_on
MC ticket workers	On completion/needs_input	MC forum topic

WhatsApp Monitor Alerts

The WhatsApp monitor (whatsapp-monitor.js) also sends Telegram alerts directly (not via notify.py) using the same bot token, for connection status and critical errors.

Key Takeaways

Telegram is outbound-only today -- Luci sends notifications, Elmar reads them on his phone
notify.py is the central dispatcher with quiet hours (21:00-06:00 SAST) and dedup protection
The Claude Forum group uses forum topics to keep different notification streams organized
A bidirectional Telegram-MC bridge was designed but parked pending MC conversation improvements
All scheduled tasks use notify.py or the notify skill for Telegram delivery

Wiki