Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Codex plugin binding slient replies when attaching an existing Codex CLI session on a paired node

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…

When a Discord group is configured with messages.groupChat.visibleReplies: "message_tool", normal agent final text should stay private unless the agent explicitly calls the message tool.

Plugin-owned conversation bindings are different: their replies come from the owning plugin's inbound_claim result, not from a normal model final. The dispatcher already routes the inbound to the bound plugin, but sendBindingNotice() reused the normal automatic-source suppression guard and returned before delivering the plugin reply.

This change keeps message_tool suppression for normal agent replies while still delivering replies returned by plugin-owned bindings.

Root Cause

When a Discord group is configured with messages.groupChat.visibleReplies: "message_tool", normal agent final text should stay private unless the agent explicitly calls the message tool.

Plugin-owned conversation bindings are different: their replies come from the owning plugin's inbound_claim result, not from a normal model final. The dispatcher already routes the inbound to the bound plugin, but sendBindingNotice() reused the normal automatic-source suppression guard and returned before delivering the plugin reply.

This change keeps message_tool suppression for normal agent replies while still delivering replies returned by plugin-owned bindings.

Fix Action

Fix / Workaround

Plugin-owned conversation bindings are different: their replies come from the owning plugin's inbound_claim result, not from a normal model final. The dispatcher already routes the inbound to the bound plugin, but sendBindingNotice() reused the normal automatic-source suppression guard and returned before delivering the plugin reply.

src/auto-reply/reply/dispatch-from-config.test.ts

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When a Discord group is configured with messages.groupChat.visibleReplies: "message_tool", normal agent final text should stay private unless the agent explicitly calls the message tool.

Plugin-owned conversation bindings are different: their replies come from the owning plugin's inbound_claim result, not from a normal model final. The dispatcher already routes the inbound to the bound plugin, but sendBindingNotice() reused the normal automatic-source suppression guard and returned before delivering the plugin reply.

This change keeps message_tool suppression for normal agent replies while still delivering replies returned by plugin-owned bindings.

Steps to reproduce

  1. Start Openclaw 2026.5.27 with codex backend
  2. "nodes": { "allowCommands": [ "codex.cli.sessions.list", "codex.cli.session.resume"
  3. Attach an existing Codex CLI session on a paired node </codex resume <session-id> --host <node> --bind here> in Discord
  4. Send a message in Discord

Expected behavior

Codex replies shall be sent and displayed via Discord.

Actual behavior

Codex replies are silent.

OpenClaw version

2026.5.27

Operating system

macOS 26.5

Install method

No response

Model

openclaw -> codex runtime -> Codex app-server

Provider / routing chain

openclaw -> codex plugin -> node -> codex cli -> gateway -> discord

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

src/auto-reply/reply/dispatch-from-config.test.ts

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

Codex replies shall be sent and displayed via Discord.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING