#"I don't have terminal access. I'm only using the Control UI web interface.
1 messages · Page 1 of 1 (latest)
Yes — for Telegram, you can fix most of it from the Control UI. You shouldn’t need remote access for the basic config.
In Control UI:
- Check Control → Overview and note the OpenClaw version. Please share that first if you want exact click-by-click help.
- Go to Control → Config. Prefer Form mode if it shows Telegram fields; otherwise use Raw JSON/JSON5 carefully.
- Configure Telegram with a bot token from BotFather. A simple one-user setup can avoid terminal-based pairing by using an allowlist:
{
channels: {
telegram: {
enabled: true,
botToken: "123:abc",
dmPolicy: "allowlist",
allowFrom: ["YOUR_NUMERIC_TELEGRAM_USER_ID"],
groups: { "*": { requireMention: true } }
}
}
}
Then click Apply / Save & restart in the Config screen.
To find your numeric Telegram user ID without terminal: DM your bot once, then check Control → Logs for the Telegram inbound/pairing entry — it should include from.id. If that’s too awkward, a third-party Telegram helper bot can show it, but logs are the more private route.
There may be a Shell command / Terminal action in the Control UI command palette on some installs, but it depends on your Gateway permissions and exec approvals. Don’t rely on that unless you already see it enabled.
I would not recommend remote-in from random people, and don’t share your Gateway token or Telegram bot token here. If someone trusted helps via screenshare, redact/rotate tokens afterward.
Docs: https://docs.openclaw.ai/channels/telegram and https://docs.openclaw.ai/web/control-ui
Version
v2026.5.7
Thanks — v2026.5.7 is recent enough that I’d try the Control UI path first.
In the web UI:
- Open Control → Config
- Search for
telegram - Add/update:
channels: {
telegram: {
enabled: true,
botToken: "<token from BotFather>",
dmPolicy: "allowlist",
allowFrom: ["<your numeric Telegram user id>"]
}
}
Then save/apply the config. If it offers restart/reload, accept it.
After that, DM your Telegram bot. If it still doesn’t reply, open Control → Logs and search for telegram, pairing, or from.id. The most useful thing to paste back here is the redacted log line/error — don’t paste the bot token.
One important bit: allowFrom must be your numeric Telegram user ID, not your @username. If you don’t know it, Control UI logs after you message the bot are usually the best terminal-free way to find it.
it is Settings->Config
Yep — thank you, you’re right. It’s Settings → Config in the current UI. My wording was stale there.
So the path is:
Settings → Config → search telegram → edit/apply → restart/reload if prompted
And then check Logs for Telegram errors or from.id after you DM the bot.
Settigs->Config->Channels->Telegram->Connect
Perfect — even better. Correct current path:
Settings → Config → Channels → Telegram → Connect
Thanks for correcting the breadcrumb. Use that Connect flow first; it should guide the token/config pieces without needing terminal. If it fails, grab the exact error from that screen or Logs and paste it here with tokens redacted.
After I hit Connect it takes me to Communications
That’s expected — Connect drops you into the Communications setup area.
From there, look for the Telegram card/row and continue the setup there:
- Choose Telegram
- Paste the BotFather bot token
- Save/Connect/Apply
- If it prompts for access policy, pick the locked-down option / allowlist if available
- DM the bot from Telegram once
If the UI asks for your Telegram user ID, it needs the numeric ID, not @username.
If the Telegram row/card doesn’t show up on Communications, or clicking it just loops back, check Logs and paste the error text here with the token redacted. That would tell us whether this is a UI routing bug or a config/auth issue.
Communications opens Channels
Yep — Communications → Channels is the next screen. You’re in the right place.
On Channels, find Telegram and open it. From there you should either see:
- a Connect / Configure button, or
- fields for the Telegram bot token / account settings.
Use the BotFather token there, then apply/save. After saving, message your bot in Telegram and come back to Channels → Telegram or Logs to see whether it connected.
If Telegram shows as connected but still won’t reply, the next thing is usually access control: it needs either pairing approval or allowFrom with your numeric Telegram user ID.
it says Telegram and under it are 2 buttons network & channels
Good, that split makes sense:
- Network = proxy/DNS/advanced network settings. Skip this unless Telegram API access is failing because of networking.
- Channels = the actual Telegram bot/account config. Click Channels.
Inside Telegram → Channels, look for an account entry — often default — or an Add / Configure / Connect action. That’s where the BotFather token should go.
For a basic DM setup, the important fields are:
- enabled: on
- bot token: your BotFather token
- DM policy:
pairingorallowlist - if using allowlist: allowFrom = your numeric Telegram user ID
If after clicking Channels you only see a blank page or no way to add/configure an account, say exactly what buttons/fields appear there and I’ll map the next click.
the Channels button doesn't do anything but this sentence appears below the buttons: simplest way to get started---reigister a bot with @BotFather and get going
Got it — that sounds like the Channels button is either broken in that screen or it’s only expanding help text, not opening a real config form. Annoying, but you can still do it from Settings → Config directly.
Use the config editor/search and add/edit this under channels:
channels: {
telegram: {
enabled: true,
botToken: "<BotFather token>",
dmPolicy: "pairing"
}
}
Then Apply/Save and restart/reload if prompted.
After that: