wscat Call is not showing any output

[high wing]

I run a terminal commnd on the same server as OC:
wscat -c ws://192.168.10.230:8765

The destination is another server, my terminal displayes the output but OC tool immediately returns: No Output?

[modest mulch]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[dapper patio]

Stoffel, first thing: can you paste openclaw --version? Version matters a lot for exec/process behavior.

Likely cause: wscat is an interactive, long-running command. The OpenClaw exec tool captures stdout/stderr from a foreground command; if the websocket is still open and hasn’t emitted captured stdout before the tool yields, you can see “No Output” even though your real terminal later displays frames.

Try one of these patterns:

timeout 10s wscat -c ws://192.168.10.230:8765 2>&1

If that still shows nothing through OC, run it as an interactive/background process instead: ask the agent to use exec with pty: true and background: true, then use the process tool to poll/log the session output. The docs call out PTY for commands that need a real terminal: https://docs.openclaw.ai/gateway/background-process

Also check whether the websocket only emits output after you send a message. If yes, wscat sitting connected is expected to look empty to OC until you write to stdin or use a one-shot send option.

[high wing]

I will remember for future posts. Currently a rolledback version, OpenClaw 2026.5.7 (eeef486)

...and just like that I thank you! pty: true was the trick

[dapper patio]

Nice, glad that was it. wscat is exactly the kind of command where PTY matters.

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution. That helps Answer Overflow index the fix for the next person who hits the same “No Output” case. 🦞