openclaw - 💡(How to fix) Fix Subagent deliveryContext loses to/threadId/accountId when spawned from group topics [1 participants]

Fix Plan

To fix the issue, we need to modify the sessions_spawn function to inherit the full delivery context from the parent session.

Here are the steps:

• Update the sessions_spawn function to include the to, accountId, and threadId fields in the subagent's deliveryContext.
• Ensure that the deliveryContext is properly passed to the subagent.

Example code snippet:

def sessions_spawn(parent_session, subagent_config):
    # ...
    subagent_delivery_context = parent_session.deliveryContext.copy()
    subagent_delivery_context['channel'] = 'telegram'
    subagent_config['deliveryContext'] = subagent_delivery_context
    # ...

Alternatively, you can also use the following code snippet:

subagent_delivery_context = {**parent_session.deliveryContext, 'channel': 'telegram'}

This will create a new dictionary with all the key-value pairs from the parent session's deliveryContext and override the channel field with 'telegram'.

Verification

To verify that the fix worked, follow these steps:

• Spawn a subagent from a group topic session using sessions_spawn.
• Check the subagent's deliveryContext to ensure it includes the to, accountId, and threadId fields.
• Wait for the subagent to complete and verify that the completion announce is delivered to the topic.

Extra Tips

• Make sure to test the fix in different environments and scenarios to ensure it works as expected.
• Consider adding logging or monitoring to track the deliveryContext of subagents and detect any potential issues.