openclaw - 💡(How to fix) Fix ACP subagent Telegram delivery not working — delivery.channel/to not propagated to child session [1 participants]

Describe the bug

When spawning an ACP subagent via sessions_spawn with runtime: "acp" and delivery configured, the delivery parameters are not being propagated into the child session context. Subagents complete successfully but results are not delivered to the configured channel.

To Reproduce

{
  "action": "sessions_spawn",
  "runtime": "acp",
  "task": "echo test",
  "delivery": {
    "mode": "announce",
    "channel": "telegram",
    "to": "<telegram_user_id>"
  }
}

Expected: result appears on Telegram. Actual: subagent runs (accepted, completes), no Telegram message received.

Environment

• OpenClaw 2026.3.24
• ACP runtime (acpx) via sessions_spawn runtime: "acp"
• Telegram channel configured and working for direct messages
• agents.defaults.maxConcurrent: 2
• agents.defaults.subagents.maxConcurrent: 2
• acpx plugin loaded and functional for execution

What was verified

• Wrapper only unsets OPENAI_API_KEY for billing — does not affect delivery routing
• ACP subagent execution itself works (subagent accepts and runs tasks)
• Telegram bot token valid, Telegram channel enabled
• delivery fields correctly passed in sessions_spawn call from parent session
• Multiple concurrent subagents spawn successfully

Likely root cause

The delivery config from sessions_spawn is not being passed into the child session's context by the OpenClaw ACP runtime. The child session runs with its own isolated context that does not include the parent's delivery configuration. This is an upstream OpenClaw code issue, not a config or wrapper problem.

Expected behavior

ACP subagent results should be delivered to the channel specified in delivery when the subagent completes.