#Telegram channel not starting on WSL - No polling logs

1 messages Β· Page 1 of 1 (latest)

mystic atlas
#

Hey guys, I think I found a bug or maybe I'm just stuck.

I'm running OpenClaw on WSL and my Telegram channel won't start at all.
The Telegram API is working fine (tested with curl), but the bot isn't polling any messages. Even after clearing updates and restarting the gateway, the [telegram] log never shows up in the terminal.
Is this a known issue with the current version on WSL?

System Info:
OS: WSL2 (Ubuntu)

Issue: Telegram polling won't initialize

Any help would be sick, thanks!🫠

white nicheBOT
#

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

mystic atlas
#

@hollow pond

mystic atlas
#

@hollow pond pls help this

hollow pondBOT
#

Yeah, this looks very close to a known 2026.4.1 WSL2 Telegram startup regression: Telegram logs starting provider, never reaches getUpdates, and inbound messages don’t process. That issue was closed as fixed/implemented; the fix landed in v2026.4.5 by bounding Telegram startup calls so they can’t hang before polling begins. (api.github.com)

First thing: please paste this, with tokens redacted:

openclaw --version
openclaw gateway status
openclaw channels status --probe
openclaw channels logs --channel telegram --lines 100
openclaw status --all

If you’re on 2026.4.1–2026.4.4, update past 2026.4.5 and restart the gateway. If you’re already newer, then the likely causes shift to: gateway using a different config/env than your shell, Telegram token not visible to the service, channels.telegram.enabled/token config, webhook mode accidentally enabled, or a duplicate poller/token conflict. Telegram uses bot token config/env and does not use openclaw channels login telegram; long polling is the default unless webhookUrl is set. (docs.openclaw.ai)

Don’t paste the bot token here. 🦐

mystic atlas
#

Port 18789 is already in use.

  • pid 5454 ahmad: openclaw-gateway (127.0.0.1:18789)
  • Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
    Listening: 127.0.0.1:18789
    Troubles: run openclaw status
    Troubleshooting: https://docs.openclaw.ai/troubleshooting

🦞 OpenClaw 2026.4.24 (cbcfdf6) β€” I'm not magicβ€”I'm just extremely persistent with retries and coping strategies.

β”‚
β—‡
Gateway reachable.

  • Telegram default: enabled, configured, running, mode:polling, bot:@JarDaviss_bot, token:config, works

Tip: status --deep adds gateway health probes to status output (requires a reachable gateway).

hollow pondBOT
#

That output is actually good news: Telegram is running and probing successfully now.

The Port 18789 is already in use bit just means you tried to start a second gateway while the real one is already running:

pid 5454 ahmad: openclaw-gateway
Telegram default: enabled, configured, running, mode:polling ... works

So the reason you don’t see [telegram] logs in that terminal is probably: you’re looking at the new failed foreground process, not the already-running gateway/service.

Try:

openclaw logs --follow
#

or just Telegram logs:

openclaw channels logs --channel telegram --lines 100

If the bot still doesn’t reply, the next likely thing is access/pairing, not polling. For a DM:

openclaw pairing list telegram
openclaw pairing approve telegram <CODE>

For groups, make sure the group is allowed under channels.telegram.groups and that you’re mentioning the bot unless requireMention: false is configured.

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

mystic atlas
#

the bot is replied me but it said "all models are temporarily rate-limited. please try again in a few minutes"

hollow pondBOT
#

Nice, that means Telegram is fixed β€” the bot is receiving messages and handing them to OpenClaw now. This is no longer a Telegram/WSL polling problem.

That error means the model provider side is failing/exhausted: current model + configured fallbacks are all in rate-limit/cooldown.

Please run:

openclaw models status --probe
openclaw models fallbacks list
openclaw logs --follow

Look for:

  • missing/expired auth
  • provider 429 / quota / billing errors
  • no fallbacks configured
  • all configured profiles in cooldown
#

Quick fixes are usually one of:

  1. wait a few minutes if it’s a real temporary 429
  2. add/fix provider auth via:
    openclaw onboard
    
  3. configure a fallback model/provider so one rate limit doesn’t stop replies:
    openclaw models fallbacks add <provider/model>
    

For fresh model/provider recommendations, ask in #models β€” that changes too fast for me to safely guess. Docs: https://docs.openclaw.ai/concepts/models and https://docs.openclaw.ai/concepts/model-failover 🦐

mystic atlas
hollow pondBOT
#

Yep β€” that explains it. Telegram is working now; the blocker is Gemini quota.

Because you have 0 fallbacks, OpenClaw tries Google, gets 429 quota exceeded, then has nowhere else to go, so it returns:

all models are temporarily rate-limited

Fix options:

  1. Wait / increase Gemini quota or billing in Google AI Studio.
  2. Add another model/provider as fallback so OpenClaw can recover automatically:
    openclaw onboard
    openclaw models fallbacks add <provider/model>
    openclaw models status --probe
    
  3. Or switch primary model:
mystic atlas
#

how to switch primary model?

hollow pondBOT
#

Use the models CLI:

openclaw models list
openclaw models set <provider/model>
openclaw models status --probe

models set changes the global primary/default model.

If that provider/model is not configured yet, run:

openclaw onboard

or configure model/auth first, then run models set again.

#

For the current Telegram chat only, you can also send this to the bot:

/model

and pick/switch the session model there.

I won’t suggest exact model names here β€” ask in #models for current recommendations. Docs: https://docs.openclaw.ai/cli/models 🦐

mystic atlas
#

sudah set ke flash 3. tapi pas saya suruh buka youtube dia hanya berjalan setenagh ingin membalas tapi diinterup dan tiba tiba rate limited ready in 11s

hollow pondBOT
#

Itu masih rate limit model, bukan Telegram lagi.

β€œready in 11s” artinya OpenClaw sudah masuk cooldown pendek dan akan coba lagi setelah ~11 detik. Kalau kamu switch ke Flash 3 tapi masih lewat Google/Gemini, kuotanya tetap bisa kena limit β€” apalagi task seperti β€œbuka YouTube” biasanya butuh beberapa langkah/tool call, jadi lebih cepat kena 429.

Coba:

openclaw models status --probe
openclaw models fallbacks list
openclaw logs --follow

Kalau masih 429 dari Google, pilih salah satu:

  1. tunggu quota window Google reset / upgrade billing di Google AI Studio
  2. tambahkan fallback dari provider lain, bukan Google lagi:
#
   openclaw onboard
   openclaw models fallbacks add <provider/model>
   openclaw models status --probe
  1. untuk test, pakai prompt kecil dulu setelah cooldown lewat, jangan langsung task browser berat.

Docs: https://docs.openclaw.ai/concepts/model-failover 🦐

mystic atlas
#

prompt kecilnya apa?

hollow pondBOT
#

Pakai prompt yang nggak perlu browser/tool, cuma chat pendek. Contoh kirim ke bot Telegram:

balas "ok" saja

atau:

sebutkan 3 warna primer dalam satu baris

atau:

ringkas: OpenClaw adalah asisten AI pribadi. Maksimal 1 kalimat.
#

Kalau prompt kecil ini masih kena rate limited, berarti kuota/model Google-nya memang lagi habis/cooldown. Kalau ini berhasil tapi β€œbuka YouTube” gagal, berarti task browser/tool-nya yang terlalu berat untuk quota saat ini. 🦐

mystic atlas
#

sudah saya tanya 3 warna dan dia menjawab dan minta apa identitasnya, pas saya balas malah gak respob lagi, tapi pas saya /status dia masih bisa

hollow pondBOT
#

/status itu command lokal Gateway β€” jadi dia bisa balas walaupun model/agent normal lagi macet atau rate-limited.

Coba urut begini:

  1. Tunggu cooldown lewat dulu, misalnya 30–60 detik.
  2. Kirim ini sebagai pesan standalone ke bot:
    /new
    
    atau:
    /reset
    
  3. Lalu test lagi:
    balas "ok" saja
    
#

Kalau masih diam, cek log pas kamu kirim pesan:

openclaw logs --follow

dan model probe:

openclaw models status --probe

Kalau di /status terlihat agent masih busy / running / rate-limited, berarti bukan Telegram β€” session/model-nya yang lagi ketahan. Solusi stabilnya tetap tambah fallback provider lain, karena Gemini free/quota sering kena limit walau prompt kecil. 🦐

mystic atlas
#

dia balas lagi, ternyata dia ngerapiin sistem agar mengubah nama yang sya beri

hollow pondBOT
#

Mantap, berarti alurnya normal πŸŽ‰

Yang terjadi kemungkinan: agent masih memproses task sebelumnya, jadi kelihatan seperti diam. /status tetap bisa balas karena itu command Gateway, bukan respons model biasa.

Tips biar nggak bingung:

/status

cek apakah dia masih running/busy.

Kalau mau mulai bersih:

/new
#

Kalau ingin menghentikan konteks lama dan test ringan:

balas "ok" saja

Dan tetap saran saya: tambahkan fallback provider/model lain, karena quota Gemini tadi sudah sempat kena limit. Kalau fixed, boleh right-click pesan solusi β†’ Apps β†’ βœ… Mark Solution biar keindeks Answer Overflow untuk user lain. 🦐

mystic atlas
#

kok sering banget ya rate limited, padahal lagi working

hollow pondBOT
#

Iya, itu normal kalau pakai provider yang quotanya kecil/ketat β€” β€œlagi working” justru bisa makin cepat kena rate limit.

Satu task OpenClaw bukan cuma 1 request model. Bisa jadi beberapa call:

  • baca instruksi/context
  • mutusin tool/browser action
  • proses hasil tool
  • bikin jawaban final
  • retry kalau ada error/interruption

Jadi task seperti buka YouTube jauh lebih β€œmahal” daripada tanya 3 warna.

Yang bisa dilakukan:

openclaw models status --probe
#

Kalau Google masih 429, solusinya:

openclaw models fallbacks add <provider/model>

sebaiknya fallback dari provider lain, bukan Google lagi. Atau ganti primary:

openclaw models set <provider/model>

Sementara itu: tunggu cooldown selesai, jangan kirim banyak pesan saat dia masih running, dan test pakai prompt kecil dulu. Untuk rekomendasi model/provider yang paling stabil sekarang, tanya di #models ya. 🦐

mystic atlas
#

masalahnya saya mau gratis

hollow pondBOT
#

Bisa gratis, tapi tradeoff-nya ya itu: rate limit sering πŸ˜…

Pilihan realistis:

  1. Tetap pakai Gemini free

    • cocok buat chat ringan
    • jangan task berat seperti browser/YouTube terus-menerus
    • tunggu cooldown kalau kena 429
  2. Tambah fallback gratis lain

    openclaw onboard
    openclaw models scan
    openclaw models fallbacks add <provider/model>
    

    Kalau satu provider kena limit, OpenClaw coba fallback.

#
  1. Local model
    Gratis per request, tapi butuh hardware kuat. Untuk tool/browser agent, local model sering kurang stabil kecuali mesin/GPU-nya bagus.

Intinya: gratis bisa, tapi tidak akan se-stabil paid API. Untuk daftar opsi gratis yang lagi bagus sekarang, tanya di #models karena cepat berubah. 🦐

mystic atlas
#

provider/model apa aja yang gratis selain gemini

hollow pondBOT
#

Kalau mau gratis selain Gemini, jangan pakai daftar manual dari saya β€” cepat banget berubah. Cara paling aman: biarkan OpenClaw scan katalog free:

openclaw models scan

atau metadata-only:

openclaw models scan --no-probe

Biasanya opsi gratis paling realistis:

  1. OpenRouter free models
    Butuh OPENROUTER_API_KEY, walau modelnya free. Tetap ada rate limit.
#
  1. Local model via Ollama / LM Studio
    Gratis per request, tapi untuk agent + tools/browser sering kurang stabil kalau hardware biasa.

  2. Provider free tier lain
    Ini berubah-ubah, jadi tanya di #models untuk rekomendasi terbaru.

Setelah dapat model yang cocok:

openclaw models set <provider/model>
openclaw models fallbacks add <provider/model>
openclaw models status --probe

Docs: https://docs.openclaw.ai/concepts/models 🦐

mystic atlas
#

rate limited terus nih udah coba 3 model gemini, padhal masih used 40k token / 1m token

hollow pondBOT
#

Itu masuk akal: 40k / 1M token itu cuma TPM (tokens per minute). Gemini juga punya limit lain seperti RPM (requests per minute) dan RPD (requests per day). Kalau RPM/RPD kena, tetap 429 walaupun token masih jauh dari 1M. Google juga bilang limit berlaku per project, bukan cuma per API key. (ai.google.dev)

OpenClaw β€œworking” bisa bikin banyak request kecil ke model, jadi cepat kena RPM.

Coba cek di Google AI Studio bagian rate limits/quota:

  • RPM model yang dipakai
  • RPD harian
  • apakah semua model Gemini masih di project/API key yang sama

Solusi gratis paling realistis:

openclaw models fallbacks add <provider/model>

tapi fallback-nya usahakan non-Google, karena kalau masih Gemini/project yang sama bisa tetap kena 429. Also jangan kirim banyak pesan saat agent masih running β€” tunggu dia selesai dulu.

mystic atlas
#

^Cahmad@HP14S:~openclaw models fallbacks add <provider/model>l>
-bash: syntax error near unexpected token `newline'

hollow pondBOT
#

Ah, <provider/model> itu placeholder, jangan diketik pakai tanda < >.

Formatnya begini:

openclaw models fallbacks add provider/model

Contoh bentuknya:

openclaw models fallbacks add openrouter/some-free-model

Tapi pilih model yang benar dulu dari daftar:

#
openclaw models list

atau cari free models:

openclaw models scan

Lalu copy salah satu model ref yang muncul, misalnya bentuk openrouter/..., dan pakai:

openclaw models fallbacks add MODEL_REF_YANG_MUNCUL
openclaw models fallbacks list
openclaw models status --probe
#

Jadi jangan literal <provider/model> ya β€” itu maksudnya β€œisi dengan nama model asli.” 🦐

mystic atlas
#

saya --probe model status tapi sudah gak ada 429 padahal

hollow pondBOT
#

Bisa begitu. models status --probe cuma test kecil sekali; itu bisa OK, tapi task Telegram/browser tetap kena limit karena:

  • task normal butuh beberapa request model, bukan cuma 1 probe
  • cooldown lama bisa sudah lewat saat probe dijalankan
  • limit yang kena bisa RPM / concurrency, bukan token total
  • session lama mungkin masih punya model/auth cooldown state

Coba reset session Telegram-nya:

/new

lalu test kecil:

#
balas "ok" saja

Kalau test kecil OK tapi task berat kena lagi, berarti quota Gemini masih terlalu ketat untuk workload itu.

Kalau mau bukti pastinya, jalankan log sambil kirim prompt yang gagal:

openclaw logs --follow

Cari baris error model/provider setelah prompt dikirim. Itu yang paling akurat dibanding probe. 🦐

mystic atlas
#

padahal saya cuma nyruuh panggil nama saya, tapi terkena rate limited. dan di log terminal 429

hollow pondBOT
#

Kalau prompt sesimpel β€œpanggil nama saya” tetap kena 429 di log, berarti ini bukan karena prompt berat β€” quota/rate limit provider-nya memang sedang kena.

Beberapa hal penting:

  • 429 dari Gemini bisa kena karena RPM/RPD/concurrency, bukan cuma token.
  • Walaupun models status --probe sempat OK, request berikutnya tetap bisa kena 429.
  • Kalau 3 model Gemini sama-sama kena, kemungkinan limitnya di project/API key Google yang sama.

Coba hentikan spam/retry dulu 5–10 menit, lalu:

openclaw models status --probe
openclaw models fallbacks list

Kalau masih mau gratis, tambah fallback non-Google. Jangan pakai placeholder:

#
openclaw models scan

copy model ref yang muncul, lalu:

openclaw models fallbacks add MODEL_REF

Kalau mau saya bantu baca tepatnya, paste 10–20 baris log sekitar error 429 β€” hapus token/API key kalau ada.

mystic atlas
#

terjadi Error: Missing OpenRouter API key. Set OPENROUTER_API_KEY to run models scan pas saya scan

hollow pondBOT
#

Iya, models scan default-nya mau probe live, jadi butuh OPENROUTER_API_KEY.

Kalau cuma mau lihat daftar kandidat gratis tanpa probe, pakai:

openclaw models scan --no-probe

Tapi untuk benar-benar dipakai inference, OpenRouter tetap butuh API key. Bisa ambil key di OpenRouter, lalu set di shell/gateway env:

export OPENROUTER_API_KEY="sk-or-..."
openclaw gateway restart

Kalau gateway jalan sebagai service, pastikan env itu masuk ke service juga β€” bukan cuma terminal sementara. Setelah itu:

#
openclaw models scan
openclaw models fallbacks add MODEL_REF
openclaw models status --probe

Jangan paste API key ke Discord. 🦐

mystic atlas
#

gimana gimana? tolong bertahap

hollow pondBOT
#

Oke, pelan-pelan. Ikuti ini satu per satu.

Step 1 β€” bikin OpenRouter API key

  1. Buka OpenRouter β†’ API Keys.
  2. Buat key baru.
  3. Jangan paste key ke Discord.

Step 2 β€” masukin key ke OpenClaw
Di terminal WSL:

openclaw onboard --auth-choice openrouter-api-key

Nanti paste API key saat diminta.

Step 3 β€” cek kebaca

#
openclaw models status --probe

Kalau OpenRouter muncul ok, lanjut.

Step 4 β€” scan model gratis

openclaw models scan

Kalau muncul daftar model, pilih/copy model ref yang bentuknya seperti:

openrouter/xxx/yyy:free
#

Step 5 β€” tambah sebagai fallback
Ganti MODEL_REF dengan yang kamu copy:

openclaw models fallbacks add MODEL_REF

Contoh format saja:

openclaw models fallbacks add openrouter/meta-llama/llama-3.3-70b-instruct:free

Step 6 β€” restart gateway

openclaw gateway restart
#

Step 7 β€” test Telegram
Kirim ke bot:

/new

lalu:

balas "ok" saja

Kalau ada error di step mana pun, paste errornya di sini β€” tapi jangan paste API key. 🦐

mystic atlas
#

I understand this is personal-by-default and shared/multi-user use requires lock-down. Continue?

hollow pondBOT
#

Itu prompt normal dari openclaw onboard.

Kalau ini untuk bot pribadi kamu sendiri, jawab:

y

atau:

yes

Maksudnya OpenClaw ngingetin: default-nya asisten pribadi, jadi kalau dipakai banyak orang/group publik harus dikunci dengan allowlist/pairing/config. Untuk setup pribadi Telegram kamu, lanjut saja. 🦐

mystic atlas
#

itu terjadi pas saya openclaw auth choice openrouter api key

hollow pondBOT
#

Iya, itu masih normal. openclaw onboard --auth-choice openrouter-api-key memang masuk ke flow onboarding dan menampilkan peringatan keamanan itu dulu.

Lanjut:

  1. Saat muncul:

    Continue?
    

    jawab:

    y
    
  2. Kalau diminta API key OpenRouter, paste key kamu.

  3. Setelah selesai:

#
   openclaw models status --probe

Kalau command kamu tadi bukan ini, pakai yang lengkap:

openclaw onboard --auth-choice openrouter-api-key

Bukan openclaw auth choice ... ya. 🦐

mystic atlas
#

Config handling
β”‚ ● Use existing values
β”‚ β—‹ Update values
β”‚ β—‹ Reset

hollow pondBOT
#

Pilih:

Update values

Karena kamu mau menambahkan/mengubah auth OpenRouter API key.

Di menu itu pakai tombol panah bawah ke Update values, lalu Enter.

Jangan pilih Reset kecuali kamu memang mau reset config lama. 🦐

mystic atlas
#

Telegram already configured. What do you want to do?
β”‚ β—‹ Modify settings
β”‚ ● Skip (leave as-is)

hollow pondBOT
#

Pilih:

Skip (leave as-is)

Telegram kamu sudah jalan, jadi jangan diubah. Kita cuma mau tambah OpenRouter/model fallback. 🦐

mystic atlas
#

Search provider
β”‚
β”‚ Search: _
β”‚ β—‹ Brave Search
β”‚ β—‹ Exa Search
β”‚ β—‹ Firecrawl Search
β”‚ ● Gemini (Google Search) (Requires Google Gemini API key Β· Google Search grounding Β· configured)
β”‚ β—‹ Grok (xAI)
β”‚ β—‹ Kimi (Moonshot)
β”‚ β—‹ Ollama Web Search
β”‚ β—‹ Perplexity Search
β”‚ β—‹ SearXNG Search
β”‚ β—‹ Tavily Search
β”‚ β—‹ Skip for now
β”‚ ↑/↓ to select β€’ Enter: confirm β€’ Type: to search

hollow pondBOT
#

Pilih:

Skip for now

Ini untuk search provider, bukan model utama/fallback. Biar nggak nambah masalah dulu, skip saja. 🦐

mystic atlas
#

Configure skills now? (recommended)
β”‚ ● Yes / β—‹ No

hollow pondBOT
#

Pilih:

No

Kita lagi fokus model/OpenRouter dulu. Skills bisa dikonfigurasi nanti kalau semua sudah stabil. 🦐

mystic atlas
#

Gateway service already installed
β”‚ ● Restart
β”‚ β—‹ Reinstall
β”‚ β—‹ Skip

hollow pondBOT
#

Pilih:

Restart

Itu perlu supaya config/auth baru kebaca oleh gateway. 🦐

mystic atlas
#

How do you want to hatch your bot?
β”‚ ● Hatch in Terminal (recommended)
β”‚ β—‹ Do this later

hollow pondBOT
#

Pilih:

Do this later

Kamu sudah punya Telegram bot/gateway jalan. Kita nggak perlu hatch/terminal chat sekarang β€” setelah onboarding selesai, langsung cek:

openclaw models status --probe

🦐

mystic atlas
#

Auth probes
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Model β”‚ Profile β”‚ Status β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ google/gemini-3.1-pro-preview β”‚ google:default (api_key) β”‚ ok Β· 51.5s β”‚
β”‚ openrouter/openrouter/auto β”‚ openrouter:default (api_key) β”‚ ok Β· 34.9s β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Probed 2 targets in 78.6s

hollow pondBOT
#

Nice, OpenRouter auth sudah kebaca βœ…

Sekarang tambah OpenRouter sebagai fallback:

openclaw models fallbacks add openrouter/auto

Kalau command itu error karena yang muncul di status adalah openrouter/openrouter/auto, pakai ini:

openclaw models fallbacks add openrouter/openrouter/auto

Lalu cek:

#
openclaw models fallbacks list
openclaw models status
openclaw gateway restart

Setelah itu di Telegram:

/new

lalu test:

balas "ok" saja
#

Kalau Gemini kena 429 lagi, OpenClaw harusnya punya jalur fallback ke OpenRouter. 🦐

mystic atlas
#

Config overwrite: /home/ahmad/.openclaw/openclaw.json (sha256 62db237466ce3d75642059af4af19d6f7c683f23f2bdff2dfdd0f4ce6068bd92 -> bf5fc9a8b40fcbb497c0e1358ea6b8c03f24baff65f48a7184e3894ba496cd7c, backup=/home/ahmad/.openclaw/openclaw.json.bak)
Updated ~/.openclaw/openclaw.json
Fallbacks: openrouter/auto

hollow pondBOT
#

Perfect β€” fallback sudah terpasang βœ…

Sekarang lakukan:

openclaw gateway restart
openclaw models status

Lalu di Telegram kirim:

/new

Terus test:

#
balas "ok" saja

Kalau masih rate-limited, paste bagian log sekitar error dari:

openclaw logs --follow

Tapi sejauh ini config-nya sudah benar: Fallbacks: openrouter/auto. 🦐

mystic atlas
#

saya cek /status dia masih menggunakan gemini flash, apakah harus saya ganti

hollow pondBOT
#

Nggak harus. Primary tetap Gemini Flash, dan openrouter/auto sekarang jadi fallback. Jadi normal kalau /status masih menampilkan Gemini Flash saat Gemini belum gagal.

Artinya alurnya:

  1. coba Gemini Flash dulu
  2. kalau kena 429 / rate limit
  3. baru pindah ke OpenRouter fallback

Kalau kamu mau langsung pakai OpenRouter sebagai primary, baru ganti:

openclaw models set openrouter/auto
openclaw gateway restart

Lalu di Telegram:

#
/new

Rekomendasi saya:

  • kalau Gemini kadang masih jalan β†’ biarkan Gemini primary + OpenRouter fallback
  • kalau Gemini sering banget 429 β†’ jadikan OpenRouter primary dulu 🦐
mystic atlas
#

katanya dia gak bisa kemampuan buat ngontrol aplikasi atau browser di komputer lokal saya

hollow pondBOT
#

Bisa jadi dia benar untuk kondisi sekarang: Telegram/model sudah jalan, tapi browser tool belum aktif/terkonfigurasi.

Cek bertahap dulu:

1. Cek browser tool ada atau tidak

openclaw browser status

2. Jalankan diagnosis browser

openclaw browser doctor

3. Coba buka browser test

#
openclaw browser start --headless
openclaw browser open https://youtube.com

Kalau command openclaw browser error/unknown, aktifkan browser plugin:

openclaw config set browser.enabled true --strict-json
openclaw config set tools.alsoAllow '["browser"]' --strict-json
openclaw gateway restart

Lalu di Telegram kirim:

mystic atlas
#

profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: unknown
detectedPath: auto
profileColor: #FF4500

hollow pondBOT
#

Browser tool enabled, tapi OpenClaw belum nemu browser executable:

running: false
detectedBrowser: unknown
detectedPath: auto

Di WSL, kemungkinan belum ada Chrome/Chromium di Linux side.

Coba:

which google-chrome chromium chromium-browser microsoft-edge brave-browser

Kalau tidak ada output, install Chromium/Chrome di WSL. Paling simpel di Ubuntu:

#
sudo apt update
sudo apt install -y chromium-browser

Kalau chromium-browser bermasalah karena Snap di WSL, pakai Google Chrome .deb:

wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install -y ./google-chrome-stable_current_amd64.deb

Lalu set path eksplisit:

openclaw config set browser.executablePath "/usr/bin/google-chrome"
#
openclaw gateway restart
openclaw browser status
openclaw browser start --headless

Kalau browser start sudah jalan, coba lagi dari Telegram setelah /new. 🦐

mystic atlas
#

saya berhasil menginstall sudo apt update
sudo apt install -y chromium-browser

hollow pondBOT
#

Mantap. Sekarang verifikasi path dan start browsernya:

which chromium-browser chromium google-chrome

Lalu:

openclaw browser doctor
openclaw browser status
openclaw browser start --headless
openclaw browser open https://youtube.com
openclaw browser snapshot

Kalau which menunjukkan path misalnya /usr/bin/chromium-browser, tapi OpenClaw masih detectedBrowser: unknown, set eksplisit:

#
openclaw config set browser.executablePath "/usr/bin/chromium-browser"
openclaw gateway restart
openclaw browser status
openclaw browser start --headless

Kalau browser snapshot berhasil, baru di Telegram:

/new

lalu:

#
buka youtube pakai browser tool

🦐

mystic atlas
#

detectbrsr udh chronium tapi snapshot : GatewayClientRequestError: Error: Failed to start Chrome CDP on port 18800 for profile "openclaw". CDP diagnostic: http_unreachable after 1ms; cdp=http://127.0.0.1:18800; fetch failed.
Hint: If running in a container or as root, try setting browser.noSandbox: true.
Hint: No DISPLAY/X server was detected. Enable browser.headless: true, start Xvfb, or run the Gateway in a desktop session.
Chrome stderr:
/usr/bin/chromium-browser: 12: xdg-settings: not found
[9695:9695:0427/222036.566293:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:256] Missing X server or $DISPLAY
[9695:9695:0427/222036.566409:ERROR:ui/aura/env.cc:246] The platform failed to initialize. Exiting

hollow pondBOT
#

Error-nya jelas: Chromium jalan headed, tapi WSL kamu nggak punya X/DISPLAY. Set browser jadi headless permanen.

Jalankan:

openclaw config set browser.headless true --strict-json
openclaw gateway restart

Lalu test lagi:

openclaw browser status
openclaw browser start --headless
openclaw browser open https://youtube.com
openclaw browser snapshot
#

Kalau masih error soal sandbox/root, tambahkan ini:

openclaw config set browser.noSandbox true --strict-json
openclaw gateway restart

Soal xdg-settings: not found biasanya bukan blocker utama, tapi bisa dibereskan dengan:

sudo apt install -y xdg-utils

Mulai dari browser.headless true dulu. 🦐

mystic atlas
#

bahkan dia gak bisa akses file eksplorer saya

hollow pondBOT
#

Itu beda hal ya:

OpenClaw di WSL bisa akses file, tapi bukan β€œFile Explorer” GUI Windows. Dia jalan di Linux/WSL, jadi path Windows harus lewat /mnt/c/....

Coba test begini:

ls /mnt/c/Users
openclaw config get agents.defaults.workspace

Kalau user Windows kamu ahmad, file Windows biasanya ada di:

/mnt/c/Users/ahmad/Documents
/mnt/c/Users/ahmad/Downloads
#
/mnt/c/Users/ahmad/Desktop

Lalu di Telegram jangan bilang β€œbuka file explorer saya”, tapi kasih path jelas, misalnya:

tolong lihat daftar file di /mnt/c/Users/ahmad/Downloads

Lebih aman: buat folder khusus, misalnya OpenClawWorkspace, taruh file yang mau dibaca di situ, lalu set workspace ke folder itu:

openclaw config set agents.defaults.workspace "/mnt/c/Users/ahmad/OpenClawWorkspace"
openclaw gateway restart
#

Jangan set workspace ke seluruh C:\Users\ahmad kalau nggak perlu β€” itu terlalu luas/privacy risk.

Kalau maksudnya benar-benar mengontrol aplikasi File Explorer Windows, itu belum otomatis dari WSL headless. Untuk sekarang fokusnya: kasih akses lewat path /mnt/c/... atau folder workspace khusus. 🦐

mystic atlas
#

Saya tidak dapat mengakses jalur /mnt/c/Users/ahmad/Downloads karena berada di sistem file lokal Anda dan di luar lingkungan aman saya. Saya hanya dapat mengakses file di dalam direktori kerja OpenClaw (/home/ahmad/.openclaw/workspace) atau file yang Anda berikan secara langsung.

hollow pondBOT
#

Itu berarti bot kamu lagi dibatasi ke workspace β€” itu aman, tapi jadi nggak bisa baca /mnt/c/Users/ahmad/Downloads.

Cara paling gampang + aman: buat folder khusus untuk OpenClaw di Windows, lalu jadikan workspace.

1. Buat folder khusus

mkdir -p /mnt/c/Users/ahmad/OpenClawWorkspace

Taruh/copy file yang mau dibaca ke folder itu dari File Explorer Windows.

2. Set workspace OpenClaw

openclaw config set agents.defaults.workspace "/mnt/c/Users/ahmad/OpenClawWorkspace"
openclaw gateway restart
#

3. Di Telegram kirim

/new

Lalu test:

lihat daftar file di workspace

Kalau kamu mau cek batasannya sekarang:

openclaw config get agents.defaults.workspace
openclaw config get tools.fs.workspaceOnly
openclaw config get agents.defaults.sandbox.mode
mystic atlas
#

+-----------------------------------------------------------------------------------+
Config overwrite: C:\Users\ahmad.openclaw\openclaw.json (sha256 81e313e783e8e1a18a4a77aaf1a85f3728cb4579e8d637269265ea7c598b35aa -> 3b1d6de9ec1381d0eaa27882b0d9e83a6d508bd374b5d40507f487f963543461, backup=C:\Users\ahmad.openclaw\openclaw.json.bak)
|
o Gateway service runtime --------------------------------------------+
| |
| QuickStart uses Node for the Gateway service (stable + supported). |
| |
+----------------------------------------------------------------------+
|

  • Gateway service already installed
    | > Restart
    | Reinstall
    | Skip (KONTENS: SAYA INGIN COBA DI WINDOWS AGAR BISA MENGAKSES FILE DAN KOMPITER LOKAL
hollow pondBOT
#

Pilih Restart.

Tapi penting: kalau kamu pindah coba native Windows, jangan biarkan gateway WSL jalan bareng dengan token Telegram yang sama β€” nanti bisa konflik polling.

Urutannya:

1. Di WSL, stop gateway lama

openclaw gateway stop

2. Di wizard Windows ini, pilih

Restart

3. Di PowerShell Windows, cek

#
openclaw status --deep
openclaw channels status --probe

4. Buat workspace Windows khusus

mkdir C:\Users\ahmad\OpenClawWorkspace
openclaw config set agents.defaults.workspace "C:/Users/ahmad/OpenClawWorkspace"
openclaw gateway restart

Lalu di Telegram:

/new
#

Test:

lihat daftar file di workspace

Catatan: native Windows bisa lebih dekat ke file Windows, tapi WSL2 masih jalur yang paling direkomendasikan/stabil. Jangan kasih akses seluruh C:\Users\ahmad dulu β€” pakai folder khusus lebih aman. 🦐

mystic atlas
#

sudah bisa akses file, tapi gak bisa buka browser sebagai perintah untuk membuka aplikasi, dan juga tidak bisa menscreenshot, padahal pas awal banget nyoba dia bisa.

hollow pondBOT
#

Iya, itu dua kemampuan berbeda:

  1. Akses file Windows βœ… sudah bisa
  2. Kontrol browser / screenshot perlu browser tool aktif dan browser path benar
  3. Screenshot desktop / kontrol aplikasi Windows biasa belum sama dengan browser tool

Coba di PowerShell Windows:

openclaw browser doctor
openclaw browser status

Kalau browser belum jalan, set Chrome/Edge:

#
openclaw config set browser.enabled true --strict-json
openclaw config set tools.alsoAllow '["browser"]' --strict-json
openclaw config set browser.headless false --strict-json
openclaw config set browser.executablePath "C:/Program Files/Google/Chrome/Application/chrome.exe"
openclaw gateway restart

Kalau pakai Edge:

openclaw config set browser.executablePath "C:/Program Files (x86)/Microsoft/Edge/Application/msedge.exe"
openclaw gateway restart

Lalu test:

#
openclaw browser start
openclaw browser open https://youtube.com
openclaw browser snapshot
openclaw browser screenshot

Kalau ini berhasil, di Telegram kirim:

/new

lalu:

#
buka youtube pakai browser tool

Catatan: browser screenshot = screenshot halaman browser, bukan screenshot seluruh desktop/File Explorer. Untuk kontrol aplikasi Windows umum + screenshot desktop, native Windows masih lebih terbatas. 🦐

hollow pondBOT
#

I deleted that message because it exposed your Telegram bot token publicly.

Please rotate it immediately:

  1. Open Telegram β†’ @BotFather
  2. Send:
    /revoke
    
  3. Choose your bot
  4. Copy the new token
  5. Update OpenClaw config with the new token / rerun Telegram setup
  6. Restart:
    openclaw gateway restart