Version

• OpenClaw 2026.4.9 (0512059)

Summary

When sessions_send is called from a visible webchat-backed session to an internal session, it does not behave like a strict internal-only handoff. The target reply can surface into visible webchat, and the target session can inherit webchat delivery context.

What seems to be happening

Current behavior appears to be:

• the target run starts with deliver: false
• then a follow-up agent-to-agent announce flow still runs
• the tool result reports delivery.mode: announce
• the inter-session path uses internal webchat, which can cause fresh internal targets to pick up webchat delivery context

Expected behavior

• sessions_send to an internal session should keep execution internal
• the reply should remain internal
• the caller should be the only session deciding what becomes user-visible
• the target session should not inherit visible webchat binding just because the source was visible

Actual behavior

• raw internal replies can appear in visible webchat
• target sessions can become associated with webchat delivery context, for example:
  • channel: webchat
  • deliveryContext.channel: webchat
• tool results consistently show delivery.mode: announce

Steps to reproduce

1. Start from a visible webchat-backed session.
2. Call sessions_send to an internal session with a message such as:
   Reply with exactly: TEST_OK
3. Observe the result.

Observed result

• TEST_OK appears in visible webchat
• the target session becomes webchat-associated
• the tool result reports delivery.mode: announce

Expected result

• the reply stays internal
• no raw internal text reaches the visible user thread
• the destination session remains internal

Why this matters

This makes sessions_send unsafe as a strict internal delegation primitive from visible user-facing sessions.

Temporary workaround

• avoid sessions_send from visible webchat when strict internal boundaries are required

Additional note

If this behavior is intended, the docs should explicitly describe sessions_send as an announce-capable handoff rather than an internal-only RPC-style primitive.