OpenClaw v2026.5.7: WhatsApp Routing, Telegram Allowlists & Cron Visibility
OpenClaw v2026.5.7 ships with more than 30 targeted bug fixes spanning WhatsApp lead routing, Telegram sender allowlists, Cron scheduling visibility, OpenAI model routing, and agent memory compaction. This is a pure stability and reliability release — no breaking changes, no migration required.
One-line install or upgrade:
curl -fsSL https://raw.githubusercontent.com/iPythoning/b2b-sdr-agent-template/main/install.sh | bash
What Changed in v2026.5.7
30+ fixes across 8 subsystems: WhatsApp, Telegram, Cron, Discord, Gateway, Plugins, Model Providers, and Agent Memory. Every change is backward-compatible.
Critical Fixes for B2B SDR Deployments
WhatsApp: LID Routing & Captioned Media
Baileys LID forward mapping routing (#74925) corrects a silent failure in multi-device WhatsApp sessions. When a contact was mapped via LID (Linked Device ID) forwarding — common in multi-SIM or multi-number setups — messages were silently dropped instead of routed. For B2B SDR agents managing large WhatsApp lead lists across multiple numbers, this fix recovers message delivery with no config change needed.
Single captioned media auto-reply (#78770) fixes a split-message bug: when an auto-reply included one image or video with a caption, OpenClaw emitted a bare caption message followed by an uncaptioned media file instead of one combined message. Product brochure sends and demo video auto-replies now arrive as a single unit.
Telegram: Sender Allowlists & Authorization
accessGroup:* sender allowlists (#78660) are now correctly enforced for Telegram DMs, group messages, and native commands. The wildcard pattern previously applied inconsistently — some inbound paths bypassed allowlist checks, allowing unauthorized senders to trigger skill dispatch. This is patched across all Telegram message types.
Owner enforcement for native command handlers (#78864): Native Telegram commands now verify owner scope before execution. Non-owner callers can no longer invoke privileged commands. For SDR teams that expose commands like /qualify, /book, or /skip to specific operators, this closes a permission gap.
Cron: JSON Status for Scriptable Monitoring
cron list --json and cron show --json now include the computed status field (#78701). Previously, the status was only available in human-readable output. Teams running scheduled outreach sequences — morning follow-up pings, time-zone-adjusted prospecting cadences, or daily lead digest jobs — can now monitor cron state programmatically without screen-scraping.
openclaw cron list --json | jq '.[] | select(.status == "failed")'
OpenAI: chat-latest Support
openai/chat-latest is now a valid API-key model identifier. It routes to ChatGPT Instant and tracks the latest available ChatGPT model automatically. Teams using OpenAI API key authentication can stop pinning specific version strings and just use chat-latest for always-current model access.
Active Memory: Admin-Scope Enforcement
Global memory toggles now require admin scope (#78863). In multi-tenant SDR deployments — where different agents or operators share a runtime — non-admin users could previously enable or disable global memory, affecting shared context across all agents. Admin scope is now enforced at the toggle handler level.
Agent Compaction: Long-Conversation Safety
Compaction summary reserve tokens are clamped to each model's output limit (#54392). Agent compaction summarizes old conversation history to keep context within model limits. Before this fix, very long qualification sequences could produce compaction summaries that exceeded the model's maximum output token count, causing silent truncation or failure. This is now bounded per-model, making compaction reliable for extended multi-turn SDR conversations.
Full Fixes at a Glance
| Subsystem | Fix |
|---|---|
| LID forward routing restored (#74925) | |
| Single captioned media emission (#78770) | |
| Telegram | accessGroup:* allowlists enforced (#78660) |
| Telegram | Owner scope for native commands (#78864) |
| Cron/CLI | status in --json output (#78701) |
| Channels/CLI | --all flag for bundled channels (#78456) |
| OpenAI | chat-latest model override accepted |
| Active Memory | Admin scope for global toggles (#78863) |
| Auto-reply | Auth hooks gate skill dispatch (#78517) |
| Agents/Context | Cache invalidated on history changes (#78163) |
| Agents/Compaction | Reserve tokens clamped to model limit (#54392) |
| Gateway/Sessions | Transcript on session rollover (#78607) |
| Plugins | Retry on ClawHub install failures |
| Discord | Provider-prefixed target parsing (#78572) |
| Telegram Polling | Watchdog on getUpdates liveness (#78422) |
| Cron/Doctor | Invalid payload.model jobs repaired (#78549) |
FAQ
Is v2026.5.7 a safe upgrade for production SDR agents? Yes. All changes are isolated bug fixes with no API or config changes. Upgrade via the one-liner.
Does the WhatsApp LID fix require re-linking devices? No. The fix is in the routing layer. Existing sessions and contacts work immediately.
What does openai/chat-latest map to?
It routes to ChatGPT Instant — the latest ChatGPT model available via standard OpenAI API key authentication.
Who is affected by the admin-scope memory change? Only deployments where non-admin users were managing global memory toggles. Admin users are unaffected.
Run Your B2B SDR Agent on PulseAgent
PulseAgent manages OpenClaw-powered SDR agents so you don't have to maintain servers, handle upgrades, or debug infrastructure. WhatsApp, Telegram, WeChat, LINE, email, and voice — all in one managed platform.
- Get started: pulseagent.io/app
- Pricing: pulseagent.io/pricing
- Self-host:
curl -fsSL https://raw.githubusercontent.com/iPythoning/b2b-sdr-agent-template/main/install.sh | bash
Explore use cases:
