openclaw - 💡(How to fix) Fix ACP session replies delivered as 'Background task done' without content after upgrade to 2026.4.2 [1 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#60872Fetched 2026-04-08 02:46:16
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0

After upgrading from OpenClaw 2026.3.28 to 2026.4.2, ACP sessions (via acpx) stop delivering reply text to Telegram. Instead of the agent's actual response, Telegram only shows:

Background task done: oscar-1775307657 (run 10504).

The ACP session spawns and the agent starts successfully (startup announce message is delivered), but subsequent user messages result in empty "background task done" notifications with no content.

Downgrading back to 2026.3.28 immediately resolves the issue — replies are delivered normally.

Error Message

error=-32002: Resource not found: <resumeSessionId> error=429 rate_limit_error But even when the embedded runner doesn't error, the "Background task done" message appears without content.

Root Cause

After upgrading from OpenClaw 2026.3.28 to 2026.4.2, ACP sessions (via acpx) stop delivering reply text to Telegram. Instead of the agent's actual response, Telegram only shows:

Background task done: oscar-1775307657 (run 10504).

The ACP session spawns and the agent starts successfully (startup announce message is delivered), but subsequent user messages result in empty "background task done" notifications with no content.

Downgrading back to 2026.3.28 immediately resolves the issue — replies are delivered normally.

Fix Action

Workaround

Downgrade to 2026.3.28:

npm install -g [email protected]
# Restore local acpx extension (0.3.1) if previously backed up
systemctl --user restart openclaw-gateway

Code Example

Background task done: oscar-1775307657 (run 10504).

---

{
  "id": "oscar",
  "runtime": {
    "type": "acp",
    "acp": {
      "agent": "claude",
      "backend": "acpx",
      "mode": "persistent",
      "cwd": "/home/jack/Openclaw-Oscar"
    }
  },
  "model": {
    "primary": "kimi-coding/k2p5",
    "fallbacks": ["anthropic/claude-sonnet-4-6"]
  }
}

---

[plugins] acpx ensureSession repairing dead named session by resuming backend session:
  session=agent:claude:acp:58702d6c-... status=dead summary=queue owner unavailable

[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner:
  error=-32002: Resource not found: <resumeSessionId>

---

[gateway] acp startup identity reconcile (renderer=v1): checked=209 resolved=0 failed=209

---

[agent/embedded] embedded run agent end: isError=true model=k2p5 provider=kimi-coding
  error=429 rate_limit_error

---

npm install -g openclaw@2026.3.28
# Restore local acpx extension (0.3.1) if previously backed up
systemctl --user restart openclaw-gateway
RAW_BUFFERClick to expand / collapse

Description

After upgrading from OpenClaw 2026.3.28 to 2026.4.2, ACP sessions (via acpx) stop delivering reply text to Telegram. Instead of the agent's actual response, Telegram only shows:

Background task done: oscar-1775307657 (run 10504).

The ACP session spawns and the agent starts successfully (startup announce message is delivered), but subsequent user messages result in empty "background task done" notifications with no content.

Downgrading back to 2026.3.28 immediately resolves the issue — replies are delivered normally.

Environment

  • OS: Ubuntu 24.04 (Linux 6.8.0-106-generic)
  • Node: v22.22.0
  • OpenClaw: 2026.4.2 (d74a122) — regression vs 2026.3.28 (f9b1079)
  • acpx: Tested with both bundled 0.4.0 and local extension 0.3.1 — same behavior
  • Channel: Telegram
  • ACP backend: acpx, mode: persistent
  • ACP agent: claude (Claude Code 2.1.92)

Agent config (simplified)

{
  "id": "oscar",
  "runtime": {
    "type": "acp",
    "acp": {
      "agent": "claude",
      "backend": "acpx",
      "mode": "persistent",
      "cwd": "/home/jack/Openclaw-Oscar"
    }
  },
  "model": {
    "primary": "kimi-coding/k2p5",
    "fallbacks": ["anthropic/claude-sonnet-4-6"]
  }
}

Reproduction steps

  1. Upgrade from 2026.3.28 to 2026.4.2 (npm update -g openclaw)
  2. Restart gateway
  3. Send a message to the ACP-backed agent via Telegram
  4. Observe: agent startup announce works, but user message replies only show "Background task done: ... (run XXXX)."

Observed behavior in logs

On every user message, the ACP session repair loop fires:

[plugins] acpx ensureSession repairing dead named session by resuming backend session:
  session=agent:claude:acp:58702d6c-... status=dead summary=queue owner unavailable

[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner:
  error=-32002: Resource not found: <resumeSessionId>

The new dead-session repair mechanism in 2026.4.2 (ACPX changelog entries #58669, related fix for stale session IDs) attempts to resume with resumeSessionId, but the backend session no longer exists (-32002: Resource not found). After the repair loop, no reply text is delivered — only the task completion notification.

Startup identity reconcile always fails:

[gateway] acp startup identity reconcile (renderer=v1): checked=209 resolved=0 failed=209

All 209 existing ACP sessions fail reconciliation on every restart.

When ACP dispatch fails entirely, fallback to embedded runner also fails:

[agent/embedded] embedded run agent end: isError=true model=k2p5 provider=kimi-coding
  error=429 rate_limit_error

But even when the embedded runner doesn't error, the "Background task done" message appears without content.

Suspected cause

The new unified background task control plane introduced in 2026.3.31/2026.4.2 (changelog: "turn tasks into a real shared background-run control plane") appears to wrap ACP runs as background tasks. The task completion notification is sent to Telegram, but the actual agent reply text is not being relayed through the task delivery path.

Workaround

Downgrade to 2026.3.28:

npm install -g [email protected]
# Restore local acpx extension (0.3.1) if previously backed up
systemctl --user restart openclaw-gateway

extent analysis

TL;DR

Downgrade OpenClaw to version 2026.3.28 to resolve the issue with ACP sessions not delivering reply text to Telegram.

Guidance

  • The new unified background task control plane in OpenClaw 2026.4.2 may be causing the issue by wrapping ACP runs as background tasks and not relaying the actual agent reply text.
  • The ACP session repair loop firing on every user message and the startup identity reconcile always failing may be related to the problem.
  • To verify the issue, check the logs for the "Background task done" notification and the absence of the agent's reply text.
  • Consider testing with a different ACP backend or agent to isolate the issue.

Example

No code snippet is provided as the issue is related to a specific version of OpenClaw and its interaction with the ACP backend and agent.

Notes

The workaround of downgrading to 2026.3.28 is confirmed to resolve the issue, but it may not be a long-term solution. The root cause of the problem is likely related to the changes introduced in OpenClaw 2026.4.2, and further investigation is needed to determine a permanent fix.

Recommendation

Apply the workaround by downgrading to OpenClaw 2026.3.28, as it is a confirmed solution to the issue. This will allow for normal functioning of ACP sessions and delivery of reply text to Telegram until a permanent fix is available.

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…

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 ACP session replies delivered as 'Background task done' without content after upgrade to 2026.4.2 [1 participants]