openclaw - 💡(How to fix) Fix [Bug]: Regression in v2026.4.5: non-main agents in Telegram multi-agent setup stop replying unless OpenViking contextEngine is set to legacy [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62324Fetched 2026-04-08 03:05:59
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Participants
Timeline (top)
commented ×1labeled ×1

In OpenClaw v2026.4.5, non-main agents in a Telegram multi-agent setup stop sending replies, and they start working again when OpenViking contextEngine is switched back to legacy.

Root Cause

Telegram is enabled and working. channels.telegram.defaultAccount is set to main. The issue does not appear to be a basic Telegram account-routing failure, because non-main agents already had valid Telegram group sessions visible in openclaw status. Switching only OpenViking contextEngine back to legacy restored replies.

Fix Action

Fix / Workaround

This affects Telegram multi-agent behaviour for non-main agents on v2026.4.5. Observed consequence: the setup that worked on v2026.4.2 no longer behaves correctly unless OpenViking contextEngine is forced back to legacy. Current workaround: use contextEngine=legacy or stay on v2026.4.2.

Code Example

Observed version matrix:

• v2026.4.2 ✅ works
• v2026.4.5 + newer context engine ❌ non-main agents do not reply
• v2026.4.5 + contextEngine=legacy ✅ works again

Additional observed evidence:

• channels.telegram.defaultAccount = "main"
• openclaw status showed active Telegram group sessions for non-main agents such as Tim, Sam, and Walt
This suggests the regression is not a simple Telegram routing/account-resolution problem
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

In OpenClaw v2026.4.5, non-main agents in a Telegram multi-agent setup stop sending replies, and they start working again when OpenViking contextEngine is switched back to legacy.

Steps to reproduce

  1. Run the same Telegram multi-agent setup on OpenClaw v2026.4.5.
  2. Keep OpenViking on the newer contextEngine path, not legacy.
  3. Send a message that should be handled by a non-main agent in the Telegram group/topic setup.
  4. Observe that the non-main agent does not send a reply.
  5. Switch OpenViking contextEngine to legacy.
  6. Repeat the same test.
  7. Observe that the non-main agent replies normally again.

Expected behavior

Non-main agents should reply normally in the Telegram multi-agent setup, as they do on v2026.4.2 and on v2026.4.5 when contextEngine=legacy.

Actual behavior

On v2026.4.5 with the newer OpenViking context-engine path, non-main agents do not reply. After switching contextEngine to legacy, the same agents start responding again.

OpenClaw version

v2026.4.5

Operating system

Ubuntu Linux

Install method

npm

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

Telegram is enabled and working. channels.telegram.defaultAccount is set to main. The issue does not appear to be a basic Telegram account-routing failure, because non-main agents already had valid Telegram group sessions visible in openclaw status. Switching only OpenViking contextEngine back to legacy restored replies.

Logs, screenshots, and evidence

Observed version matrix:

• v2026.4.2 ✅ works
• v2026.4.5 + newer context engine ❌ non-main agents do not reply
• v2026.4.5 + contextEngine=legacy ✅ works again

Additional observed evidence:

• channels.telegram.defaultAccount = "main"
• openclaw status showed active Telegram group sessions for non-main agents such as Tim, Sam, and Walt
• This suggests the regression is not a simple Telegram routing/account-resolution problem

Impact and severity

This affects Telegram multi-agent behaviour for non-main agents on v2026.4.5. Observed consequence: the setup that worked on v2026.4.2 no longer behaves correctly unless OpenViking contextEngine is forced back to legacy. Current workaround: use contextEngine=legacy or stay on v2026.4.2.

Additional information

Based on the observed version matrix, this looks like a regression tied to the newer OpenViking context-engine path in v2026.4.5.

extent analysis

TL;DR

Switching OpenViking contextEngine to legacy resolves the issue of non-main agents not sending replies in Telegram multi-agent setups on OpenClaw v2026.4.5.

Guidance

  • Verify that the issue is indeed related to the newer OpenViking context-engine path by testing with the legacy context engine.
  • Check the OpenClaw and OpenViking documentation for any known issues or configuration recommendations related to the context engine and Telegram integration.
  • Test the setup with different versions of OpenClaw and OpenViking to confirm the regression and identify potential workarounds.
  • Consider reporting the issue to the OpenClaw or OpenViking development teams for further investigation and potential fixes.

Example

No specific code example is provided as the issue seems to be related to configuration and versioning rather than code-level changes.

Notes

The root cause of the issue appears to be related to the newer OpenViking context-engine path in OpenClaw v2026.4.5, but the exact cause is unclear. The provided workaround of using the legacy context engine may not be a permanent solution and may have other implications.

Recommendation

Apply the workaround of using contextEngine=legacy until a permanent fix is available, as it has been observed to resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Non-main agents should reply normally in the Telegram multi-agent setup, as they do on v2026.4.2 and on v2026.4.5 when contextEngine=legacy.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING