Skip to content

feat: add telegram heartbeats#51

Closed
simonsickle wants to merge 2 commits intoopenclaw:mainfrom
simonsickle:ssickle/telegram-heartbeats
Closed

feat: add telegram heartbeats#51
simonsickle wants to merge 2 commits intoopenclaw:mainfrom
simonsickle:ssickle/telegram-heartbeats

Conversation

@simonsickle
Copy link

@simonsickle simonsickle commented Dec 24, 2025

If you run without whatsapp, you dont get heartbeats right now. I couldn't run Whatsapp without getting temp banned for being a bot (in defense of WA, I was a bot lol). So now I am running telegram only mode.

To be merged after #50

Allow using a different (cheaper) model for periodic heartbeat runs.
When configured, heartbeat runs will use heartbeatProvider/heartbeatModel
instead of the main provider/model, enabling cost optimization
(e.g., using Haiku for heartbeats while keeping Opus for conversations).

Example config:
  "agent": {
    "provider": "anthropic",
    "model": "claude-opus-4-5",
    "heartbeatProvider": "anthropic",
    "heartbeatModel": "claude-3-5-haiku-20241022",
    "heartbeatMinutes": 30
  }
Enables the same heartbeat functionality that exists for WhatsApp to work
with the Telegram provider. Uses the first allowFrom chat ID as the target
for heartbeat messages.

When agent.heartbeatMinutes is configured, the Telegram provider will:
- Start a periodic timer at the configured interval
- Send HEARTBEAT prompts to the agent
- Deliver non-HEARTBEAT_OK responses to the owner's chat
- Respect heartbeatModel for cost-effective heartbeat runs

This enables proactive features like alarms, email alerts, and calendar
reminders to work via Telegram.
@steipete
Copy link
Contributor

Thanks for the push! I've reworked heartbeat to be it's own module instead of going the duplication route here.

@steipete steipete closed this Dec 26, 2025
@steipete
Copy link
Contributor

heads up, config format changed a bit, see docs/configuration.md and docs/heartbeat.md

@simonsickle simonsickle deleted the ssickle/telegram-heartbeats branch December 31, 2025 02:26
dgarson referenced this pull request in dgarson/clawdbot Feb 2, 2026
feat: integrate the 'ccsdk' as a distinct 'mainRuntime' option in con…
alexprime1889-prog pushed a commit to alexprime1889-prog/moltbot that referenced this pull request Feb 8, 2026
slathrop referenced this pull request in slathrop/openclaw-js Feb 11, 2026
Tasks completed: 2/2
- Task 1: Port commit #28 (Voyage docs + API key) and #51 (input_type)
- Task 2: Port commit #29 (default model update to Opus 4.6)

SUMMARY: .planning/phases/12-memory-qmd-hardening/12-06-SUMMARY.md
dalefrieswthat pushed a commit to dalefrieswthat/openclaw that referenced this pull request Feb 25, 2026
songliu0403-rgb pushed a commit to songliu0403-rgb/openclaw that referenced this pull request Feb 26, 2026
ddupg pushed a commit to ddupg/openclaw that referenced this pull request Feb 27, 2026
- 翻译 docs/concepts/memory.md 全文为中文
- 更新 auto 模式说明以反映 openclaw#49 修复后的行为(自动回退到本地嵌入)

Co-Authored-By: Y1fe1Zh0u <Y1fe1Zh0u@users.noreply.github.com>
Co-Authored-By: Warp <agent@warp.dev>
heatherstew44-maker pushed a commit to heatherstew44-maker/openclaw that referenced this pull request Mar 8, 2026
CoffeeNoir pushed a commit to CoffeeNoir/openclaw that referenced this pull request Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants