openclaw - ✅(Solved) Fix [Bug]: Discord replies generated locally but not delivered/rendered in Discord [1 pull requests, 1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75207Fetched 2026-05-01 05:36:49
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
2
Author
Timeline (top)
labeled ×2mentioned ×2subscribed ×2closed ×1

Summary

Discord inbound works and the model generates replies, but final assistant replies do not appear in Discord.

Environment

  • OpenClaw: 2026.4.27
  • macOS: 26.3.1 arm64
  • Node: 22.22.0
  • Gateway: local LaunchAgent, healthy
  • Default model: openai-codex/gpt-5.5
  • Discord streaming: off
  • WhatsApp: disabled

Repro

  1. Restart gateway.
  2. Confirm openclaw status --deep shows Gateway reachable and Discord OK.
  3. Send in Discord #general from a user account:
    @clawc brown reply exactly reinvite-fixed

Expected

Bot posts:
reinvite-fixed

Actual

No visible Discord reply.

Evidence

  • User-authored Discord message reaches OpenClaw.
  • Session history shows assistant generated exactly reinvite-fixed.
  • Session status is done.
  • Reply does not appear in Discord.
  • Raw Discord API send/read works.
  • Re-inviting the bot with fresh scopes/permissions did not fix it.
  • Codex auth is healthy.

Relevant paths

  • Failed session transcript:
    /Users/moltbot/.openclaw/agents/codex/sessions/d046e2b3-17a0-4997-9264-32308c3a7798.jsonl

openclaw-discord-global-failed-send.log openclaw-sfc-main-failed-send.log

Root Cause

Summary

Discord inbound works and the model generates replies, but final assistant replies do not appear in Discord.

Environment

  • OpenClaw: 2026.4.27
  • macOS: 26.3.1 arm64
  • Node: 22.22.0
  • Gateway: local LaunchAgent, healthy
  • Default model: openai-codex/gpt-5.5
  • Discord streaming: off
  • WhatsApp: disabled

Repro

  1. Restart gateway.
  2. Confirm openclaw status --deep shows Gateway reachable and Discord OK.
  3. Send in Discord #general from a user account:
    @clawc brown reply exactly reinvite-fixed

Expected

Bot posts:
reinvite-fixed

Actual

No visible Discord reply.

Evidence

  • User-authored Discord message reaches OpenClaw.
  • Session history shows assistant generated exactly reinvite-fixed.
  • Session status is done.
  • Reply does not appear in Discord.
  • Raw Discord API send/read works.
  • Re-inviting the bot with fresh scopes/permissions did not fix it.
  • Codex auth is healthy.

Relevant paths

  • Failed session transcript:
    /Users/moltbot/.openclaw/agents/codex/sessions/d046e2b3-17a0-4997-9264-32308c3a7798.jsonl

openclaw-discord-global-failed-send.log openclaw-sfc-main-failed-send.log

PR fix notes

PR #75382: fix(auto-reply): keep group visible replies deliverable

Description (problem / solution / changelog)

Summary

  • keep the message tool available when group/channel visible replies require message-tool delivery
  • include group/subagent tool policy in visible-reply fallback detection so restricted rooms fall back to automatic delivery instead of going silent
  • extend qa-channel and qa-lab with Discord/Slack-style group:<room> coverage for message-tool replies and fallback replies

Verification

  • pnpm test extensions/qa-channel/src/bus-client.test.ts extensions/qa-channel/src/channel.test.ts extensions/qa-lab/src/scenario-catalog.test.ts extensions/qa-lab/src/providers/mock-openai/server.test.ts src/auto-reply/reply/dispatch-from-config.test.ts src/auto-reply/reply/followup-runner.test.ts
  • pnpm config:channels:check
  • git diff --check
  • OPENCLAW_QA_SUITE_PROGRESS=1 fnm exec --using v22.21.1 node --input-type=module ... for group-visible-reply-tool and group-message-tool-unavailable-fallback

QA artifact: .artifacts/qa-e2e/group-visible-replies-pr/qa-suite-report.md

Fixes #74842. Refs #75207.

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • docs/channels/qa-channel.md (modified, +2/-0)
  • extensions/qa-channel/src/bus-client.test.ts (modified, +14/-1)
  • extensions/qa-channel/src/bus-client.ts (modified, +9/-3)
  • extensions/qa-channel/src/channel-actions.ts (modified, +1/-1)
  • extensions/qa-channel/src/channel.test.ts (modified, +121/-0)
  • extensions/qa-channel/src/channel.ts (modified, +20/-3)
  • extensions/qa-channel/src/config-schema.ts (modified, +15/-1)
  • extensions/qa-channel/src/inbound.ts (modified, +10/-9)
  • extensions/qa-channel/src/types.ts (modified, +10/-0)
  • extensions/qa-lab/src/bus-queries.ts (modified, +5/-0)
  • extensions/qa-lab/src/providers/mock-openai/server.ts (modified, +18/-0)
  • extensions/qa-lab/src/runtime-api.ts (modified, +1/-0)
  • extensions/qa-lab/src/suite.ts (modified, +12/-0)
  • qa/scenarios/channels/group-message-tool-unavailable-fallback.md (added, +98/-0)
  • qa/scenarios/channels/group-visible-reply-tool.md (added, +96/-0)
  • src/agents/pi-tools.policy.ts (modified, +5/-7)
  • src/auto-reply/reply/agent-runner-execution.ts (modified, +2/-0)
  • src/auto-reply/reply/dispatch-from-config.test.ts (modified, +36/-0)
  • src/auto-reply/reply/dispatch-from-config.ts (modified, +61/-5)
  • src/auto-reply/reply/followup-runner.test.ts (modified, +1/-0)
  • src/auto-reply/reply/followup-runner.ts (modified, +1/-0)
  • src/config/bundled-channel-config-metadata.generated.ts (modified, +172/-0)
  • src/plugin-sdk/qa-channel-protocol.ts (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

Discord inbound works and the model generates replies, but final assistant replies do not appear in Discord.

Environment

  • OpenClaw: 2026.4.27
  • macOS: 26.3.1 arm64
  • Node: 22.22.0
  • Gateway: local LaunchAgent, healthy
  • Default model: openai-codex/gpt-5.5
  • Discord streaming: off
  • WhatsApp: disabled

Repro

  1. Restart gateway.
  2. Confirm openclaw status --deep shows Gateway reachable and Discord OK.
  3. Send in Discord #general from a user account:
    @clawc brown reply exactly reinvite-fixed

Expected

Bot posts:
reinvite-fixed

Actual

No visible Discord reply.

Evidence

  • User-authored Discord message reaches OpenClaw.
  • Session history shows assistant generated exactly reinvite-fixed.
  • Session status is done.
  • Reply does not appear in Discord.
  • Raw Discord API send/read works.
  • Re-inviting the bot with fresh scopes/permissions did not fix it.
  • Codex auth is healthy.

Relevant paths

  • Failed session transcript:
    /Users/moltbot/.openclaw/agents/codex/sessions/d046e2b3-17a0-4997-9264-32308c3a7798.jsonl

openclaw-discord-global-failed-send.log openclaw-sfc-main-failed-send.log

Notes

systemSent=true appears in session metadata, but source inspection suggested that is not proof of Discord delivery; it is set during session setup/metadata, before actual outbound delivery.

Steps to reproduce

  1. Run OpenClaw gateway on 2026.4.27 with Discord enabled.
  2. Confirm openclaw status --deep shows Gateway reachable and Discord OK/configured.
  3. In Discord #general, from a user account, send:
    @clawc brown reply exactly reinvite-fixed
  4. Check Discord for the bot reply.
  5. Check local OpenClaw session history for the same channel.

Expected behavior

The bot should post reinvite-fixed in the same Discord channel. This is the expected behavior for a Discord channel reply after a user mention is received and the assistant produces final text.

Actual behavior

No visible Discord reply appears. Local OpenClaw session history shows the user-authored Discord message was received and the assistant generated reinvite-fixed; the session status is done, but the generated final reply does not
render in Discord.

OpenClaw version

2026.4.27 (cbc2ba0)

Operating system

macOS 26.3.1 arm64

Install method

Global npm/pnpm-style install under /Users/moltbot/homebrew, running as a macOS LaunchAgent via openclaw gateway.

Model

openai-codex/gpt-5.5

Provider / routing chain

Discord channel inbound -> local OpenClaw gateway -> codex agent -> openai-codex/gpt-5.5 -> Discord channel reply delivery.

Additional provider/model setup details

  • Codex auth was verified healthy with openclaw models status; openai-codex:default ok expires in 10d.
  • Default agent model: openai-codex/gpt-5.5.
  • Opus lane exists separately with claude-cli, but was not the route under test.
  • Discord streaming was set to off during repro.
  • WhatsApp was disabled during repro.
  • Re-inviting the same Discord bot with refreshed scopes/permissions did not fix the issue.

Logs, screenshots, and evidence

Impact and severity

Affected users/systems/channels:

  • Discord channel integration for this OpenClaw gateway.
  • Reproduced in #general and #sfc-main.

Severity:

  • Blocks workflow. Discord appears to accept messages and the bot starts processing, but no assistant reply is
    delivered visibly.

Frequency:

  • Reproduced consistently during this debugging session after gateway restart, token/auth verification, and bot
    re-invite.

Consequence:

  • Missed replies in Discord even though local generation succeeds. Users cannot rely on Discord as an OpenClaw channel and must use local/web/terminal fallback.

Additional information

  • Raw Discord API send/read worked using the same bot, so basic Discord token/permissions were not obviously broken.
  • openclaw status --deep showed Gateway reachable and Discord OK/configured.
  • systemSent=true appears in session metadata, but local source inspection suggested this is not proof of Discord
    delivery; it appears to be set during session setup/metadata rather than after outbound Discord send acknowledgement.
  • A test on 2026.4.29-beta.1 introduced separate Codex auth/runtime noise, so the clean repro is reported against
    2026.4.27.
  • Earlier logs showed intermittent event-loop/liveness warnings and Discord slash-command deploy 429s, but the clean
    repro had Codex auth healthy and Discord configured.

extent analysis

TL;DR

The issue is likely related to the Discord reply not being delivered due to a problem with the OpenClaw gateway or the Discord API integration, and a workaround may involve checking the Discord API send/read logs or reconfiguring the OpenClaw gateway settings.

Guidance

  • Check the openclaw-discord-global-failed-send.log and openclaw-sfc-main-failed-send.log logs for any error messages or clues about the failed Discord reply delivery.
  • Verify that the Discord API token and permissions are correctly configured and not expired.
  • Test the Discord API send/read functionality using a separate tool or script to rule out any issues with the OpenClaw gateway.
  • Re-check the OpenClaw gateway settings and configuration to ensure that Discord is properly enabled and configured.

Example

No code snippet is provided as the issue is more related to configuration and logging.

Notes

The issue seems to be specific to the OpenClaw gateway and Discord API integration, and more information about the logs and configuration may be needed to provide a more accurate solution.

Recommendation

Apply a workaround by reconfiguring the OpenClaw gateway settings or checking the Discord API send/read logs to identify the root cause of the issue. This is because the problem seems to be related to the integration between OpenClaw and Discord, and a workaround may help to mitigate the issue until a more permanent fix is found.

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

The bot should post reinvite-fixed in the same Discord channel. This is the expected behavior for a Discord channel reply after a user mention is received and the assistant produces final text.

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 - ✅(Solved) Fix [Bug]: Discord replies generated locally but not delivered/rendered in Discord [1 pull requests, 1 comments, 2 participants]