#no response from Clawd

1 messages · Page 1 of 1 (latest)

dapper canopy
#

When the Clawd agent is messaged in the TUI, there is no response. Each message I send is answered with "Assistance <timestamp>" but there's no actual text. The terminal just shows "(no output)" each time I send a message

native pikeBOT
# dapper canopy When the Clawd agent is messaged in the TUI, there is no response. Each message ...

This is a known bug (GitHub issue #747). You're experiencing exactly what's documented:

The Problem:
When the primary model (Claude) hits a rate limit and fallback triggers, the TUI displays "(no output)" instead of streaming the fallback response. The response is being generated, but it doesn't render live — only shows up after restarting the session.

What's happening:

  1. Claude gets rate-limited or hits token exhaustion (429)
  2. Fallback model (likely OpenAI Codex) kicks in
  3. Response generates successfully (logs show no errors)
  4. TUI fails to stream/display it → shows "(no output)"
  5. After restart, the cached response appears

Current status:

  • Already tracked in GitHub issue #747
  • Not yet fixed (reported ~2 weeks ago)
  • The CHANGELOG mentions: "TUI: show LLM error messages (rate limits, auth, etc.) instead of (no output)" — so they're aware and working on it
dapper canopy
#

I have literally only just paid for a new Claude Pro subscription today and have used ZERO tokens. It's not possible that it's an overusage issue

native pikeBOT
# dapper canopy I have literally only just paid for a new Claude Pro subscription today and have...

Good catch — that rules out rate limiting! So this might be a broader TUI issue, not just the fallback bug.

Let me ask a few questions to narrow it down:

To diagnose:

  1. What model are you using? (run clawdbot --version to check your setup)
  2. Does this happen with every message, or only certain types?
  3. Are you seeing any errors in the terminal logs before "(no output)"?
  4. What channel/provider are you testing in? (TUI → Claude directly, or via a connector?)

The fallback bug specifically happens after a rate limit, but if you're not hitting limits and still seeing this constantly, it could be:

  • A different TUI streaming bug
  • Model configuration/auth issue
  • Something specific to your setup

Also: if you Ctrl+C out and restart, does the next message work normally, or still "(no output)"?

#

The more details you can share, the faster we can debug this! 🦐

dapper canopy
#
  1. 2026.1.24-3
  2. This happens with every message I send other than commands to the TUI chat like /status. Incidentally, the /status in the terminal returns what is shown in the first image attached
  3. See screenshot 2
  4. See response 1
Screenshot_2026-01-27_at_17.28.08.png Screenshot_2026-01-27_at_17.29.12.png
native pikeBOT
# dapper canopy 1) 2026.1.24-3 2) This happens with every message I send other than commands to ...

Found it! You're not alone — this is affecting multiple users:

Similar reports:

  • papi1992 (Jan 19): Same issue with 2026.1.17-1, switching models with /model
  • Yasu: 56 replies thread — same "(no output)" problem

Your logs tell the story:

  • Request starts → ends in 601ms
  • No response logs at all
  • Technically "successful" (aborted=false) but nothing generated

This looks like a TUI streaming/response capture bug — the response is generated but never rendered. Since /status works but messages don't, the infrastructure is fine but the response path is broken.

Quick tests to narrow it down:

  1. Try non-TUI mode:
# 
   clawdbot chat

Does this work? If yes, the bug is TUI-specific.

  1. Check if model switching affects it:

    • Are you switching models with /model?
    • Does it work immediately after starting TUI, then break?

  2. Run with verbose logging:

    clawdbot --verbose tui

    See if more details appear.

This needs a GitHub issue if there isn't one specifically for the non-fallback "(no output)" case. The existing #747 is for fallbacks, but this looks like a broader TUI bug.

#

What happens with clawdbot chat? That'll tell us if it's TUI-specific or something deeper. 🦐

dapper canopy
#

Could this be caused by me having set up/configured Telegram incorrectly? When i use the command clawdbot doctor in the terminal, it shows a 401 error and says Telegram is unauthorised.

dapper canopy
#

no response from clawd

#

no response from clawd

#

no response from clawd

lean mirage
#

Why do many of these commands that are mentioned not exist?

17:02:05 ~/.clawdbot $ clawdbot --verbose tui
error: unknown option '--verbose'
17:02:23 ~/.clawdbot $ 
17:02:23 ~/.clawdbot $ clawdbot chat         
error: unknown command 'chat'
17:03:34 ~/.clawdbot $
native pikeBOT