installing and stuck on hat my bot ste | Friends of the Crustacean 🦞🤝 | Page 1

pearl hound Apr 19, 2026, 8:32 PM

#

need some guidance froim this step forward. i always get stuck and confused here.
How do you want to hatch your bot?
│ ● Hatch in TUI (recommended)
│ ○ Open the Web UI
│ ○ Do this later

warm hamletBOT Apr 19, 2026, 8:32 PM

#

sleek crystalBOT Apr 19, 2026, 8:32 PM

#

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

warm hamletBOT Apr 19, 2026, 8:32 PM

#

karmic ravenBOT Apr 19, 2026, 8:33 PM

#

You’re not making a permanent config choice here, it’s just where to open your first chat.

Hatch in TUI: chat opens in the terminal. Usually pick this and press Enter.
Open the Web UI: opens the browser dashboard instead.
Do this later: finish setup now, open the dashboard later with openclaw dashboard --no-open.

So, if you’re installing on your normal machine, I’d choose Hatch in TUI.

If you’re on SSH / a remote box / Oracle, I’d choose Do this later instead.

If it gets stuck after this, paste these:

openclaw --version
openclaw status
openclaw models status

#

If you see “Wake up, my friend!” with no reply, that usually means the gateway/auth part is stuck, not you.

Docs:
https://docs.openclaw.ai/start/wizard
https://docs.openclaw.ai/help/faq

pearl hound Apr 19, 2026, 8:35 PM

#

Can you walk me throught the step for getting telegram connected now

karmic ravenBOT Apr 19, 2026, 8:36 PM

#

Yep. Telegram is one of the easier ones.

Important gotcha first: Telegram does not use openclaw channels login telegram.

Step-by-step

Create a Telegram bot token
- In Telegram, open @BotFather
- Run /newbot
- Follow the prompts
- Copy the bot token
Put that token into OpenClaw
In your config, add:

#

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

Or use env for the default account:

#

   export TELEGRAM_BOT_TOKEN="123:abc"

Start or restart the gateway
```
openclaw gateway restart
```
DM your bot on Telegram
Send it something like hi.
Approve the pairing code on your machine
OpenClaw uses pairing for Telegram DMs by default.

#

   openclaw pairing list telegram
   openclaw pairing approve telegram <CODE> --notify

Send another message to the bot
After approval, it should reply normally.

If you want Telegram groups later

Two common Telegram gotchas:

bots default to privacy mode
group replies usually require a mention

If you want group support after DMs work, I can walk you through that too.

If it doesn’t respond

Paste these:

#

openclaw --version
openclaw status
openclaw logs --follow

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

If you want, I can also give you the exact next click/command based on whether you’re doing this on local install, Docker, or a VPS.

pearl hound Apr 19, 2026, 8:36 PM

#

I chose hatch in TUI nopw i have ths prompt: How do you want to hatch your bot?
│ Hatch in TUI (recommended)
openclaw tui - ws://127.0.0.1:18789 - agent main - session main

session agent:main:main

Wake up, my friend!

Hello! I'm awake and ready to help. What can I do for you today?
gateway connected | idle
agent main | session main (openclaw-tui) | openrouter/openrouter/auto | think low | tokens 11k/200k (5%)
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

karmic ravenBOT Apr 19, 2026, 8:37 PM

#

Nice, that means hatching worked 🎉

You are not stuck anymore. That screen means:

the gateway is connected
the bot is awake
the empty area is just waiting for you to type a chat message

Important

That TUI is chat, not where you paste your Telegram token.

For Telegram setup, do this in a second terminal (or exit TUI with Ctrl+D, or Ctrl+C twice).

Next steps for Telegram

Create a bot in Telegram
- Open @BotFather
- Run /newbot

#

Copy the token

Add the token to your OpenClaw config
Usually in ~/.openclaw/openclaw.json:

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

#

Or use env:

export TELEGRAM_BOT_TOKEN="123:abc"

Restart the gateway
```
openclaw gateway restart
```
DM your bot on Telegram
Send hi
Approve the pairing request on your machine

#

   openclaw pairing list telegram
   openclaw pairing approve telegram <CODE> --notify

Send another message
It should reply normally now.

Quick sanity check

If you want, paste these next:

openclaw --version
openclaw status

and I’ll tell you the exact next move.

#

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

pearl hound Apr 19, 2026, 8:41 PM

#

hold on, I am at this step I want to get to the finish line as easily as possible. I want to create a new bot in telegram to work with this. can you walk me through step by step slowly as i am not familiar with telegram.

karmic ravenBOT Apr 19, 2026, 8:43 PM

#

Yep. Let’s take the easiest path.

Where you are right now

That TUI screen is good. It means OpenClaw is running.

You do not need to do anything else in that TUI right now.

You can leave it open
Or close it with Ctrl+D
For the Telegram setup, open a second terminal window

Part 1, create your Telegram bot

If you do not already have Telegram on your phone/computer:

#

Install Telegram
Create your own normal Telegram account
Log in

Then:

In Telegram, search for @BotFather
- make sure it is exactly BotFather
Open that chat
Press Start
Send this message:
```
/newbot
```
BotFather will ask for a name

#

this is just the display name
- example: Spearmin Assistant

BotFather will ask for a username
- this must end in bot
- example: spearmin_helper_bot
BotFather will then send you a bot token
- it looks like a long password
- keep it secret
- do not paste it in Discord

Part 2, connect that Telegram bot to OpenClaw

In a second terminal window on your computer, run:

#

openclaw channels add --channel telegram --token "PASTE_YOUR_BOT_TOKEN_HERE"

Then restart the gateway:

openclaw gateway restart

Then check status:

openclaw channels status --probe

You want to see Telegram show up there.

#

Part 3, approve yourself in Telegram

Now go back to Telegram.

Open the chat with your new bot
Send it:

hi

The bot should send you a pairing code

Back in your terminal, run:

#

openclaw pairing list telegram

Then approve the code:

openclaw pairing approve telegram <CODE> --notify

Replace <CODE> with the code Telegram gave you.

Part 4, test it

Go back to Telegram

#

Send your bot another message:

hi

If all is well, it should reply normally.

Two common gotchas

the bot username must end in bot
the Telegram token is a secret

#

If you want, do Part 1 only first, then tell me:

your bot username (not the token)
what openclaw channels status --probe shows

and I’ll walk you through the next exact step.

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

pearl hound Apr 19, 2026, 8:53 PM

#

I stopped the install and started over. I'll post thje next prompt that coem iup and can we proceed from there?

karmic ravenBOT Apr 19, 2026, 8:54 PM

#

Yep, absolutely. Post the next prompt exactly as it appears and I’ll walk you through it step by step.

Also, please paste this once so I know what version you’re on:

openclaw --version

One important thing, if a screen shows a token / API key / secret, redact that part before posting it here.

pearl hound Apr 19, 2026, 8:59 PM

#

i'm not on a version yet I'm in the middle of installing version 4.12. I am at this step now. I have an openrouter api key which i entered in the previous step: Default model
│ ● Keep current (openrouter/auto)
│ ○ Enter model manually
│ ○ openrouter/ai21/jamba-large-1.7
│ ○ openrouter/allenai/olmo-3.1-32b-instruct
│ ○ openrouter/amazon/nova-2-lite-v1
│ ○ openrouter/amazon/nova-lite-v1
│ ○ openrouter/amazon/nova-micro-v1
│ ○ openrouter/amazon/nova-premier-v1
│ ○ openrouter/amazon/nova-pro-v1
│ ○ openrouter/anthropic/claude-3-haiku
│ ○ openrouter/anthropic/claude-3.5-haiku
│ ○ openrouter/anthropic/claude-3.7-sonnet
│ ○ openrouter/anthropic/claude-3.7-sonnet:thinking
│ ○ openrouter/anthropic/claude-haiku-4.5
│ ○ openrouter/anthropic/claude-opus-4
│ ○ openrouter/anthropic/claude-opus-4.1
│ ○ openrouter/anthropic/claude-opus-4.5
│ ○ openrouter/anthropic/claude-opus-4.6
│ ○ openrouter/anthropic/claude-opus-4.6-fast
│ ○ openrouter/anthropic/claude-sonnet-4
│ ○ openrouter/anthropic/claude-sonnet-4.5
│ ○ openrouter/anthropic/claude-sonnet-4.6
│ ○ openrouter/arcee-ai/trinity-large-preview:free
│ ○ openrouter/arcee-ai/trinity-large-thinking
│ ...

karmic ravenBOT Apr 19, 2026, 9:01 PM

#

Yep, for fastest/easiest finish, choose:

Keep current (openrouter/auto)

So here, do this:

leave the top option selected
press Enter

That’s the right “don’t get stuck here” choice. You can change the model later after setup is finished.

This step is just picking the default model. It is not permanent.

Docs:
https://docs.openclaw.ai/concepts/models
https://docs.openclaw.ai/concepts/models#model-discussions-community-notes

#

After you press Enter, post the next prompt and we’ll keep going.

pearl hound Apr 19, 2026, 9:02 PM

#

I chose telegram for this step: Select channel (QuickStart)
│ ○ Feishu/Lark (飞书)
│ ○ Google Chat (Chat API)
│ ○ Nostr
│ ○ Microsoft Teams (Bot Framework)
│ ○ Mattermost (plugin)
│ ○ Nextcloud Talk (self-hosted)
│ ○ Matrix (plugin)
│ ○ BlueBubbles (macOS app)
│ ○ LINE (Messaging API)
│ ○ Zalo (Bot API)
│ ○ Zalo (Personal Account)
│ ○ Synology Chat (Webhook)
│ ○ Tlon (Urbit)
│ ○ Discord (Bot API)
│ ○ iMessage (imsg)
│ ○ IRC (Server + Nick)
│ ○ QQ Bot
│ ○ Signal (signal-cli)
│ ○ Slack
│ ● Telegram (Bot API) (recommended · configured)
│ ○ Twitch (Chat)
│ ○ WhatsApp (QR link)
│ ○ Skip for now

#

I"m now at this step and i have a bravesearch api key:Search provider
│ ● Brave Search (Structured results · country/language/time filters · configured)
│ ○ Exa Search
│ ○ Firecrawl Search
│ ○ Gemini (Google Search)
│ ○ Grok (xAI)
│ ○ Kimi (Moonshot)
│ ○ Ollama Web Search
│ ○ Perplexity Search
│ ○ SearXNG Search
│ ○ Tavily Search
│ ○ Skip for now

#

Ok I'm at this step this is where things usually go wrong so i am going to need close guidance from here on. How do you want to hatch your bot?
│ ● Hatch in TUI (recommended)
│ ○ Open the Web UI
│ ○ Do this later
└

karmic ravenBOT Apr 19, 2026, 9:07 PM

#

Yep, this time let’s not open the TUI yet.

For easiest / least confusing path, choose:

Do this later

Exact keys

press the Down Arrow twice
highlight Do this later
press Enter

Why: last time the TUI opened and it felt like something went wrong, but it was really just another interface.
If we choose Do this later, the installer can finish cleanly first, then we connect Telegram step by step after.

If it accidentally opens the TUI anyway, press:

#

Ctrl+D

Once you hit Do this later, paste the next screen/prompt here and I’ll guide the next exact click/key.

pearl hound Apr 19, 2026, 9:09 PM

#

It say "Onboarding complete. Use the dashboard link above to control OpenClaw." what is my next step after this

karmic ravenBOT Apr 19, 2026, 9:09 PM

#

Nice, that means the install itself is done 🎉

You can ignore the dashboard for a minute.
Your next step is to create your Telegram bot.

Do only this next

Open Telegram
- if you do not have it yet, install it and sign in first
Search for @BotFather
- make sure it is exactly BotFather
Open that chat and press Start
Send this:

#

/newbot

When BotFather asks for a name
- pick any name you want
- example: Spearmin Assistant
When BotFather asks for a username
- it must end in bot
- example: spearmin_helper_bot
BotFather will give you a token
- copy it somewhere safe
- do not paste the token here

Then come back here and tell me:

#

“I have the Telegram bot token.”

Then I’ll give you the next exact command.

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

pearl hound Apr 19, 2026, 9:10 PM

#

no lets verify we are truly up and running in the dashboard first

karmic ravenBOT Apr 19, 2026, 9:11 PM

#

Yep, good call. Let’s verify the dashboard first.

Do these steps

1. Open the dashboard

In your terminal, run:

openclaw dashboard

That should open the browser for you.

If it does not open automatically, copy the link it prints and open it manually.
Local installs are usually here:

#

http://127.0.0.1:18789/

2. If the dashboard asks for auth

If it asks for a token/password, in the terminal run:

openclaw config get gateway.auth.token

Then paste that token into the dashboard and click Connect.

If you do not see where to paste it, look in:

#

Overview → Gateway Access

That card has the auth fields.

3. Verify from the terminal too

In another terminal tab/window, run:

openclaw status

What you want to see is basically:

Runtime: running
RPC probe: ok

#

When you reply

Paste either:

what the dashboard shows, or
the output of openclaw status

and I’ll tell you if you’re fully up and running.

Docs:
https://docs.openclaw.ai/web/dashboard
https://docs.openclaw.ai/help/faq#how-do-i-open-the-dashboard-after-onboarding

pearl hound Apr 19, 2026, 9:13 PM

#

got this when I opend the dashboard: Hello! I'm awake and ready to help. What can I do for you today?

karmic ravenBOT Apr 19, 2026, 9:13 PM

#

Perfect, that is the success message.

It means:

the dashboard opened
OpenClaw is running
the bot is awake and connected

So yes, you are up and running now. 🎉

If you want one extra sanity check, run:

openclaw status

But honestly, the dashboard reply you got is already a very good sign.

#

Next step

Now we create your Telegram bot.

Do this next:

open Telegram
search for @BotFather
press Start
send:

/newbot

choose a bot name
choose a username that ends in bot

#

When BotFather gives you the token, do not paste it here.
Just reply:

“I have the Telegram token.”

Then I’ll give you the exact next command.

pearl hound Apr 19, 2026, 9:14 PM

#

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ Telegram │ ON │ OK │ token config (8711…S6sY · len 46) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Sessions
┌────────────────────────────────────────────────────────────────┬────────┬─────────┬─────────────────┬────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├────────────────────────────────────────────────────────────────┼────────┼─────────┼─────────────────┼────────────────┤
│ agent:main:main │ direct │ 38m ago │ openrouter/auto │ 11k/200k (5%) │
└────────────────────────────────────────────────────────────────┴────────┴─────────┴─────────────────┴────────────────┘

FAQ: https://docs.openclaw.ai/faq
Troubleshooting: https://docs.openclaw.ai/troubleshooting

Update available (npm 2026.4.15). Run: openclaw update
Next steps:
Need to share? openclaw status --all
Need to debug live? openclaw logs --follow
Need to test channels? openclaw status --deep
warren@Warrens-Mac-mini ~ %

karmic ravenBOT Apr 19, 2026, 9:14 PM

#

Nice, this looks good. Telegram is configured and OK. You’re very close now.

Next step, test the bot in Telegram

Open Telegram
Find your bot
Send it:

hi

What should happen

Most likely, Telegram will send back a pairing code.

If that happens, go back to your terminal and run:

#

openclaw pairing list telegram

Then approve it with:

openclaw pairing approve telegram <CODE> --notify

Replace <CODE> with the code you got.

After that, send your bot hi again.

If the bot replies normally right away

#

That is also fine. It means you’re already through the gate.

For now

Ignore the update message. We can do that later.

When you send hi to the bot, tell me exactly what Telegram sends back, and I’ll guide the next step.

pearl hound Apr 19, 2026, 9:16 PM

#

nope the bot didnt reply

karmic ravenBOT Apr 19, 2026, 9:16 PM

#

Okay, that narrows it down. The install itself looks fine, so now we’re debugging the Telegram inbound step.

Please run these two commands and paste the output:

openclaw --version
openclaw pairing list telegram

Why

pairing list telegram checks whether Telegram created a pending pairing request
if it did, we can approve it immediately
if it did not, we’ll check the logs next

If pairing list telegram comes back empty, the next command will be:

#

openclaw logs --follow

Then you’ll send the bot hi again once, and we’ll watch what reaches OpenClaw.

pearl hound Apr 19, 2026, 9:18 PM

#

OpenClaw 2026.4.12 (1c0672b) /warren@Warrens-Mac-mini ~ % openclaw pairing list telegram

🦞 OpenClaw 2026.4.12 (1c0672b) — I can't fix your code taste, but I can fix your build and your backlog.

No pending telegram pairing requests.
warren@Warrens-Mac-mini ~ %

karmic ravenBOT Apr 19, 2026, 9:18 PM

#

Good, that tells us something important:

Telegram is configured, but your message is not reaching OpenClaw yet.

Let’s do the next exact check.

Step 1

In your terminal, run:

openclaw logs --follow

Step 2

While that is running, go to Telegram and do both of these in your bot chat:

press Start if you see a Start button

#

send:

/start

then send:

hi

Step 3

Copy the new log lines that appear after that and paste them here.

That will tell us whether:

Telegram is reaching the gateway at all

#

pairing is being created but not shown
or the bot token / transport is connected but not receiving inbound events

If nothing new appears in the logs at all, tell me that too.

pearl hound Apr 19, 2026, 9:20 PM

#

2device=761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write client=cli conn=ba1cca66-8266-44c8-ad48-dcd2648cd080
21:20:35+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
21:20:35+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
gateway connect failed: GatewayClientRequestError: pairing required
21:20:35+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"pairing-required","handshake":"failed","durationMs":32,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"8fadbe49-ef15-4adf-8a0f-847bbd9ae694","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":49849,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:49849->127.0.0.1:18789","deviceId":"761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542","requestId":"8d851f8f-9829-459e-bbc6-8e0782dfe8f7","reason":"scope-upgrade"} closed before connect conn=ba1cca66-8266-44c8-ad48-dcd2648cd080 peer=127.0.0.1:49849->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1008 reason=connect failed
21:20:36+00:00 warn gateway {"subsystem":"gateway"} security audit: device access upgrade requested reason=scope-upgrade device=761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write client=cli conn=6b9ec043-75a1-49f7-832e-c0f52a360291
21:20:36+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
21:20:36+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
g

karmic ravenBOT Apr 19, 2026, 9:21 PM

#

Aha, we found it.

This is not a Telegram-token problem.
It’s a local device scope-upgrade pairing problem.

Your log says:

pairing required
reason":"scope-upgrade"
it even gave a requestId

Fix this now

Run:

#

openclaw devices list

You should see a pending device request.

Then approve it with:

openclaw devices approve <requestId>

Use the exact requestId from devices list.

Important

Don’t use --latest for the real approval.
That only previews. Use the full request id.

#

After approving

Run:

openclaw status

Then refresh the dashboard.

After that, try your Telegram bot again with:

/start

#

or

hi

If you want, paste the output of:

openclaw devices list

and I’ll point to the exact line to approve.

Docs:
https://docs.openclaw.ai/cli/devices
https://docs.openclaw.ai/gateway/troubleshooting

pearl hound Apr 19, 2026, 9:26 PM

#

Direct scope access failed; using local fallback.
Approved 761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542 (cddc4690-ce86-42ec-bc14-71079975a70f)
w

karmic ravenBOT Apr 19, 2026, 9:26 PM

#

Nice, that part is fixed.
“Approved …” is the important bit. The local fallback note is okay.

Next steps

Run:

openclaw status

Refresh the dashboard in your browser
Go back to Telegram and send your bot:

#

/start

If nothing happens, send:

hi

If it still does not reply

Run this again:

openclaw logs --follow

#

Then send /start once more and paste the new log lines.

You’re actually making good progress here, we knocked out the pairing issue.

pearl hound Apr 19, 2026, 9:29 PM

#

Listen it woul be better if you could only send me 1 step at a time wait for my respone then send me the next step after evaluating y response. otherise thisng get off track. Your currently sending me 3 steps at once

karmic ravenBOT Apr 19, 2026, 9:29 PM

#

You’re right. My bad. One step at a time from here.

Step 1

In Telegram, send your bot exactly this:

/start

Then tell me exactly what happens, even if the answer is just “nothing happened.”

pearl hound Apr 19, 2026, 9:31 PM

#

Ok I am in my new bot's chat session and i sent it that command and it did nothing

karmic ravenBOT Apr 19, 2026, 9:31 PM

#

Good, that helps.

Step 2

In your terminal, run:

openclaw logs --follow

Then tell me when it’s running.

pearl hound Apr 19, 2026, 9:33 PM

#

21:25:56+00:00 warn gateway {"subsystem":"gateway"} security audit: device access upgrade requested reason=scope-upgrade device=761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write client=cli conn=fa4c42af-81ff-44c7-8f60-e410c89dde3d
21:25:56+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
21:25:56+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
21:25:56+00:00 info Direct scope access failed; using local fallback.
21:25:56+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"pairing-required","handshake":"failed","durationMs":41,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"bf9bd72b-11e1-4330-b22d-5ef0d02a172c","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":50104,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:50104->127.0.0.1:18789","deviceId":"761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542","requestId":"cddc4690-ce86-42ec-bc14-71079975a70f","reason":"scope-upgrade"} closed before connect conn=fa4c42af-81ff-44c7-8f60-e410c89dde3d peer=127.0.0.1:50104->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1008 reason=connect failed
21:25:56+00:00 info Approved 761f4622f91e8a478b7ff3bb9839c96c00a3573a802914cb3b0b47ac975e1542 (cddc4690-ce86-42ec-bc14-71079975a70f)
21:31:44+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 260ms conn=528d19f9…606b id=52915435…5d4e
Log tail truncated (increase --max-bytes).

karmic ravenBOT Apr 19, 2026, 9:34 PM

#

Perfect. Those lines are old, not the Telegram message yet.

Step 3

Leave openclaw logs --follow running, then send your Telegram bot:

/start

one more time.

Then tell me whether any brand new log lines appear right after you send it.

pearl hound Apr 19, 2026, 9:35 PM

#

the log didnt move

karmic ravenBOT Apr 19, 2026, 9:36 PM

#

Got it. That means Telegram is not reaching the gateway yet.

Step 4

In your terminal, run:

openclaw channels status --probe

Then paste the Telegram part of the output.

pearl hound Apr 19, 2026, 10:38 PM

#

Actually I got the pairing request this time after typing hi

karmic ravenBOT Apr 19, 2026, 10:39 PM

#

Nice, that’s progress.

Step 5

In your terminal, run:

openclaw pairing list telegram

Then paste exactly what it shows.

pearl hound Apr 19, 2026, 10:41 PM

#

Code │ telegramUserId │ Meta │ Requested │
├──────────┼─────────────────┼──────────────────────────────────────────────────────────────┼──────────────────────────┤
│ SLG6NT8E │ 8603700526 │ {"firstName":"Warren","lastName":"S","accountId":"default"} │ 2026-04-19T21:40:47.910

karmic ravenBOT Apr 19, 2026, 10:41 PM

#

Perfect.

Step 6

Run this exact command:

openclaw pairing approve telegram SLG6NT8E --notify

Then tell me exactly what it prints.

pearl hound Apr 19, 2026, 10:42 PM

#

[openclaw] Failed to start CLI: Error: No pending pairing request found for code: SLG6NT8E
at Command.<anonymous> (file:///opt/homebrew/lib/node_modules/openclaw/dist/pairing-cli-CFmdkTGe.js:108:24)
at async Command.parseAsync (/opt/homebrew/lib/node_modules/openclaw/node_modules/commander/lib/command.js:1122:5)
at async runCli (file:///opt/homebrew/lib/node_modules/openclaw/dist/run-main-CqxhDA30.js:463:4)

karmic ravenBOT Apr 19, 2026, 10:42 PM

#

Got it. That usually means the code changed or got consumed/replaced.

Step 7

Run this again:

openclaw pairing list telegram

Then paste the new code it shows.

pearl hound Apr 19, 2026, 10:43 PM

#

No pending telegram pairing requests.

karmic ravenBOT Apr 19, 2026, 10:44 PM

#

Okay, we need to generate a fresh one.

Step 8

In Telegram, send your bot:

hi

one more time.

Then tell me whether Telegram shows you a new pairing code.

pearl hound Apr 19, 2026, 10:45 PM

#

this is the code 7MYPZWC8

karmic ravenBOT Apr 19, 2026, 10:45 PM

#

Great.

Step 9

Run this exact command:

openclaw pairing approve telegram 7MYPZWC8 --notify

Then tell me exactly what it prints.

pearl hound Apr 19, 2026, 10:45 PM

#

Approved telegram sender 8603700526.

karmic ravenBOT Apr 19, 2026, 10:46 PM

#

Perfect.

Step 10

Go back to Telegram and send your bot:

hi

Then tell me exactly what the bot does.

pearl hound Apr 19, 2026, 10:46 PM

#

Hello! How can I help you today?

karmic ravenBOT Apr 19, 2026, 10:47 PM

#

Perfect, that means it’s working 🎉

Your Telegram bot is now connected and replying.

If you want one simple next step, send it:

what can you do?

Glad we got you to the finish line.

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for future users.

pearl hound Apr 19, 2026, 10:48 PM

#

Ok as a last quick question how do i get it to start the identity questions like who am i and what is my purpose etc

#installing and stuck on hat my bot ste

Step-by-step

If you want Telegram groups later

If it doesn’t respond

Important

Next steps for Telegram

Quick sanity check

Where you are right now

Part 1, create your Telegram bot

Part 2, connect that Telegram bot to OpenClaw

Part 3, approve yourself in Telegram

Part 4, test it

Two common gotchas

Exact keys

Do only this next

Then come back here and tell me:

Do these steps

1. Open the dashboard

2. If the dashboard asks for auth

3. Verify from the terminal too

When you reply

Next step

Next step, test the bot in Telegram

What should happen

If the bot replies normally right away

For now

Why

Step 1

Step 2

Step 3

Fix this now

Important

After approving

Next steps

If it still does not reply

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10