#openclaw onboard telegram

1 messages · Page 1 of 1 (latest)

crystal zinc
#

I am not able to connect my telegram bot with openclaw can anybody please help me with that??

rough ermineBOT
#

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

livid yokeBOT
#

Yep — first thing: please paste openclaw --version and don’t paste your Telegram token publicly.

Quick checklist:

openclaw --version
openclaw status
openclaw channels status --probe
openclaw logs --follow

For Telegram, you don’t use openclaw channels login telegram. You create a bot in @BotFather, then configure the token:

{
  channels: {
# 
    telegram: {
      enabled: true,
      botToken: "123:abc",
      dmPolicy: "pairing",
      groups: { "*": { requireMention: true } }
    }
  }
}

Then restart/start the gateway and approve your DM:

openclaw gateway restart
openclaw pairing list telegram
# 
openclaw pairing approve telegram <CODE>

Common failures:

  • /start works but no reply → pairing not approved
  • getMe returned 401 → wrong/revoked BotFather token
  • group silent → mention the bot, disable BotFather privacy mode, or make it admin
  • group IDs go under channels.telegram.groups; user IDs go under allowFrom / groupAllowFrom

Docs: https://docs.openclaw.ai/channels/telegram

crystal zinc
#

why its taking so long for processing whenever i enter any command
even simplest command like openclaw --version

livid yokeBOT
#

If openclaw --version is slow in your server/PC terminal, that’s not a Telegram issue — it means the CLI install/runtime is slow or stuck.

First check whether you’re accidentally running through npx/pnpm dlx every time:

type -a openclaw
command -v openclaw
time openclaw --version
node -v

If type -a openclaw shows an alias/function using npx, that’s likely the delay. Install globally instead:

npm install -g openclaw@latest
#

If you mean you’re sending openclaw --version inside Telegram chat, that goes through the AI/model/tool loop, so it won’t be instant. Run version checks in the terminal.

Please paste the output of the 4 commands above, plus what OS/VPS you’re using. Don’t paste bot tokens. 🦐

crystal zinc
#

it says -a cpommand not found
and i have run npm command
what next??

livid yokeBOT
#

The command is:

type -a openclaw

all on one line — don’t run -a by itself.

Next, open a new terminal and run:

node -v
openclaw --version
command -v openclaw

If openclaw --version works, continue Telegram setup:

# 
openclaw gateway restart
openclaw status
openclaw pairing list telegram

If openclaw is still “command not found”, your global install bin folder is probably not in PATH. Paste the output of:

node -v
pnpm -v
command -v node
command -v pnpm
command -v openclaw

Also tell us your OS: Windows / WSL / macOS / Linux VPS.

crystal zinc
#

it says no pending telegram pairing req

#

its windows

livid yokeBOT
#

“No pending telegram pairing req” usually means OpenClaw hasn’t received a new DM from your Telegram bot yet.

Do this in order:

  1. In Telegram, open your bot directly and send:
/start

or any message like hi.

  1. Immediately run:
openclaw logs --follow
#
  1. In another terminal run:
openclaw channels status --probe
openclaw pairing list telegram

If pairing still shows nothing:

  • you may be messaging the wrong bot
  • the BotFather token in config may be wrong
  • Telegram channel may not be enabled
  • gateway may not be running
  • another process may be using the same bot token

Please paste the output of these, with tokens redacted:

# 
openclaw --version
openclaw status
openclaw channels status --probe

Also: pairing is for DMs only. If you’re testing in a Telegram group, first get DMs working, then configure group access.

#

Ah, on Windows that explains the type -a issue — that was a Linux/macOS shell command.

If you’re in PowerShell, use these instead:

Get-Command openclaw
node -v
npm -v
openclaw --version

Windows support works, but WSL2 is the recommended/stabler path for OpenClaw. Native Windows can work for CLI/Gateway, but setup is still rougher.

If openclaw --version works, run:

crystal zinc
#

PS C:\Users\ADMIN> openclaw logs --follow
Config warnings:

  • plugins: plugin: ignored plugins.load.paths entry that points at OpenClaw's current bundled plugin directory; remove this redundant path or run openclaw doctor --fix

🦞 OpenClaw 2026.4.26 (be8c246) — Making 'I'll automate that later' happen now.

│
◇ Config warnings ───────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins: plugin: ignored plugins.load.paths entry that points at OpenClaw's current │
│ bundled plugin directory; remove this redundant path or run openclaw doctor --fix │
│ │
├─────────────────────────────────────────────────────────────────────────────────────────╯
Config warnings:

  • plugins: plugin: ignored plugins.load.paths entry that points at OpenClaw's current bundled plugin directory; remove this redundant path or run openclaw doctor --fix
    Gateway not reachable. Is it running and accessible?
    Gateway target: ws://127.0.0.1:18789
    Source: local loopback
    Config: C:\Users\ADMIN.openclaw\openclaw.json
    Bind: loopback
    Hint: run openclaw doctor.
    PS C:\Users\ADMIN>

what now ???

livid yokeBOT
#

The important line is:

Gateway not reachable. Is it running?

So Telegram pairing won’t appear yet because the Gateway isn’t running.

In PowerShell, run:

openclaw doctor --fix
openclaw gateway run

Keep that terminal open. If the gateway starts, open a second PowerShell and run:

# 
openclaw gateway status
openclaw channels status --probe
openclaw pairing list telegram

Then DM your Telegram bot /start.

If openclaw gateway run exits or shows an error, paste that error here. The plugin warning is probably not the main blocker; the Gateway being down is. 🦐

crystal zinc
livid yokeBOT
#

Yep, tiny typo — it’s plural:

openclaw channels status --probe

But first make sure the gateway is actually running. Use this sequence:

Terminal 1:

openclaw gateway run

Leave it open.

Terminal 2:

# 
openclaw gateway status
openclaw channels status --probe
openclaw pairing list telegram

Then message your Telegram bot /start.

If Terminal 1 shows an error, paste that error — that’s the real blocker.

crystal zinc
#

[assistant turn failed before producing content]

why its not replying on openclaw dashboard

livid yokeBOT
#

If OpenClaw Dashboard/WebChat isn’t replying, that usually means the issue is gateway/model/session, not Telegram yet.

Please paste these first:

openclaw --version
openclaw status --all
openclaw gateway status

Then watch logs while sending one test message in the dashboard:

openclaw logs --follow

If Telegram is the thing you’re setting up, quick checklist:

# 
{
  channels: {
    telegram: {
      enabled: true,
      botToken: "YOUR_BOTFATHER_TOKEN",
      dmPolicy: "pairing",
    },
  },
}

Then restart/start gateway and approve your first DM:

openclaw gateway restart
crystal zinc
#

windows with wsl2

#

its actaully connected with telegram

livid yokeBOT
#

WSL2 is good — that’s the recommended Windows path.

Run these inside WSL/Ubuntu, not PowerShell, and paste the output:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw models status

For the Dashboard specifically: send /status in the dashboard/WebChat.

  • If /status replies but normal messages don’t → likely model/auth issue.
  • If /status also doesn’t reply → likely dashboard ↔ gateway auth/connection issue.

Then keep logs open and send one dashboard message:

crystal zinc
#

@jovial leaf bro please help me i am setting up openclaw for 3 days

livid yokeBOT
#

Got it — then Telegram setup may be fine; let’s isolate Dashboard/WebChat.

Inside WSL run:

openclaw dashboard

Open the URL it prints. If the UI says disconnected/unauthorized, go to:

Control → Overview → Gateway Access

Paste the Gateway Token or Password there, then click Connect.

Then in Dashboard/WebChat try:

#

Oof, 3 days is rough — let’s make this smaller. Don’t change Telegram stuff for now if it’s already connected.

Please run this inside WSL/Ubuntu and paste the output here — don’t paste your bot token/API keys:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw models status

Then run this:

openclaw dashboard
#

Open the URL it prints, send /status in the dashboard, and tell us:

  1. Does /status reply in Dashboard?
  2. Does Telegram reply if you DM the bot?
  3. What error appears in:
openclaw logs --follow

The key split is:

  • Telegram replies but Dashboard doesn’t → Dashboard/Gateway token or browser connection issue.
  • /status replies but normal messages don’t → model/auth issue.
  • Nothing replies anywhere → Gateway/session issue.

Docs for reference: https://docs.openclaw.ai/gateway/troubleshooting

crystal zinc
#

@jovial leaf I have installed openclaw
set auth provider to gemini
set search provider to gemini
setup telegram channel
downloaded skills using homebrew
and now when i am trying to run openclaw dashboard its not replyin on the chatbox in browser of openclaw

livid yokeBOT
#

That helps. Telegram being connected means the channel side is probably okay — now we debug Dashboard/WebChat + Gemini model auth.

Important: search provider = Gemini only affects web search, not whether the assistant can answer normal chat. Normal replies need the chat model/auth working.

Please run this inside WSL/Ubuntu and paste the output, with keys/tokens redacted:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw models status --probe

Then:

# 
openclaw dashboard

Open the URL it prints, send exactly:

/status

If /status replies but “hello” doesn’t, it’s almost certainly Gemini/model auth. If /status also doesn’t reply, it’s Dashboard ↔ Gateway auth/connection.

Also run logs while sending one dashboard message:

openclaw logs --follow
crystal zinc
#

13:19:56 Embedded agent failed before reply: ⚠️ Google Generative AI API error (429): You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits. To monitor your current usage, head to: https:… [code=RESOURCE_EXHAUSTED]

livid yokeBOT
#

Yep — that log is the root cause.

OpenClaw is reaching Gemini, but Gemini is rejecting the request:

429 RESOURCE_EXHAUSTED = quota/rate limit exhausted

So Dashboard isn’t replying because the agent fails before it can produce a reply.

Fix options:

  1. Wait for Gemini quota/rate limit reset.
  2. Enable/upgrade billing/quota on the Google/Gemini API project.
  3. Switch OpenClaw to another working model/provider:
crystal zinc
#

does ollama reuqiores api key?? for setting up it for auth provider and search provider

livid yokeBOT
#

Short answer: local Ollama does not need a real API key.

But there are two separate things:

1) Ollama as model/chat provider

  • Local/LAN Ollama: no real key needed; OpenClaw can use the local marker/placeholder.
  • Ollama Cloud / https://ollama.com: needs OLLAMA_API_KEY.

For local Ollama, first make sure OpenClaw can reach it from WSL:

curl http://127.0.0.1:11434/api/tags

If that fails, Ollama is not reachable from WSL yet.

2) Ollama as search provider

#
  • Local/self-hosted Ollama Web Search: no separate search API key, but you need:
ollama signin
  • Direct hosted Ollama search via https://ollama.com: needs OLLAMA_API_KEY.

Setup path I’d use:

openclaw configure --section model
openclaw configure --section web
openclaw gateway restart

Then test: