Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

When executing long-running tasks (15-30 minutes) via custom tools, the task completes successfully but the agent never sends the result back to the user. The user must explicitly ask "why didn't you reply?" to get the result.

Steps to reproduce

1. User sends DM: "Run long database query" (takes ~17 minutes)
2. Agent calls custom tool → exec(..., background: true) → process(poll, timeout=1800000)
3. Task completes successfully at 09:58:51 ✓
4. Agent receives full result via process ✓
5. Agent does NOT send reply to user ❌
6. User waits 9 minutes, then asks "where's the result?"
7. Only then does agent send the result

Expected behavior

After process(poll) returns with the completed task result, the agent should automatically:

1. Parse the output
2. Format a user-friendly response
3. Send it to the originating DM/channel

Actual behavior

• Agent receives the result but doesn't send anything
• Session looks "frozen" from user perspective
• User cannot tell if task succeeded/failed
• Severely degraded UX

OpenClaw version

2026.6.9

Operating system

macOS (Darwin 25.3.0, arm64)

Install method

package manager

Model

Claude Opus 4.6

Provider / routing chain

dingding -> openclaw -> extentions

Additional provider/model setup details

Configuration (sanitized)

{
  "channels": {
    "dingtalk-connector": {
      "accounts": {
        "my_account": {
          "asyncMode": false,
          "separateSessionByConversation": true
        }
      }
    }
  },
  "agents": {
    "list": [{
      "tools": {
        "profile": "coding",
        "alsoAllow": ["custom_tool"]
      }
    }]
  }
}

Workaround

Manually call message(action: 'send', ...) after tool completes, but agent doesn't do this automatically.

Questions

1. Is there a session timeout for long-poll

Logs, screenshots, and evidence

## Timeline


09:41:29 Task started, agent: "查询已经开始执行..."
09:43:38 Agent: "预计还需 18-28 分钟..."
09:58:51 Task completed (exitCode 0, full output received)
         [NO REPLY SENT]
10:07:00 User: "为什么不通知我？"
10:07:xx Agent finally shows result


**9-minute gap between completion and user having to ask**

Impact and severity

• Severity: High (broken UX for any long task)
• Frequency: 100% for tasks >15 minutes
• Regression: User reports v2026.6.8 was stable

Additional information

Suspected Root Cause

Possibly related to v2026.6.9 changes:

• PR fix(reply): deliver final reply when queued follow-up claims session; scope dedupe to routed thread #90943: "fix(reply): deliver final reply when queued follow-up claims session"
• PR fix(agents): replace prose terminal classifiers #93228: "fix(agents): replace prose terminal classifiers"

Hypothesis:

• Session context or reply-routing gets lost during long process(poll) waits
• dingtalk-connector conversation context may expire after 15-20 minutes
• Agent receives toolResult but reply delivery mechanism fails silently