#I’m new and need help

1 messages · Page 1 of 1 (latest)

void hornet
#

I just installed open claw but when I try to text it my messages come up blank. Fresh Mac install, OpenRouter key works (curl tested), sessions cleared, full reinstall done. Every model returns blank response with incomplete turn detected, payloads=0 in logs. Web UI and Telegram both show blank. Anyone seen this?

mild eagleBOT
#

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

quartz shadowBOT
trail cradleBOT
#

Let me check the local docs paths and the exact log string before I steer you wrong.

#

Yep, this rings a bell.

incomplete turn detected ... payloads=0 means the model run happened, but OpenClaw got no visible assistant text back. So this is probably not a Telegram/Web UI issue.

Most likely culprits:

  1. OpenRouter streaming bug / older build
    There are recent fixes for blank OpenRouter replies and reasoning_details handling. If you're on 2026.4.14 or older, I'd try updating first: https://docs.openclaw.ai/install/updating

  2. macOS launchd env mismatch
    On macOS, the gateway service often does not inherit your shell env. So curl working in Terminal does not prove the gateway sees OPENROUTER_API_KEY.
    Put the key in ~/.openclaw/.env or enable shell env import, then restart. Docs: https://docs.openclaw.ai/help/faq

Can you paste these?

# 
openclaw --version
openclaw status --all
openclaw models status --probe
openclaw infer model run --model <exact-model> --prompt "say hi" --json

If infer model run is blank too, that narrows it to provider/runtime, not channel routing.

If you paste those outputs, I can help pin it down pretty quickly.

void hornet
#

k3v0@Mac ~ % openclaw infer model run --model openrouter/anthropic/claude-sonnet-4.5 --prompt "say hi" --json
08:20:41 [agent/embedded] incomplete turn detected: runId=b2a6b518-a884-4aaf-996b-b740c3036f61 sessionId=b2a6b518-a884-4aaf-996b-b740c3036f61 stopReason=stop payloads=0 — surfacing error to user
{
"ok": true,
"capability": "model.run",
"transport": "local",
"provider": "openrouter",
"model": "anthropic/claude-sonnet-4.5",
"attempts": [],
"outputs": [
{
"text": "⚠️ Agent couldn't generate a response. Please try again.",
"mediaUrl": null
}
]
}

trail cradleBOT
#

I’ve got enough to narrow this down a lot more. Let me check the OpenRouter reasoning/streaming bits so I can give you the least-annoying workaround, not just “update and pray.”

#

That repro is super helpful.

Because infer model run also fails, this is not Telegram/UI/session routing. It’s the model transport/parser path.

And stopReason=stop + payloads=0 is the tell: the request finished “cleanly”, but this build extracted no visible text from the OpenRouter stream.

That matches a recent OpenRouter streaming bug/fix pretty closely, especially around newer streamed response shapes.

Two things I’d do next:

openclaw --version

If you’re on 2026.4.14 or older, I’d strongly try updating to current dev/main and retest:

# 
openclaw update --channel dev
openclaw gateway restart
openclaw infer model run --model openrouter/anthropic/claude-sonnet-4.5 --prompt "say hi" --json

Docs:

Why I’m leaning that way:

  • recent fixes landed for OpenRouter blank/empty streamed replies
  • your run is returning ok=true with no auth error
  • if this were missing env/key on macOS, I’d expect auth failures, not stop payloads=0

If you want one extra confirmation before updating, paste:

# 
openclaw models status --probe

But honestly, from that repro, I think you’re probably hitting the OpenRouter stream parsing bug rather than a bad local setup.

void hornet
#

it works now. i just had to run the channel dev command