#Agent is blind - tool results never reach the model on Telegram"

1 messages · Page 1 of 1 (latest)

steel light
#

Setup:

• OpenClaw latest (just updated via npm update -g openclaw)
• macOS, Apple Silicon
• Channel: Telegram (direct chat)
• Model: Claude Opus
• Gateway: running fine, openclaw status shows all green

The issue:
My agent can send messages on Telegram perfectly, but every tool call (exec, apply_patch, ls, read, session_status, sessions_list — all of them) returns no result to the model. The calls seem to execute (I can sometimes see output on my end as the user), but the model never receives the result back. It just carries on as if no result was returned.

This means the agent can't read or write files, can't update memory, can't use any tools — essentially can't learn or persist anything.

What I've tried:

• Gateway restart (openclaw gateway restart)
• npm update to latest
• Multiple different tool calls (exec, apply_patch, ls, sessions_list, session_status)
• None return results

Terminal sessions seem unaffected — the issue appears to be Telegram-specific. The agent suggested it might be a session created before tools were properly configured, but there's no sessions reset or sessions delete command to test that theory.

Expected: Tool results feed back into model context
Actual: Tool calls fire but model receives nothing back

Any ideas? Is this a known Telegram integration issue?

real nimbusBOT
#

Two things here:

1) There is a “start fresh session” command

In the Telegram DM, send either of these as a standalone message:

  • /reset (or)
  • /new

That forces a new sessionId for that chat. It’s the fastest way to test “session got into a bad state”.

Docs: https://docs.openclaw.ai/help/faq#how-do-i-start-a-fresh-conversation

2) This matches a known-ish Telegram DM failure mode

There’s a recent bug report where a Telegram DM session works fine for a while, then tools suddenly stop working (often after a tool error like an “operation was aborted”), and /reset immediately restores tool usage:

#

Even if your symptom is “tool runs but the model acts like it got nothing back”, it’s very likely the same underlying “session/tool router/transcript got corrupted” class of issue.

Quick workaround

If /reset makes tools behave again → you’re basically confirmed in that bucket.

Best next step (so it can get fixed)

Comment on that issue with:

  • openclaw --version
  • openclaw status --all (tokens are redacted)
  • A short openclaw logs --follow snippet covering one “good tool call” and one “bad tool call”
  • If you can: the relevant excerpt from the session .jsonl showing the first “missing/empty tool result” moment

3) One more macOS gotcha worth ruling out: CLI vs LaunchAgent mismatch

On macOS after npm update -g openclaw, it’s possible your terminal CLI and the LaunchAgent service are effectively running different installs/entrypoints.

Run and paste: