Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: published package omits Discord subagent deliveryOrigin fix [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The Discord source fix from #83172 is merged on main, but the published [email protected] package still ships a compiled Discord subagent hook that returns only threadBindingReady: true from subagent_spawning and omits the bound thread deliveryOrigin.

That leaves clean installs with the original Discord thread-bound child-session behavior: the binding can succeed, but the initial child delivery can still fall back to the parent Discord channel.

Root Cause

Discord thread-bound delegated sessions remain broken for clean installs even though the source fix is merged. Users can misdiagnose this as local config drift because main and the merged PR look correct while the installed package bytes are stale.

Fix Action

Fixed

Code Example

return {
  status: "ok",
  threadBindingReady: true,
  deliveryOrigin: {
    channel: "discord",
    accountId: account.accountId,
    to: `channel:${binding.threadId}`,
    threadId: binding.threadId,
  },
};
RAW_BUFFERClick to expand / collapse

Bug type

Packaging / release artifact bug

Summary

The Discord source fix from #83172 is merged on main, but the published [email protected] package still ships a compiled Discord subagent hook that returns only threadBindingReady: true from subagent_spawning and omits the bound thread deliveryOrigin.

That leaves clean installs with the original Discord thread-bound child-session behavior: the binding can succeed, but the initial child delivery can still fall back to the parent Discord channel.

Evidence

Observed on a clean global install of [email protected]:

  • openclaw --version reports OpenClaw 2026.5.18.
  • The installed compiled Discord hook under dist/subagent-hooks-*.js contains the extensions/discord/src/subagent-hooks.ts source marker.
  • Its subagent_spawning success path returns only { status: "ok", threadBindingReady: true }.
  • It does not include the deliveryOrigin object added by #83172.

By contrast, origin/main now has the correct source contract:

return {
  status: "ok",
  threadBindingReady: true,
  deliveryOrigin: {
    channel: "discord",
    accountId: account.accountId,
    to: `channel:${binding.threadId}`,
    threadId: binding.threadId,
  },
};

Expected behavior

Package/tarball acceptance and post-publish verification should fail if a 2026.5.18-or-newer package contains the compiled Discord subagent hook but omits the bound-thread deliveryOrigin contract.

Actual behavior

The stale compiled hook passed release/package verification and was installable as openclaw@latest.

Impact

Discord thread-bound delegated sessions remain broken for clean installs even though the source fix is merged. Users can misdiagnose this as local config drift because main and the merged PR look correct while the installed package bytes are stale.

Proposed fix

Add a targeted package/tarball and post-publish verification guard that scans the compiled Discord subagent hook and rejects 2026.5.18-or-newer packages unless the hook includes the deliveryOrigin return contract from #83172.

Related

  • Original source bug: #83170
  • Source fix: #83172

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Package/tarball acceptance and post-publish verification should fail if a 2026.5.18-or-newer package contains the compiled Discord subagent hook but omits the bound-thread deliveryOrigin contract.

#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: published package omits Discord subagent deliveryOrigin fix [1 pull requests]