Summary

• prefer channel/agent binding account IDs when the message action omits accountId
• keep explicit accountId values as highest priority
• add tests for binding precedence and explicit override behavior

Why

Sub-agents can inherit the requester account context, which caused outbound messages to route through the wrong bot in multi-account setups. This change makes account selection align with routing bindings for the active agent.

Testing

• bash /Users/newdldewdl/.openclaw/workspace/skills/openclaw-autonomous-contributor/scripts/quality_gate.sh /Users/newdldewdl/.openclaw/workspace/memory/openclaw-contrib/worktrees/issue-26975

AI-assisted: yes

Fixes #26975

Greptile Summary

Adds agent-bound account ID resolution to the message action runner, ensuring sub-agents use their configured account bindings instead of inheriting the requester's account context.

• Introduced resolveAgentBoundAccountId helper that looks up agent-specific account bindings from channel configuration
• Modified account resolution to use three-tier precedence: explicit accountId param → agent binding → defaultAccountId
• Added comprehensive test coverage for binding precedence and explicit override behavior

The implementation correctly prevents wrong-bot routing in multi-account setups by respecting agent-to-account bindings defined in the configuration.

Confidence Score: 5/5

• Safe to merge with no issues found
• The changes are well-structured, thoroughly tested, and maintain backward compatibility. The new account resolution logic correctly implements the stated precedence (explicit > agent-bound > default) and all edge cases are properly handled with optional chaining and type safety.
• No files require special attention

_{Last reviewed commit: 5acd1d6}