openclaw - 💡(How to fix) Fix CLI: openclaw message send hangs indefinitely after successful delivery

Official PRs (…)
ON THIS PAGE

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…

openclaw message send successfully delivers the message to Discord but the CLI process never exits. The node.js process remains in ep_poll (epoll_wait) state with 7 threads and 2 unix sockets open to the gateway.

Root Cause

Current workaround

timeout 10 openclaw message send ... || true

The || true is needed because timeout kills the process with exit code 124.

Fix Action

Fix / Workaround

Current workaround

timeout 10 openclaw message send ... || true

The || true is needed because timeout kills the process with exit code 124.

Code Example

# This hangs forever (message IS delivered to Discord)
openclaw message send --channel discord --target "channel:<channel_id>" -m "test" --json

# Must be killed manually or with timeout
timeout 10 openclaw message send --channel discord --target "channel:<channel_id>" -m "test" --json

---

State: S (sleeping)
Threads: 7
wchan: ep_poll
Open fds: 2 unix sockets (ESTAB) to gateway, 1 eventpoll, 1 io_uring, 1 pipe, 1 eventfd
No TCP connections (gateway communication is via unix socket)

---

codex-discord-send --channel general --message "progress update"

---

timeout 10 openclaw message send ... || true
RAW_BUFFERClick to expand / collapse

Bug: openclaw message send CLI hangs indefinitely after successful delivery

Version

OpenClaw 2026.5.27 (27ae826)

Description

openclaw message send successfully delivers the message to Discord but the CLI process never exits. The node.js process remains in ep_poll (epoll_wait) state with 7 threads and 2 unix sockets open to the gateway.

Reproduction

# This hangs forever (message IS delivered to Discord)
openclaw message send --channel discord --target "channel:<channel_id>" -m "test" --json

# Must be killed manually or with timeout
timeout 10 openclaw message send --channel discord --target "channel:<channel_id>" -m "test" --json

Evidence: Other message subcommands exit cleanly

CommandExits?Duration
openclaw message send❌ Never
openclaw message send --dry-run✅ Yes~4s
openclaw message read✅ Yes~4s
openclaw message thread create✅ Yes~5s
openclaw health✅ Yes~1s

Process state while hung

State: S (sleeping)
Threads: 7
wchan: ep_poll
Open fds: 2 unix sockets (ESTAB) to gateway, 1 eventpoll, 1 io_uring, 1 pipe, 1 eventfd
No TCP connections (gateway communication is via unix socket)

Impact

This breaks codex-discord-send bridge scripts used by Codex sandbox agents (stuart-coder, etc.). These agents are instructed to send Discord progress updates via:

codex-discord-send --channel general --message "progress update"

Which internally calls openclaw message send. Since the process never exits, the Codex sandbox treats it as a hung command and the agent either times out or skips subsequent Discord updates.

Result: Codex agents never send progress updates to Discord threads, despite the messages actually being delivered.

Current workaround

timeout 10 openclaw message send ... || true

The || true is needed because timeout kills the process with exit code 124.

Suspected root cause

The CLI loads the discord plugin out-of-process for send. After the gateway delivers the message, the plugin's event loop / connection is not properly cleaned up (no client.destroy() or process.exit() call on the send code path). Other actions (read, thread create) either use a different code path or properly close their connections.

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…

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 CLI: openclaw message send hangs indefinitely after successful delivery