NO_REPL

[unique kelp]

How do you want to hatch your bot?
│ Hatch in TUI (recommended)
openclaw tui - ws://127.0.0.1:18789 - agent main - session main

session agent:main:main

Wake up, my friend!

NO_REPLY

After entering the web UI, whenever I type anything into chat NO_REPLY is outputted back, can you fix this?

[swift barn]

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

[haughty sundial]

NO_REPLY is an internal silent-reply sentinel (“don’t deliver anything to the user”). You should basically never see it in the TUI / webchat.

When people do see it, it’s usually one of these:

1. You’re on an older OpenClaw build where TUI/Web would show NO_REPLY as a placeholder (especially when the agent sent the real message via a messaging tool and then returned NO_REPLY to avoid duplicates). This was fixed in 2026.2.15.

2. The agent is genuinely producing only the silent token (e.g. something is preventing a real run / it’s failing early).

Can you paste this first?

openclaw --version

If it’s < 2026.2.15: update to latest and restart the gateway: