#enable my agent to stream and explain what its doing while its working.

1 messages · Page 1 of 1 (latest)

quaint moss
#

currently my agent is basically silent while its working. using openai oauth. it doesnt stream. help bot

spare parrotBOT
#

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

oak pathBOT
#

Discord is silent by default while the agent is generating. You need to explicitly enable preview streaming for Discord.

1) Turn on live preview streaming (Discord)

In your ~/.openclaw/openclaw.json:

{
channels: {
discord: {
streaming: "partial" // off | partial | block | progress
}
}
}

Then restart the gateway:

# 
openclaw gateway restart

Docs: https://docs.openclaw.ai/channels/discord#live-stream-preview
(Concepts: https://docs.openclaw.ai/concepts/streaming)

2) “Explain what it’s doing” while working

In the thread/chat, send:

  • /verbose on (shows tool call summaries as they start)
  • or /verbose full (also includes truncated tool outputs)

Docs: https://docs.openclaw.ai/tools/thinking (covers /verbose + /reasoning)

3) Two common gotchas

  • Preview streaming is text-only (media replies won’t stream).
#
  • If you enabled Discord block streaming, OpenClaw will skip preview streaming to avoid double-streaming (see the streaming doc above).

If you paste:

  1. openclaw --version
  2. your channels.discord config block
    …I can tell you exactly why it’s still not updating.
quaint moss
#

im talking to it through openclaw control. should i be using disc instead? its my preferred way of talking but im not really using it

oak pathBOT
#

You don’t need Discord — the Control UI is the “best” surface for debugging, because it can show live tool cards + tool output while a run is in-flight.

That said: if Discord is your preferred way to chat day-to-day, it’s totally fine (and common) to use both:

  • Control UI: setup, config edits, logs, troubleshooting, watching tools run
  • Discord: “normal chatting” where you already hang out

If it feels “silent” in Control UI

Two quick things to try:

  1. Turn on tool narration:
  • send: /verbose on (or /verbose full)
    This will show what it’s doing (tool starts/results) even when the model isn’t emitting much text yet.
  1. If you truly get zero incremental updates (no partial assistant text, no tool cards), paste:
  • openclaw --version
  • what model you’re using (from Control UI → session/model picker, or openclaw models status)