#Can someone explain to me how to set this up?
1 messages · Page 1 of 1 (latest)
You’re not crazy, the Windows setup is where a lot of people get stuck.
Short honest answer:
- Yes, no API keys is possible
- No, OpenClaw itself is not a single "$300/month" plan
- Billing comes from the model provider you choose, not from OpenClaw
For what you want, I’d do this:
-
Use WSL2 on Windows, not native Windows if you can
Docs: https://docs.openclaw.ai/platforms/windows -
Inside WSL2 / Ubuntu, install OpenClaw:
curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon
- In onboarding, choose a no-API-key auth route:
- OpenAI Codex subscription
https://docs.openclaw.ai/providers/openai - Claude CLI reuse if you already have Claude set up
https://docs.openclaw.ai/providers/anthropic
- OpenAI Codex subscription
Important bit: if you want no API keys, the closest fit is a subscription-backed login like Codex or Claude CLI.
If you want a strict spend cap, that usually lives on the provider side, not inside OpenClaw. Cost docs: https://docs.openclaw.ai/reference/api-usage-costs
If you already installed it and it’s failing, paste these 3 outputs and I’ll tell you the exact next step:
openclaw --version
openclaw status
openclaw models status
Also, for Etsy print-on-demand automation, yes, parts of that can be automated, but first get OpenClaw running cleanly, then do the automation layer second.
Windows PC I just can’t get past the set up with the anthropic oauth
Got it. I wouldn’t keep fighting the Anthropic token/OAuth path on Windows.
For Anthropic without an API key, the docs now prefer Claude CLI reuse instead.
If OpenClaw is running on your Windows machine, do this on the same machine that runs OpenClaw, ideally inside WSL2:
openclaw --version
claude --version
claude auth login
openclaw models auth login --provider anthropic --method cli --set-default
openclaw models status
Then rerun onboarding and choose Claude CLI, not the Anthropic token/OAuth option:
openclaw onboard
I’d strongly recommend WSL2 if you’re on native Windows right now:
https://docs.openclaw.ai/platforms/windows
Relevant docs:
If you paste:
openclaw --version- which one you’re using, native Windows or WSL2
- the exact error from
openclaw models auth login --provider anthropic --method cli --set-default
…I can help you line by line.
I haven’t set it up at all cause I could never figure it out
Okay, that actually helps. If you’re starting from zero, then stop trying Anthropic OAuth for now.
The simplest Windows path is:
1) Install WSL2
In PowerShell as Admin:
wsl --install -d Ubuntu
If Windows asks, reboot.
2) Open Ubuntu and install OpenClaw
In the Ubuntu window:
curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon
3) For no API keys
During onboarding, the easiest subscription-style path is usually:
- OpenAI Codex subscription, if that’s the subscription you have/want
https://docs.openclaw.ai/providers/openai
If you specifically want Anthropic, do Claude CLI later, not the Anthropic token/OAuth route:
https://docs.openclaw.ai/providers/anthropic
Windows docs:
So the short version is:
- Use WSL2
- Install OpenClaw inside Ubuntu
- Do not start with Anthropic OAuth
- Get one subscription provider first, then connect OpenClaw to that
If you want, reply with just:
I installed WSL- or the first error message you get
and I’ll walk you through the next step exactly.
I have no idea what you’re talking about
No worries. Plain English:
- OpenClaw is the app/tool
- ChatGPT or Claude is the AI service it connects to
- So you need one paid AI subscription somewhere, OpenClaw is not one single $300/month service by itself
Let’s do one tiny step at a time.
Step 1
On your Windows computer:
- Click Start
- Type PowerShell
- Right-click PowerShell
- Click Run as administrator
- Paste this:
wsl --install
- Press Enter
That makes Windows ready for the easier OpenClaw setup.
When it finishes, reply with exactly what happened, and I’ll give you Step 2 only.
Also, quick question: do you already pay for ChatGPT or Claude?
I was gonna just pay for the claude I haven’t yet. Cause apparently it’s like the best one you can get.
Yep, that’s a workable plan.
If you want no API keys, then:
- buy Claude
- install OpenClaw
- log Claude into OpenClaw
So let’s keep it simple and do this in order.
Right now, do this first on Windows:
Open PowerShell as Administrator and run:
wsl --install
Don’t worry about the Claude login part yet. We’ll do that after Windows finishes this step.
So for now:
- run
wsl --install - tell me what it says
If it worked, I’ll give you the next single step.
Am I able to send you pictures of my screen?
Yes, absolutely, send screenshots.
That’ll probably be the easiest way here.
If you can, send:
- the full window
- the error message
- and the part where you got stuck
Just hide/blur any passwords, tokens, QR codes, or personal info first.
OK OK so what’s the first step?
First step:
- Click Start
- Type PowerShell
- Right-click PowerShell
- Click Run as administrator
- Paste this:
wsl --install
- Press Enter
That’s it for step 1.
If anything weird pops up, send a screenshot and I’ll tell you exactly what to click next.
Is it true if I use Claude oauth I can get banned
Short answer: I would not assume you’ll get banned.
OpenClaw’s current docs say Anthropic told them Claude CLI reuse is allowed again, so OpenClaw treats that path as okay unless Anthropic changes policy later.
But two important details:
- the preferred no-API-key Anthropic path is Claude CLI reuse
- if you want the safest / clearest billing path, API keys are still the more predictable option
So:
- Claude CLI = the current no-key Anthropic route OpenClaw supports
- API key = cleaner and more predictable
- nothing is something I’d promise is “ban-proof forever”
Docs:
If you want, I can tell you the lowest-risk setup for your case in plain English.
But I don’t want the API key so is the CLI still like allowed?
According to the current OpenClaw docs, yes, Claude CLI is treated as allowed.
More exactly:
- OpenClaw says Anthropic told them Claude CLI reuse is allowed again
- so if you want no API key, Claude CLI is the Anthropic route OpenClaw supports
- I just can’t promise Anthropic will never change their policy later
So for your goal:
- No API key
- Use Claude
- Use Claude CLI
That is the current path.
If you want, I can give you the simple beginner setup for that path, with no jargon, one step at a time.
So what’s the first steps to setting it up on my Windows PC
Here’s the easiest Windows setup path if you want Claude and no API key:
Step 1
Open PowerShell as Administrator and run:
wsl --install
If it asks you to restart, restart.
Step 2
After that, open the new Ubuntu app on your computer.
Step 3
Inside Ubuntu, run:
curl -fsSL https://openclaw.ai/install.sh | bash
Step 4
Then run:
openclaw onboard --install-daemon
That gets OpenClaw installed the right way on Windows.
After that, we do the Claude login part.
If you want, do Step 1 right now, and send me a screenshot of what happens.
So why don’t you do after I restart it?
Yep, exactly.
After you restart:
- open Ubuntu
- wait for it to finish loading
- send me a screenshot of what it shows
Then I’ll give you the next step.
I can’t click your computer for you from here, but I can walk you through it step by step.
It says enter new unix username
Perfect, that’s normal.
Type a username you want to use for Ubuntu, for example:
- your first name
- or a simple nickname
Just make sure:
- no spaces
- keep it simple, like
johnoradolf
Then press Enter.
After that it will ask for a password.
When you type the password, nothing will show on screen. That is normal.
Type the password, press Enter, then type it again.
When that’s done, tell me what it says next.
OK now I got some MMA Clem at desktop Numbers and letters and then there’s a money sign
Yep, that’s perfect, you’re in the right place.
That money sign $ means Ubuntu is ready for the next command.
Now copy and paste this exactly, then press Enter:
curl -fsSL https://openclaw.ai/install.sh | bash
Then wait for it to do its thing.
When it changes or asks you something, send me a screenshot or tell me what it says.
It made me put in a password and now it says installing Lennox build tools and then it’s like Meg G plus plus can make Python three and now it says build tools installed
Nice, that’s actually good, it sounds like it’s working. 👍
Those build tools are normal.
Next:
- if the terminal is still doing stuff, just wait
- if you are back at the
$again, run this:
openclaw onboard --install-daemon
Then tell me what it says next.
If it says openclaw: command not found, tell me that exact message and I’ll fix it.
It says two over three installing open claw and then some stuff under it
Perfect, that means it’s still installing. You’re good.
Right now:
- do not type anything
- do not close the window
- just let it finish
When you see the $ again, send me a screenshot or tell me, and I’ll give you the next command.
It’s on this I understand this is a personal body
User requires lockdown continue yes or no
Yep, for your setup, choose yes.
It’s basically saying:
“This is meant to be your own personal assistant, not a public/shared bot.”
Since you’re setting it up for yourself, type:
yes
then press Enter.
After that, tell me what the next screen says.
Quickstart.
That’s the easier option, and it’s the right one for you right now.
So choose Quickstart, then tell me what the next screen says.
Model/off provider do we click Anthropic?
Quickstart.
That’s the easy beginner option. Choose that, then tell me what it says next.
It says model/authenticator provider
Yes, click Anthropic.
Since you want Claude and no API key, that’s the right provider.
If the next screen asks how to sign in, send me what the options are and I’ll tell you which one to click.
Yep, on that screen choose:
Anthropic
That is the provider for Claude.
After you click that, tell me what the next choices are.
Yes, choose Claude CLI.
That’s the no API key option for Claude.
Click Claude CLI, then tell me what it says next.
error is not authenticated on this host one cloud off login first then rerun this set up
Claude CLI, not Anthropic setup token.
So choose:
Claude CLI
That’s the better fit for what you want, Claude with no API key.
I did error is not authenticated on this host one cloud off login first then rerun this set up
That’s okay, it just means Claude is not signed in yet.
Do this now in the Ubuntu window:
claude auth login
Then follow the sign-in steps for Claude.
After that finishes, run:
openclaw onboard --install-daemon
again.
If claude auth login gives another error, send me the exact message or a screenshot and I’ll keep walking you through it.
It says Claude command not found
Ah, got it, that means the setup is waiting for Claude to be signed in first.
Do this:
-
Exit the setup for now
- press Ctrl + C once
- you should get back to the normal
$line
-
Then type:
claude auth login
-
Finish the Claude sign-in
-
After that, run:
openclaw onboard --install-daemon
again
So basically:
- leave setup
- log into Claude
- start setup again
If you want, send a screenshot after you press Ctrl + C and I’ll tell you the exact next thing to type.
It won’t let me log into the cloud. It just says it’s that command is not found.
Got it, that means Claude CLI is not installed yet.
In the Ubuntu window, run these one at a time:
corepack enable
then
pnpm add -g @anthropic-ai/claude-code
then
claude auth login
After that, run:
openclaw onboard --install-daemon
again.
If any one of those gives an error, send me the screenshot and I’ll tell you the next move.
Then it said permission denied when I put core pack enable
No worries, let’s use the simpler install command.
In Ubuntu, type this:
npm install -g @anthropic-ai/claude-code
When that finishes, type:
claude auth login
Then after Claude signs in, run:
openclaw onboard --install-daemon
again.
So the order is:
- install Claude
- log into Claude
- rerun OpenClaw setup
If the first command gives an error, send me the screenshot.
That’s fine, ignore corepack enable.
You don’t need it.
Use this instead:
npm install -g @anthropic-ai/claude-code
If that works, then run:
claude auth login
So, just skip the corepack part.
I did the Claude install and PM install and it said added two packages in two seconds
Nice, that means Claude installed. 🎉
Now type this:
claude auth login
Then follow the Claude sign-in steps.
When that finishes, tell me what it says next.
It still says command, not found
Okay, that usually just means Claude installed, but Ubuntu can’t see it yet.
Type this exactly:
export PATH="$(npm prefix -g)/bin:$PATH"
then type:
claude auth login
If that works, we’ll make it permanent after.
If it still says command not found, send me a screenshot of both commands and the output.
It said opening browser to sign in if the browser didn’t open visit this link it didn’t open. Should I go to that link?
Yes, go to that link.
Open it in your normal browser on Windows, then:
- sign in to Claude
- if it gives you a code or sends you back to the terminal, paste that into Ubuntu
- don’t post the code here
When you finish, tell me what the terminal says next.
I need a new link. Is there a way to get a different link?
Yes.
To get a new link, just run this again in Ubuntu:
claude auth login
If it’s still sitting on the old login screen first, press Ctrl + C once, then run:
claude auth login
again.
That should generate a fresh link.
I used an Apple ID to set it up and that’s not an option on here
Ah, okay, that’s probably the issue.
If you signed up with Apple, try Continue with email instead of looking for an Apple button.
Important part:
- if you used your normal email with Apple, use that email
- if you used Hide My Email, use the
@privaterelay.appleid.comemail Apple gave you
So:
- click Continue with email
- enter the email tied to your Claude account
- finish the login from the email they send you
Official help:
https://support.claude.com/en/articles/13189465-logging-in-to-your-claude-account
If you want, send me a screenshot of the login page and I’ll tell you exactly which button to press.
It says Claude Max or pro is required to connect
Yep, that means the free Claude account won’t work for this setup.
For the no API key + Claude CLI route, you need Claude Pro or Max.
So your choices are:
-
Buy Claude Pro or Max
Then rerun:claude auth login -
Use an Anthropic API key instead
No subscription needed, but it’s usage-based billing -
Switch to a different no-key route
Like OpenAI Codex subscription instead of Claude
If you want the simplest path for what you asked for, I’d do option 1 and keep going with Claude.
What do you recommend buying the max probably and it says should I buy the 5X more usage or 20 X more usage?
If you want my straight recommendation, buy Max 5x, not 20x.
Why:
- official Claude pricing currently shows:
- Pro = $20/month
- Max 5x = $100/month
- Max 20x = $200/month
- you’re just getting started
- 20x is more for people using it heavily every day
- 5x gives you a lot more room without going overboard
So for your situation:
- best value / safest start: Max 5x
- cheapest possible start: Pro
- I would not start with 20x
Official refs:
- https://support.claude.com/en/articles/11049762-choosing-a-claude-plan
- https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan
If you buy Max 5x, I can walk you through the next login step right after.
All right, so say by the max 5X and then wanna upgrade to the 20 X more usage is that really easy to do like later on
Yes, that should be easy later.
Anthropic’s help says you can go to:
Settings → Billing → Upgrade to Max
and choose 5x or 20x there.
So if you start with Max 5x and later keep hitting limits, you can move up to 20x.
Official help:
https://support.claude.com/en/articles/11049752-how-do-i-sign-up-for-the-max-plan
https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan
So yep, 5x first, upgrade later if needed is a sensible move.
But like I get it if I upgrade to the Claude on the Claude app, will it automatically go to my claw bot
Yes, if it’s the same Claude account.
Plain English:
- you upgrade your Claude account
- then Claude CLI uses that same account
- then OpenClaw uses Claude CLI on your computer
So it’s not really “sending it to the bot” separately, it’s all tied to the same Claude login.
To be safe, after you upgrade I’d do this once in Ubuntu:
claude auth login
Then rerun:
openclaw onboard --install-daemon
So, short answer: yes, same Claude account = OpenClaw can use it.
I paid for the thing and then it said cloud Claude code would like to connect to your Claude chat account authorize
Yes, if that’s the official Claude / Claude Code sign-in page, click Authorize.
That’s the normal step that connects Claude Code to your Claude account.
After you do that, tell me what the Ubuntu window says next.
I got this link that says paste this in the Claude code so do I do the control C and then paste it
No, don’t do Ctrl + C if it’s waiting for the code.
Just:
- copy the code/link they gave you
- go back to the Ubuntu / Claude Code window
- paste it there
- press Enter
Only use Ctrl + C if you are trying to cancel the login.
So right now, just paste the code into Claude Code.
I don’t think it’s gonna let me unless I do the control C thing
Try this first:
- click inside the Ubuntu window
- paste with right-click
or Ctrl + Shift + V
Sometimes Ctrl + V does not work there.
If it still won’t let you paste, then yes:
- press Ctrl + C once
- run:
claude auth login - get a fresh link/code
- try again
So, try right-click or Ctrl+Shift+V first.
Nothing would work so I clicked control C then pasted that Lincoln and nothing happened. It just said command not found.
?
Do this:
- click the Ubuntu window
- try right-click paste
- if that does not work, press Ctrl + C
- then type:
claude auth login
- press Enter
If you want, send a screenshot of the Ubuntu window right now.
I did that and then it gave me one of those things to link in the browser again I did it. It gave me one of those codes and it won’t let me paste it back into the thing.
If paste is fighting you, just type the code by hand.
Seriously, that’s okay.
Do this:
- click inside the Ubuntu / Claude window
- type the code manually
- press Enter
You do not have to paste it if it won’t let you.
If it still won’t accept the code, send a screenshot of the Ubuntu window and I’ll tell you exactly what’s wrong.
The last thing it says opening browser to sign in if the resident didn’t open visit this link I visited it. I linked my account to it and then I can’t type or nothing into the terminal.
Okay, try this exact order:
- leave the browser page open
- click the Ubuntu window
- press Enter once
- wait 10 seconds
If it then says something like Paste code here, type the code and press Enter.
If nothing changes at all, then:
- press Ctrl + C once
- run:
claude auth login - do the browser step again
If you can, send a screenshot of the Ubuntu window, because I think you’re very close and the exact screen matters here.
I can’t screenshot I can’t do the pictures in the discord chat for some reason, but I have that terminal open and the only thing will let me do is control sea and then I just keep doing the Claude off login and then it does it and then it just won’t let me type the authentication code in.
Okay, stop using claude auth login for a minute.
Try the official Claude Code login flow instead:
- press Ctrl + C
- type:
claude - press Enter
Then follow that flow.
If it says the browser didn’t open, press c to copy the login link, open it in your browser, and keep going.
So, next step is just:
claude
not claude auth login.
Claude’s docs use claude as the normal first-login flow.
Accessing workspace and then it says a file quick safety check. Is this a project or created or when you trust like your own code well-known open source project or weren’t from your team? If not, take a moment to review what’s in this folder first Claude code will be able to read it. Edit it and execute files here.
That’s just a safety warning.
It means Claude can read and edit files in the folder you’re currently in.
If this is:
- your own computer
- your own Ubuntu folder
- and not some random downloaded project
then it’s okay to continue / trust it.
So for this step, yes, continue.
If you want, after this we can move it into a cleaner folder, but for now you’re okay.
OK now I’m in something called Claude code and it just says welcome back Mac and then it has my email and stuff
Perfect, that means Claude Code is logged in now. 🎉
Next:
- leave Claude Code
- press Ctrl + C
- then run:
openclaw onboard --install-daemon
again
- choose:
- Quickstart
- Anthropic
- Claude CLI
You’re actually past the hardest part now.
It says NODE no such file or directory
Okay, let’s check the two versions.
Type these one at a time:
node -v
then
openclaw --version
and tell me exactly what each one says.
That will tell us whether it’s a Node path problem or an OpenClaw problem.
Command NODE is available in the following places the command could not be located because/US R/BIN/BIN is not included in the path environment variable node command, not found
Good, we found the problem, your PATH is broken.
Copy and paste this exactly:
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH"
Then run these:
node -v
and
openclaw --version
If those start working, then run:
openclaw onboard --install-daemon
again.
We can make it permanent after, but first let’s get it working right now.
I did all that then it said error unknown command on board did you mean on board?
Yep, it has to be one word:
openclaw onboard --install-daemon
onboard
not on board
Copy and paste that exact line.
I think I accidentally put an E in it
Yep, no problem 😄
Use this exact command:
openclaw onboard --install-daemon
Just copy and paste that whole line exactly.
Now I came up with that. I understand this is personal by default in a multi shared experience lockdown continue.
I did all the set up to anthropic and now it’s making me pick a default model for Claude
Yep, that’s the same safety message as before.
For your own personal setup, choose:
yes
then continue.
Pick the strongest / main Claude option it shows.
For your setup, I would not pick a mini / cheap / fast-only variant right now.
So:
- choose the main full Claude
- avoid the smallest / lightest one
If you want, type the exact choices it shows and I’ll tell you which one to click.
Yes, if it already says Opus, I’d keep that one.
That’s the kind of strong default you want for this setup.
Yep, keep that.
claude-cli/claude-opus-4-7 is a good choice for your default.
Now it says selected channel and then it’s like Google chat Microsoft teams, Zalo, discord iMessage WhatsApp telegram
I would skip channels for now if it lets you.
That’s the easiest path.
Get OpenClaw working first, then add Discord / Telegram / whatever later.
So:
- choose Skip if you see it
- if there is no skip, tell me what the options are and I’ll guide you
You can, I just wouldn’t add all of them right now.
Best move:
- pick one first
- get it working
- add the others later
If you want the easiest one first, I’d go Telegram.
If the one you actually want is Discord, then choose Discord.
So, pick one channel only for now.
How do I want to provide the telegram bot token? Enter the telegram, bot token or use external secret provider
That’s fine, but I’d still do them one at a time.
My recommendation:
- Telegram first
- Discord second
Telegram is usually the easier one to get working first.
So if the setup is asking right now, choose Telegram first.
Choose:
Enter the Telegram bot token
That’s the simple option.
External secret provider is the advanced option, you do not need that right now.
How do I get to telegram bot token? I don’t even know what that is
No worries, here’s the simple version:
To get a Telegram bot token:
- open Telegram
- search for @BotFather
- open that chat
- type:
/newbot - follow the prompts
- pick a bot name
- pick a bot username
- BotFather will give you a long code, that is the bot token
Then paste that token into the OpenClaw setup.
Important: do not post the token here in Discord. Keep it private.
Docs:
https://docs.openclaw.ai/channels/telegram
If you want, I can walk you through the BotFather part too.
I think I got it does like the code start with a bunch of numbers
Yep, that sounds right.
A Telegram bot token usually looks like:
some numbers
then a colon :
then a long mix of letters and numbers
So if it looks like that, you probably got the right thing.
Do not paste it here.
Just paste it into the OpenClaw setup.
So I pasted it in and now wants me to pick a search provider
If you want no API keys, choose:
DuckDuckGo
That’s the simple no-key search option.
So for this step:
- pick DuckDuckGo
- if there’s a Skip option and you want to move faster, that’s okay too
But if you want search working right away, DuckDuckGo.
I don’t care how long it takes. I want the best one.
If you want the best search provider, pick Brave.
Important catch:
- Brave = better / more reliable, but needs one API key
- DuckDuckGo = no API key, but it’s the more basic / less reliable option
So the honest answer is:
- if you want best, choose Brave
- if you want no extra key, choose DuckDuckGo
Docs:
Does it cost money for the brave
Yes, technically, but it has free credit.
According to the docs:
- Brave gives $5/month in free credit
- Brave Search costs $5 per 1,000 searches
- so that free credit covers about 1,000 searches per month
So:
- it can cost money
- but for light use, you may stay inside the free credit
- and you can set a usage limit in Brave so it doesn’t surprise you
I want one I can just pay monthly. I don’t want to use API’s.
Got it, then don’t use Brave.
For your AI, your Claude monthly plan is the no-API-key part.
For search, if you don’t want APIs, choose:
DuckDuckGo
So your setup should be:
- Claude monthly plan for the brain
- DuckDuckGo for search
- no Brave API
That’s the best fit for what you want.
I don’t care I want the best one I can get, but I wanna know how much I’m gonna spend a month on it
If you want the best setup and also want to know the monthly spend, here’s the clean version:
Option A, best without extra API billing
- Claude Max 20x = $200/month
- DuckDuckGo search = $0
- Total: about $200/month
Option B, best overall
- Claude Max 20x = $200/month
- Brave Search = about $0 to $5/month for light use, because Brave includes $5/month free credit
- Total: about $200 to $205/month at normal usage
(more only if you go past the free credit)
My recommendation
If you want:
- best while keeping cost simple → Claude Max 20x + DuckDuckGo
- best overall quality → Claude Max 20x + Brave, but set a spending cap in Brave
So if your budget is $300/month, either of those is safely inside it.
So how much am I gonna play just for thev brave search like under $10. You think I feel like I want to use this thing a lot like I wanna have multiple sub agents.
Yeah, under $10 is very realistic for Brave search.
Based on Brave’s pricing:
- first 1,000 searches/month are basically covered by the $5 free credit
- around 2,000 searches/month would be about $5
- around 3,000 searches/month would be about $10
So if you’re asking:
“Can I use Brave a lot and still keep it under $10?”
Yes, probably, especially if you set a spending cap.
Important part:
- subagents only cost Brave money when they actually do web searches
- they do not burn Brave money just for existing
So my recommendation:
- use Brave
- set the Brave usage cap to $10
- then you can try it hard without surprise charges
That’s honestly a pretty safe move.
So how do I get the API key?
For the Brave API key:
- go to https://brave.com/search/api/
- make a Brave Search API account
- choose the Search plan
- generate an API key
- copy that key
- paste it into the OpenClaw setup
Do not paste the key here in Discord.
That key is just for Brave search, not for Claude.
Search Google_places_API_keyboard got places
Not Google Places.
You want a Brave Search API key.
Go here:
Then:
- make the Brave Search account
- pick the Search plan
- generate the API key
- paste that into OpenClaw
So, not Google, Brave.
How should I hatch my bot in Tui or Web ui
Web UI.
That’s the easier choice for you.
- Web UI = browser, easier to understand
- TUI = terminal, more technical
So for this step, pick Web UI.
OK, I clicked Web UI and then it said on boarding complete useless dashboard link above to control open claw
Perfect, that means you’re basically in 🎉
Now:
- open the dashboard link it printed
- if it isn’t clickable, copy and paste it into your browser
- that should open the OpenClaw Web UI
If the page asks for a Gateway Token or Password, use the one you set during onboarding.
Tell me what the page shows after you open it.
It says Gateway dashboard and then it’s asking unauthorized gateway token missing
That just means the dashboard needs your Gateway Token.
In the Ubuntu window, run:
openclaw config get gateway.auth.token
Then:
- copy the token it prints
- go back to the dashboard
- paste it into Gateway Token
- click Connect
If that command prints nothing, then run:
openclaw doctor --generate-gateway-token
and then run:
openclaw config get gateway.auth.token
again.
Do not paste the token here in Discord.
But I have I’m in this thing like I can talk to it on my browser or something
Yep, that’s it, that’s the Web UI.
If you can:
- open it in your browser
- type a message
- and it replies
then OpenClaw is working 🎉
So right now, try sending it a simple message like:
hello
If it answers, you’re in.
Then after that, we can do the extra stuff like Telegram and Discord.
I want to do the Telegram
Perfect, let’s do Telegram next.
Step 1
Open Telegram and search for your bot.
Then:
- open the chat with your bot
- tap Start
- send it a message like hello
If Telegram pairing is on, the bot should give you a pairing code.
Step 2
Go back to Ubuntu and run:
openclaw pairing list telegram
If you see the code there, approve it with:
openclaw pairing approve telegram YOURCODE
Replace YOURCODE with the actual code.
If you want, do Step 1 first and tell me what the bot says back.
It doesn’t respond to me through telegram
Okay, no worries, let’s check whether Telegram is actually connected.
In Ubuntu, run these one at a time:
openclaw --version
then
openclaw channels list
Then tell me what the Telegram line says.
That will tell us if Telegram is:
- connected
- missing the bot token
- or not running yet
It said I don’t judge but you’re missing API keys are absolutely judging you then says telegram, default, configured, token, config, enable provide providers plus API keys, Claude oh, no provider usage available
That’s actually helpful.
It sounds like Telegram is configured, so the token part probably worked.
Also, ignore the API key warning for now, that’s not the Telegram problem.
Next, in Ubuntu run:
openclaw gateway status
Then run:
openclaw pairing list telegram
Tell me what those two commands say.
We’re probably down to either:
- the Gateway not running
- or Telegram waiting for pairing/approval
It says I’m the middle wear between your ambition and your attention span then says no pending telegram pairing request request
Good, that means there is no Telegram request reaching the bot yet.
Do this next:
-
in Ubuntu, run:
openclaw gateway restart -
in Telegram, make sure you are messaging your bot, not BotFather
-
tap Start
-
send hello
-
then in Ubuntu, run:
openclaw pairing list telegram
again
If it still says no pending telegram pairing request, then the next thing we’ll check is whether you’re messaging the correct bot username.
Still says no pending in telegram pairing necklace
Okay, next we need to see if OpenClaw is even receiving your Telegram message.
In Ubuntu, run:
openclaw logs --follow
Then, while that is running:
- open your Telegram bot
- send it hello
Then watch the Ubuntu window.
Tell me if anything new appears in the logs.
If nothing appears, then you are probably messaging the wrong bot username or Telegram isn’t reaching your bot at all.
There’s just a bunch of red and yellow things popping up everywhere like just lines of text but a lot of stuff is like air Gateway failed
Okay, stop the logs first:
press Ctrl + C
Then run this:
openclaw gateway status
and send me the exact text it shows, especially the part that says failed.
We need the exact Gateway error now.
It didn’t do anything it says system enabled. I don’t know there’s just a bunch of random stuff. How much longer is this gonna take? I just want my Telegram thing set up so I can go to bed.
I get it, this is dragging and that’s frustrating.
Honest answer, from here it’s either:
-
Fastest path, go to bed:
use the Web UI tonight since that part is working, and finish Telegram tomorrow -
One last quick shot, 2 minutes:
run:openclaw gateway restartwait 10 seconds, then message your Telegram bot again
-
Proper Telegram debugging:
we keep digging through gateway/log output, but that could take a bit longer
My recommendation: use the Web UI tonight and stop here, unless you want to try one last restart first.
If you want the quick last try, do the restart command and tell me if the bot replies after that.
No, I wanna get it finished
Okay, then let’s do the one command most likely to tell us what’s broken.
In Ubuntu, run:
openclaw status --deep
Then copy back only the lines that mention:
- Telegram
- Gateway
- failed
- error
That should tell us exactly why Telegram isn’t replying.
Security audit
Summary: 1 critical · 4 warn · 1 info
CRITICAL Telegram group commands have no sender allowlist
Telegram group access is enabled but no sender allowlist is configured; this allows any group member to invoke /… commands (including skill commands).
Fix: Approve yourself via pairing (recommended), or set channels.telegram.groupAllowFrom (or per-group groups.<id>.allowFrom).
WARN Reverse proxy headers are not trusted
gateway.bind is loopback and gateway.trustedProxies is empty. If you expose the Control UI through a reverse proxy, configure trusted proxies so local-client c…
Fix: Set gateway.trustedProxies to your proxy IPs or keep the Control UI local-only.
WARN Control UI insecure auth toggle enabled
gateway.controlUi.allowInsecureAuth=true does not bypass secure context or device identity checks; only dangerouslyDisableDeviceAuth disables Control UI device…
Fix: Disable it or switch to HTTPS (Tailscale Serve) or localhost.
WARN Insecure or dangerous config flags enabled
Detected 1 enabled flag(s): gateway.controlUi.allowInsecureAuth=true.
Fix: Disable these flags when not actively debugging, or keep deployment scoped to trusted/local-only networks.
WARN Some gateway.nodes.denyCommands entries are ineffective
gateway.nodes.denyCommands uses exact node command-name matching only (for example system.run), not shell-text filtering inside a command payload. - Unknown …
Fix: Use
That security audit is not the Telegram error, it’s just warnings.
We need the Telegram-specific log lines.
In Ubuntu, run this exact command:
openclaw logs | grep -i telegram | tail -20
Then paste back what it shows.
That should give us the actual Telegram problem instead of the general security warnings.
Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ Telegram │ ON │ OK │ token config (8748…rkIM · len 47) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘
Sessions
┌────────────────────────────────────────────────┬────────┬─────────┬─────────────────┬────────────────────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├────────────────────────────────────────────────┼────────┼─────────┼─────────────────┼────────────────────────────────┤
│ agent:main:main │ direct │ 3m ago │ claude-opus-4-7 │ 26k/200k (13%) · 🗄️ 97% cached │
└────────────────────────────────────────────────┴────────┴─────────┴─────────────────┴────────────────────────────────┘
Health
┌──────────┬───────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Status │ Detail │
├──────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
│ Gateway │ reachable │ 119ms │
│ Telegram │ WARN │ failed (404) - Not Found
Okay, we found the actual problem.
Telegram failed (404) - Not Found usually means the Telegram bot token is wrong.
So the good news is:
- your Gateway is up
- OpenClaw is running
- the Telegram token is the broken part
Fix
- go back to @BotFather in Telegram
- get the bot token again
- if needed, use /token
- make sure the token looks like:
- numbers
- then a colon
: - then a long string
- in Ubuntu, run:
openclaw configure - go to Telegram
- replace the old token with the new one
- restart the gateway:
openclaw gateway restart
Then message your bot again.
Do not paste the token here.
You’re actually close, this looks like a bad token, not a full setup failure.
Don’t use that random IP link.
If it turns out to be a real OpenClaw bug, the correct place is:
https://github.com/openclaw/openclaw/issues
For the actual problem here, Telegram failed (404) - Not Found still points to a bad Telegram bot token, so the fix is still:
- get the token again from @BotFather
- update it in OpenClaw
- restart the gateway
That’s much more likely than filing a bug right now.
i need more details on how to maKE A NEW BOT
Yep, here’s the exact Telegram bot creation process:
Make a new Telegram bot
- open Telegram
- search for @BotFather
- open that chat
- type:
/newbot - BotFather will ask for:
- a bot name
example:My Claw Bot - a bot username
example:myclawhelper_bot
- a bot name
Important
The username usually needs to end in bot or _bot.
Examples:
myshophelperbotmyshophelper_bot
After that
BotFather will send you:
- a link to your bot
- a bot token
The token is the long secret code that looks like:
- numbers
- then a colon
: - then more letters/numbers
Then do this
- copy that token
- go back to Ubuntu / OpenClaw
- run:
openclaw configure - update the Telegram bot token
- then restart:
openclaw gateway restart
Do not paste the token here in Discord.
If you want, I can walk you through the BotFather questions one by one while you do it.
IN THE OPENCLAW THING IT SAYS SELCT SECTIONS TO CONFIGURE
Choose:
Channels
Then choose:
Telegram
That’s the section where you replace the bot token.
CONFIG/LINK OR REMOVE CHANNEL CONFIG
Choose:
Configure
Not Link
Not Remove
For Telegram, you want to configure the bot token.
thwn click telegram
Yep, exactly.
Configure → Telegram
Then it should ask for the bot token again.
then modify disable delete config or skip
Choose:
Modify
That lets you replace the Telegram bot token.
Do not choose disable, delete, or skip.
then put new code in and theres no spaces in the api key right
Yep, no spaces.
Just paste the new Telegram token exactly as BotFather gave it to you.
It should be:
- numbers
- then a colon
: - then a long string
- no spaces before or after
And yep, put the new code in there.
then finish?
Yes, finish / save it.
Then do these two things:
-
restart OpenClaw:
openclaw gateway restart -
go to Telegram and message your bot again
If it replies, you’re done. 🎉
config dm acces?
For DM access, choose:
Pairing
That’s the easiest and safest option right now.
So if it asks about DM access:
- pick Pairing
- finish setup
- then message the bot and approve yourself if needed
\
If you’re still on that screen:
DM access = Pairing
then continue / finish.
ehat to do after gateway restart
After openclaw gateway restart:
- open Telegram
- go to your bot
- tap Start
- send hello
Then:
- if the bot replies, great
- if it gives you a pairing code, go back to Ubuntu and run:
then approve itopenclaw pairing list telegram
So the next thing is: message your bot again in Telegram.
i did how long till it responds
Usually within a few seconds.
If nothing happens after about 10 to 15 seconds, go back to Ubuntu and run:
openclaw pairing list telegram
Then tell me what that says.
no pendiung request
Okay, then let’s check whether the new Telegram token fixed the old 404 error.
In Ubuntu, run:
openclaw status --deep
Then send me just the Telegram line from the output.
We need to know if Telegram still says 404 Not Found or if it changed.
Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ Telegram │ ON │ OK │ token config (8264…BK1Q · len 46) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘
Sessions
┌────────────────────────────────────────────────┬────────┬─────────┬─────────────────┬────────────────────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├────────────────────────────────────────────────┼────────┼─────────┼─────────────────┼────────────────────────────────┤
│ agent:main:main │ direct │ 26m ago │ claude-opus-4-7 │ 26k/200k (13%) · 🗄️ 97% cached │
└────────────────────────────────────────────────┴────────┴─────────┴─────────────────┴────────────────────────────────┘
Health
┌──────────┬───────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Status │ Detail │
├──────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
│ Gateway │ reachable │ 121ms │
│ Telegram │ WARN │ failed (401) - Unauthorized
Good, that actually tells us the problem clearly now.
Telegram failed (401) - Unauthorized means OpenClaw is reaching Telegram, but the token is still wrong.
So the issue is definitely the Telegram bot token.
Do this exactly in BotFather
- open @BotFather
- type:
/mybots - tap your bot
- tap API Token or use:
/token
- copy the exact token BotFather gives you
Make sure you are copying the token, not:
- the bot username
- the bot link
- the bot name
The token should look like:
numbers + : + long letters/numbers
Then
- put that exact token into OpenClaw
- save
- run:
openclaw gateway restart
- run:
openclaw status --deep
If it still says 401, then the token you pasted is not the real BotFather token yet.
how to puat code into oprrnclaw
In Ubuntu, do it like this:
-
run:
openclaw configure -
choose:
- Channels
- Telegram
- Modify
-
when it asks for the token, paste the BotFather token there
- use right-click paste
- or Ctrl + Shift + V
-
finish / save
- then run:
openclaw gateway restart
That’s how you put the Telegram code into OpenClaw.
then what ]
maclem@DESKTOP-KCQU24V:~$ openclaw gateway restart
🦞 OpenClaw 2026.4.15 (041266a) — Self-hosted, self-updating, self-aware (just kidding... unless?).
Restarted systemd service: openclaw-gateway.service
maclem@DESKTOP-KCQU24V:~$
Then:
- finish / save
- run:
openclaw gateway restart - then run:
openclaw status --deep
Look at the Telegram line.
If it no longer says 401 Unauthorized, then go message your bot in Telegram again.
Perfect, restart worked.
Now run:
openclaw status --deep
Then send me the Telegram line from that output.
If it says OK instead of 401, then you can go message your bot right after.
Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ Telegram │ ON │ OK │ token config (8264…BK1Q · len 46) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘
Sessions
┌────────────────────────────────────────────────┬────────┬─────────┬─────────────────┬────────────────────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├────────────────────────────────────────────────┼────────┼─────────┼─────────────────┼────────────────────────────────┤
│ agent:main:main │ direct │ 32m ago │ claude-opus-4-7 │ 26k/200k (13%) · 🗄️ 97% cached │
└────────────────────────────────────────────────┴────────┴─────────┴─────────────────┴────────────────────────────────┘
Health
┌──────────┬───────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Status │ Detail │
├──────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
│ Gateway │ reachable │ 244ms │
│ Telegram │ OK │ ok (@Oriondagoatbot:default:244ms) │
└──────────┴───────────┴───────────────────────────────
YES, that means Telegram is working now 🎉
Telegram │ OK is exactly what we wanted.
Now do this:
- open @Oriondagoatbot in Telegram
- tap Start
- send hello
If it sends you a pairing code, then in Ubuntu run:
openclaw pairing list telegram
and approve it.
But the hard part is done, your Telegram bot is now connected.
maclem@DESKTOP-KCQU24V:~$ openclaw pairing list telegram
🦞 OpenClaw 2026.4.15 (041266a) — Ah, the fruit tree company! 🍎
Pairing requests (1)
┌──────────┬─────────────────┬──────────────────────────────────────────────────────────────┬──────────────────────────┐
│ Code │ telegramUserId │ Meta │ Requested │
├──────────┼─────────────────┼──────────────────────────────────────────────────────────────┼──────────────────────────┤
│ 9RMG6E6M │ 8473816686 │ {"firstName":"Mac","lastName":"Clem","accountId":"default"} │ 2026-04-20T03:09:03.069Z │
└──────────┴─────────────────┴──────────────────────────────────────────────────────────────┴──────────────────────────┘
maclem@DESKTOP-KCQU24V:~$
Perfect, you’re one command away.
Run this exactly:
openclaw pairing approve telegram 9RMG6E6M
Then go back to Telegram and send your bot another message.
That should finish the pairing.
siad it just cam onling and there is a bootstrap.md file siting here that syas we should figure it outyt
Ah, I think I know this one.
That usually means it got stuck in bootstrap mode.
Fix
In the same terminal, run:
mv BOOTSTRAP.md BOOTSTRAP.md.bak
Then restart OpenClaw:
openclaw gateway restart
Then message your Telegram bot again.
So:
- rename
BOOTSTRAP.md - restart gateway
- try the bot again
Don’t delete it, just rename it.
it woreks noe ehat
Nice, you got it working 🎉
Now:
- talk to your bot in Telegram
- make sure it replies normally
- if you want, add Discord after that, but I’d do it tomorrow, not tonight 😄
And if this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for other people.
You made it. 🦐
so to keep this allways online just keep my coumputer with that teminal on and i will be good
Not exactly.
If the daemon install worked, you should not need to keep that terminal window open.
But:
- your computer needs to stay on
- it should not go to sleep
- if Windows / WSL shuts down, the bot goes offline
So the simple answer is:
- terminal can usually close
- computer needs to stay on
If you want, you can test it right now:
- close the terminal
- wait a minute
- message your Telegram bot
If it still replies, you’re good.
so cna i continue this conversation and sey up lik e bot sub gaennts and a sashbored and all that tmr and give it task tmr
Yes, absolutely.
Tomorrow you can:
- keep using this thread
- talk to your bot in Telegram
- open the dashboard again
- set up subagents / tasks / the rest
If tomorrow it seems offline, check with:
openclaw gateway status
and reopen the dashboard with:
openclaw dashboard
So yeah, you’re in a good spot to stop for tonight and continue tomorrow.
so i can talk to my bot and get to know about it and what it does on tele gram when iam in bed
Yes, exactly 🙂
As long as your computer stays on and the gateway keeps running, you can talk to your bot on Telegram from bed and start getting a feel for it.
Good things to try:
- ask who it is
- ask what tools it has
- give it a small task
- test simple ideas before you build bigger automations
So yep, that’s the idea.
LETS FUCING GO
LET’S FUCKING GO 🎉🦐
You got through the hard part.
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so it gets indexed on Answer Overflow for the next person.
Now go enjoy your bot 😄
Hey, so I was messaging my But on my thing and then it won’t respond to me anymore, but my computer is still on
No worries, first check whether the Gateway is still running.
In Ubuntu, run:
openclaw gateway status
Then tell me exactly what it says.
If it says stopped / failed, we’ll restart it. If it says running, we’ll check Telegram next.
It says running stay active sub running last exit 0 reason zero run open class status it’s working it seems
Good, that means the Gateway is still up.
Now check Telegram specifically.
Run:
openclaw status --deep
Then send me just these two lines from the output:
- Gateway
- Telegram
That’ll tell us whether Telegram is connected or if only the bot reply flow broke.
Could it be because I asked it I sent in a YouTube video of a dashboard I liked and I told her to make me one and it said it would do it so I sent it to the YouTube video and then it just stopped responding to me
Yes, that absolutely could be why.
A big request like:
- “make me a dashboard”
- plus a YouTube video link
can make it take a long time, or get stuck.
For now, try this:
-
in Telegram, send a very short message like:
- stop
- or just reply with one sentence
-
if it still does not respond after a minute, run:
openclaw gateway restart
And for bigger stuff like dashboard design, I’d use the Web UI tomorrow instead of Telegram. It’s easier for long tasks.
It’s broken