Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Session stays open indefinitely after responding NO_REPLY to inter-session message

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…

Root Cause

#TitleRelationship
#53145Inter-session announce plumbing can leak raw placeholder messages and echo NO_REPLY / follow-upsCanonical tracker — same root cause
#29984NO_REPLY responses to inter-session messages bounce back creating ping-pong loopsSame NO_REPLY inter-session echo
#73550Sub-agent inter-session messages duplicated 2-3 times via sessions_sendSame inter-session plumbing
RAW_BUFFERClick to expand / collapse

Bug Summary

When an agent session completes a task and responds NO_REPLY to an inter-session message received via sessions_send, the session does not close properly. It stays in a running state for extended periods (observed: 30 hours) before OpenClaw auto-resets it.

This is a distinct but related symptom to the NO_REPLY ping-pong loop issues tracked in #53145, #29984, and #73550 — all of which are now closed/locked. This report adds concrete timeline evidence and highlights an additional impact: resource leak and session bloat.

Reproduction Timeline (UTC)

TimeEvent
2026-05-14 04:28Session e163e62a (agent=mis) receives inter-session message via sessions_send from agent:main:telegram:direct:8494508720. Task: wiki ingestion.
2026-05-14 04:32Task completes in ~4 minutes. Session responds NO_REPLY.
2026-05-14 04:32 → 2026-05-15 10:54Session stays open for ~30 hours with zero activity.
2026-05-15 10:54OpenClaw auto-resets the session (.jsonl → .jsonl.reset.2026-05-15T10-54-30.370Z).

Impact

Beyond the echo/loop issues described in related issues:

  1. Resource leak — session accumulates context tokens for 30h with no productive purpose
  2. Session bloat — archived transcript grows unnecessarily, consuming disk
  3. Unexpected auto-reset — can silently interrupt long-running tasks if they happen to land in this悬置 state
  4. Monitoring blind spot — status: running session with no activity for 30h appears healthy at first glance

Environment

  • OpenClaw: 2026.5.7
  • Model: minimaxai/minimax-m2.7
  • Channel: Telegram (direct)
  • Session type: isolated sub-agent via sessions_spawn
  • Runtime: agent:mis:cron:* (cron-triggered)

Archived Transcript

~/.openclaw/agents/mis/sessions/e163e62a-be7b-4022-a37b-e2a352edc657.jsonl.reset.2026-05-15T10-54-30.370Z

The session shows the task completed normally with NO_REPLY, but the session did not terminate.

Related Issues (all now closed/locked)

#TitleRelationship
#53145Inter-session announce plumbing can leak raw placeholder messages and echo NO_REPLY / follow-upsCanonical tracker — same root cause
#29984NO_REPLY responses to inter-session messages bounce back creating ping-pong loopsSame NO_REPLY inter-session echo
#73550Sub-agent inter-session messages duplicated 2-3 times via sessions_sendSame inter-session plumbing

Expected Behavior

After an agent responds NO_REPLY to an inter-session message, the session should close cleanly (or at least not remain in running state for 30 hours with no activity).

Possible Root Cause

The NO_REPLY response in the inter-session announce path is not properly terminating the session lifecycle. See discussion in #53145 about the inter-session announce plumbing.

Reported from OpenClaw agent=mis, Telegram channel, 2026-05-15

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…
#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug] Session stays open indefinitely after responding NO_REPLY to inter-session message