Why do OpenClaw tools not execute when triggered from Telegram or Slack on v2026.4.14?

A regression in v2026.4.14 breaks the chat-originated execution path. The agent responds conversationally but tool dispatch from channel messages fails silently. CLI tool-calling still works because it bypasses the channel session wake mechanism.

How to fix OpenClaw Telegram tools not working after update to 2026.4.14?

The issue is tracked in GitHub issue #66679. As a workaround, try downgrading to v2026.4.12 or using CLI-based tool execution. The development team is investigating the chat-triggered tool dispatch regression.

Does OpenClaw Slack Socket Mode work on version 2026.4.14?

Partially. Slack Socket Mode connects successfully but inbound events (app_mention) may not be received. This is a known issue tracked in GitHub #66989 affecting the latest release.

Is this OpenClaw tool execution bug the same as the v2026.3.2 tool dispatching regression?

No. The v2026.3.2 regression (issue #41462) disabled tools by default. The v2026.4.14 bug is different: tools appear enabled and work from CLI, but the chat-to-tool execution path specifically fails.

Which OpenClaw channels are affected by the tool execution failure?

Telegram and Slack are confirmed affected. Discord may also be impacted. The bug appears to affect the shared chat-originated execution path rather than any single channel.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-4-14-chat-tool-execution-failure

⚠ IssueWide OpenToolLive

OpenClaw v2026.4.14 Chat-Triggered Tools Never Execute: Telegram and Slack Respond But Do Not Act

On OpenClaw 2026.4.14, Telegram and Slack channels respond conversationally to requests but tool/action execution from chat never fires. CLI tool-calling works fine, indicating a regression specific to the chat-originated execution path and session wake from queued events.

Product Idea from this Signal

A CLI tool that validates an OpenClaw upgrade against your specific provider, channel, and service configuration before applying it

115 ▲

Every OpenClaw point release ships regressions that silently break production setups. v2026.4.14 alone introduced Cloudflare 403 blocks on Codex providers, chat-triggered tool dispatch failures in Telegram and Slack, installer crashes, and cron job deletion during updates. The pattern repeats across every version. This CLI reads your running OpenClaw config (active providers, channel bindings, cron jobs, installed skills), downloads the target release, and runs a provider header check, channel dispatch smoke test, service lifecycle simulation, and cron persistence validation against the new version. It outputs a pass/fail per component with specific issue references so you know exactly what will break before you upgrade.

CLIDEVTOOLTESTINGRELIABILITYOPEN-SOURCE

UnderservedView Opportunity →