fix: propagate delivery target (to) for subagent topic routing #1241
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a subagent is spawned from a Telegram forum topic, the announce result was being sent to #general instead of the original topic. The issue was that the 'to' field (containing the full target path like 'telegram:group:-123:topic:456') was not being propagated through the tool chain: - sessions-spawn-tool.ts: Added agentTo param, pass to DeliveryContext - clawdbot-tools.ts: Added agentTo param, forward to spawn tool - pi-tools.ts: Added messageTo param, forward to clawdbot-tools - pi-embedded-runner: Added messageTo to params and attempt - agent-runner-*.ts: Pass OriginatingTo/To from sessionCtx - followup-runner.ts: Pass originatingTo from queued run This ensures subagent results are announced back to the correct Telegram topic (or other threaded destination) where the spawn was initiated.
|
I'm running into a similar slack problem where i speak to clawdbot in a thread, and the reply comes back to the main chat. Would this also solve that? |
steipete
added a commit
that referenced
this pull request
Jan 20, 2026
Thanks @gnarco. Co-authored-by: gnarco <[email protected]>
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When a subagent is spawned from a Telegram forum topic, the announce result was being sent to #general instead of the original topic.
Root Cause
The
tofield (containing the full target path liketelegram:group:-123:topic:456) was not being propagated through the tool chain. TheDeliveryContexthas atofield, but it was never populated when creating therequesterOrigininsessions-spawn-tool.ts.Solution
Propagate the
tofield through the entire chain:agentToparam, pass tonormalizeDeliveryContextagentToparam, forward to spawn toolmessageToparam, forward to clawdbot-toolsmessageTotoEmbeddedRunAttemptParamsmessageTotoRunEmbeddedPiAgentParamsmessageToto attemptmessageTotocreateClawdbotCodingToolsOriginatingTofromsessionCtxOriginatingTofromsessionCtxoriginatingTofrom queued runTesting