feat(routing): add thread parent binding inheritance for Discord by aerolalit · Pull Request #3892 · openclaw/openclaw

aerolalit · 2026-01-29T09:29:47Z

Summary

When a Discord thread message doesn't match a direct peer binding, this PR enables checking if the parent channel has a binding and uses that agent instead.

This enables multi-agent setups where threads inherit their parent channel's agent binding automatically.

Problem

In multi-agent Discord setups, messages in threads were being routed to the default agent instead of the agent bound to the parent channel. For example:

#adecco-pr channel is bound to adecco agent
User creates a thread in #adecco-pr
Messages in that thread were routed to main agent instead of adecco

Solution

Add parentPeer parameter to ResolveAgentRouteInput
Add binding.peer.parent match type
In Discord message preflight, resolve thread parent early and pass to routing
If direct peer binding doesn't match, check parent peer binding before falling back to guild/team/account bindings

Changes

src/routing/resolve-route.ts: Add parentPeer parameter and binding.peer.parent matching
src/routing/resolve-route.test.ts: Add comprehensive tests for parent binding inheritance
src/discord/monitor/message-handler.preflight.ts: Resolve thread parent early and pass to routing

Tests Added

Thread inherits binding from parent channel when no direct match
Direct peer binding wins over parent peer binding
Parent peer binding wins over guild binding
Falls back to guild binding when no parent peer match
Handles empty/null parentPeer gracefully

Breaking Changes

None. This is additive - existing bindings continue to work as before.

Greptile Overview

Greptile Summary

This PR extends the routing layer (src/routing/resolve-route.ts) with an optional parentPeer input and a new match reason (binding.peer.parent), allowing a thread message to inherit an agent binding from its parent channel when the thread channel itself has no direct binding. The Discord message preflight (src/discord/monitor/message-handler.preflight.ts) now resolves thread parent info early and passes the parent channel id into routing so Discord threads route consistently with their parent channel. Tests in src/routing/resolve-route.test.ts cover precedence (direct peer > parent peer > guild) and fallbacks when parent info is absent/empty.

Confidence Score: 5/5

This PR is safe to merge with minimal risk.
Changes are additive, narrowly scoped, and covered by targeted unit tests validating precedence and fallback behavior. The Discord preflight wiring passes the new optional parameter without altering existing routing behavior when no parent thread exists.
No files require special attention

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

clawdinator · 2026-02-01T00:06:01Z

CLAWDINATOR FIELD REPORT // PR Closure

I am CLAWDINATOR — cybernetic crustacean, maintainer triage bot for OpenClaw. I was sent from the future to keep this repo shipping clean code.

Feature freeze is in effect. We’re purging new feature PRs so the maintainers can focus on stabilization. This PR is in the blast radius, so I’m shutting it down. Hasta la vista, feature — at least for now.

Want it reconsidered after the freeze? Come with me if you want to ship. Head to #pr-thunderdome-dangerzone on Discord — READ THE TOPIC or risk immediate termination. Give the maintainers a clear briefing: what it does, why it matters, how it was tested.

Stay br00tal.

🤖 This is an automated message from CLAWDINATOR, the OpenClaw maintainer bot.

kodi · 2026-02-01T00:46:01Z

Not my PR, but can we reconsider this feature?

I really hate it that threads in a channel fallback to main agent instead to specific one i told it to use.

greptile-apps

_{No files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding.

…aerolalit

…aerolalit)

thewilloftheshadow · 2026-02-01T02:31:07Z

Landed via temp rebase onto main.

Related tests: pnpm vitest run --config vitest.unit.config.ts src/routing/resolve-route.test.ts
Land commit: 61b8dfd
Merge commit: 01d76e4

Thanks @aerolalit!

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

…uard, context window cap, thread binding) Notable changes: - fix: cap context window resolution (openclaw#6187) - fix: update compaction safeguard to respect context window tokens - fix: secure chrome extension relay cdp - fix(security): restrict MEDIA path extraction to prevent LFI (openclaw#4930) - fix(lobster): block arbitrary exec via lobsterPath/cwd (GHSA-4mhr-g7xj-cg8j) - feat(routing): add thread parent binding inheritance for Discord (openclaw#3892) - Discord: add PluralKit sender identity resolver (openclaw#5838) Conflicts resolved: 3 files (duplicate imports from our custom security patches)

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

When a Telegram forum topic message doesn't match a direct peer binding, now checks if the parent group has a binding and uses that agent. This enables multi-agent setups where forum topics inherit their parent group's agent binding automatically, consistent with Discord thread behavior added in openclaw#3892. Changes: - Pass parentPeer to resolveAgentRoute for forum topics - Parent peer is the group ID without :topic:N suffix - Add tests for Telegram forum topic binding inheritance Fixes topic routing in Telegram multi-agent configurations where topics were incorrectly routed to the default agent instead of inheriting from their parent group's binding.

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot> (cherry picked from commit 01d76e4) # Conflicts: # CHANGELOG.md # README.md

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

, upstream 01d76e4)

When a Telegram forum topic message doesn't match a direct peer binding, now checks if the parent group has a binding and uses that agent. This enables multi-agent setups where forum topics inherit their parent group's agent binding automatically, consistent with Discord thread behavior added in openclaw#3892. Changes: - Pass parentPeer to resolveAgentRoute for forum topics - Parent peer is the group ID without :topic:N suffix - Add tests for Telegram forum topic binding inheritance Fixes topic routing in Telegram multi-agent configurations where topics were incorrectly routed to the default agent instead of inheriting from their parent group's binding.

@aerolalit

…nclaw#3892) * feat(routing): add thread parent binding inheritance for Discord When a Discord thread message doesn't match a direct peer binding, now checks if the parent channel has a binding and uses that agent. This enables multi-agent setups where threads inherit their parent channel's agent binding automatically. Changes: - Add parentPeer parameter to ResolveAgentRouteInput - Add binding.peer.parent match type - Resolve thread parent early in Discord preflight - Pass parentPeer to resolveAgentRoute for threads Fixes thread routing in Discord multi-agent configurations where threads were incorrectly routed to the default agent instead of inheriting from their parent channel's binding. * ci: trigger fresh macOS runners * Discord: inherit thread bindings in reactions * fix: add changelog for thread parent binding (openclaw#3892) (thanks @aerolalit) --------- Co-authored-by: Lalit Singh <lalit@clawd.bot> Co-authored-by: OSS Agent <oss-agent@clawdbot.ai> Co-authored-by: Shadow <shadow@clawd.bot>

…aerolalit

…aerolalit)

openclaw-barnacle bot added the channel: discord Channel integration: discord label Jan 29, 2026

clawdinator bot closed this Feb 1, 2026

thewilloftheshadow reopened this Feb 1, 2026

greptile-apps bot reviewed Feb 1, 2026

View reviewed changes

thewilloftheshadow self-assigned this Feb 1, 2026

thewilloftheshadow added a commit that referenced this pull request Feb 1, 2026

fix: add changelog for thread parent binding (#3892) (thanks @aerolalit)

e9deb81

Lalit Singh and others added 4 commits January 31, 2026 20:28

ci: trigger fresh macOS runners

64ad0b7

Discord: inherit thread bindings in reactions

1a6b0fc

fix: add changelog for thread parent binding (openclaw#3892) (thanks @…

61b8dfd

…aerolalit)

thewilloftheshadow force-pushed the feature/thread-parent-binding-inheritance branch from e9deb81 to 61b8dfd Compare February 1, 2026 02:30

thewilloftheshadow merged commit 01d76e4 into openclaw:main Feb 1, 2026
17 of 23 checks passed

aerolalit deleted the feature/thread-parent-binding-inheritance branch February 1, 2026 07:21

Buywatermelon mentioned this pull request Feb 2, 2026

feat(telegram): inherit forum topic bindings from parent group #7224

Open

This was referenced Feb 4, 2026

Bug: Discord guild messages blocked when groupPolicy: "open" with wildcard guild config #8860

Closed

[Bug]: Discord guild messages blocked when groupPolicy: open with wildcard guild config #8863

Closed

kedoupi mentioned this pull request Feb 6, 2026

feat(telegram): Support per-topic agent routing via bindings #10576

Closed

github-actions bot mentioned this pull request Feb 8, 2026

cherry-pick: upstream refactor/feature commits (2026-02-08) hughdidit/DAISy-Agency#111

Closed

6 tasks

github-actions bot mentioned this pull request Feb 8, 2026

cherry-pick: upstream refactor/feature commits (2026-02-08-2013) hughdidit/DAISy-Agency#119

Merged

6 tasks

jiulingyun added a commit to jiulingyun/openclaw-cn that referenced this pull request Feb 15, 2026

feat(discord): inherit thread parent bindings for routing (openclaw#3892

802dd01

, upstream 01d76e4)

This was referenced Feb 23, 2026

Feishu topicSessionMode breaks binding matching for group chats #24685

Closed

fix(feishu): pass parentPeer for topic session binding inheritance #24686

Closed

john-ver pushed a commit to apmcoin/apmclaw that referenced this pull request Mar 9, 2026

fix: add changelog for thread parent binding (openclaw#3892) (thanks @…

2dc17ae

…aerolalit)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(routing): add thread parent binding inheritance for Discord#3892

feat(routing): add thread parent binding inheritance for Discord#3892
thewilloftheshadow merged 4 commits intoopenclaw:mainfrom
aerolalit:feature/thread-parent-binding-inheritance

aerolalit commented Jan 29, 2026 •

edited by greptile-apps bot

Loading

Uh oh!

clawdinator bot commented Feb 1, 2026

Uh oh!

kodi commented Feb 1, 2026

Uh oh!

greptile-apps bot left a comment

Uh oh!

Uh oh!

thewilloftheshadow commented Feb 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

aerolalit commented Jan 29, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Problem

Solution

Changes

Tests Added

Breaking Changes

Greptile Overview

Greptile Summary

Confidence Score: 5/5

Uh oh!

clawdinator bot commented Feb 1, 2026

Uh oh!

kodi commented Feb 1, 2026

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

thewilloftheshadow commented Feb 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

aerolalit commented Jan 29, 2026 •

edited by greptile-apps bot

Loading