#agent stall
1 messages · Page 1 of 1 (latest)
Lucas, first check the version so we know what path you’re on:
openclaw --version
Also, wait is one of the standalone abort/stop trigger words, so it may have interrupted the active run. Try starting a fresh chat/session with:
/new
If /new still gives the same error, grab the safe diagnostics and the log line around the failure:
openclaw status --all
openclaw logs --follow
Docs for the quick debug ladder: https://docs.openclaw.ai/help/faq#first-60-seconds-if-something-is-broken
Cancel/stop trigger docs: https://docs.openclaw.ai/help/faq#how-do-i-stopcancel-a-running-task
in telegram i keep typing commands and nothing happens
For Telegram “commands do nothing”, the first thing I’d check is whether Telegram is actually receiving events and whether your sender is approved.
Please run:
openclaw --version
openclaw channels status --probe
openclaw pairing list telegram
openclaw logs --follow
Common causes:
- If you only sent
/start, that may not create a usable pairing flow by itself. Send a normal message likehi, then checkopenclaw pairing list telegramand approve the code if one appears. - If you configured an allowlist, Telegram
allowFrommust be your numeric Telegram user ID, not your username or the bot username. - Slash commands usually need to be standalone messages, like
/status, not embedded in a longer sentence.
Docs: https://docs.openclaw.ai/channels/troubleshooting#telegram and https://docs.openclaw.ai/help/faq#telegram-what-goes-in-allowfrom
can i run a command in terminal to fix it
Yes. The safest terminal “reset the runtime” command is:
openclaw gateway restart
Then test Telegram again with a plain message like hi.
If it still does nothing, run this and paste the relevant output:
openclaw --version
openclaw status --all
openclaw channels status --probe
openclaw pairing list telegram
If pairing list telegram shows a pending code, approve it with:
openclaw pairing approve telegram <code>
I’d avoid deleting session/config files until the status output tells us what’s actually blocked.
its stalled
If openclaw gateway restart itself is hanging, press Ctrl+C and run:
openclaw gateway status
openclaw logs --limit 80
openclaw doctor
If the gateway is running but Telegram is stalled, try a fresh session from Telegram with:
/new
Then send hi. If that still fails, the useful thing is the last ~80 log lines from openclaw logs --limit 80 plus openclaw --version. That should show whether it’s pairing, channel transport, model/auth, or a stuck session.
whats the command in terminal for openclaw doctor
Run exactly:
openclaw doctor
If you want the broader diagnostic bundle too:
openclaw status --all
If doctor reports something scary before changing anything, paste the output here.
i wanna update to latest openclaw
Yep. For latest stable, run:
openclaw update
Then verify/restart if needed:
openclaw doctor
openclaw gateway restart
openclaw --version
If you want to preview first without changing anything:
openclaw update --dry-run
how do i check version?
Run:
openclaw --version
You can also check update status with:
openclaw update status
If you installed the Gateway service/daemon, start it with:
openclaw gateway start
Then check it:
openclaw gateway status
If it says the service is not installed, install it first:
openclaw gateway install
openclaw gateway start
For a foreground/manual run instead, use:
openclaw gateway
That one keeps running in the terminal, so leave the window open.
Use this in your terminal:
openclaw gateway start
Then verify:
openclaw gateway status
If start says the service is not installed, run:
openclaw gateway install
openclaw gateway start
That error means the OpenClaw source checkout at /root/openclaw is missing dependencies. Since the CLI can’t even start, fix the checkout directly:
cd /root/openclaw
corepack enable
pnpm install
pnpm build
pnpm ui:build
openclaw doctor --fix
openclaw gateway restart
If pnpm is not found after corepack enable, run:
npm install -g pnpm
then repeat from pnpm install.
Small caution: you’re running from /root/openclaw, so this looks like a root-owned install. That’s okay if you intentionally installed as root on a VPS, but run all the commands as the same user that installed OpenClaw.
i run a 15 ai agent team and i wanna connect each agent to their own channel and each agent have their own integration with different names so i know which is which how do i go about setting that up
You want multi-agent routing.
Important distinction:
- If you want each one to show up with a different bot name/avatar in Discord/Telegram, you need one channel account/integration per agent: e.g. 15 Discord bot apps or 15 Telegram bots.
- If one shared bot is okay, you can route different channels to different agents, but the visible bot identity stays the same.
High-level setup:
openclaw agents add agent01
openclaw agents add agent02
openclaw agents add agent03
# repeat up to agent15
Then in ~/.openclaw/openclaw.json, define the agents, channel accounts, and bindings. Example shape for Discord:
{
agents: {
list: [
{
id: "agent01",
name: "Agent 01",
workspace: "~/.openclaw/workspace-agent01",
identity: { name: "Agent 01", emoji: "🔵" },
},
{
id: "agent02",
name: "Agent 02",
workspace: "~/.openclaw/workspace-agent02",
identity: { name: "Agent 02", emoji: "🟢" },
},
],
},
bindings: [
{ agentId: "agent01", match: { channel: "discord", accountId: "agent01" } },
{ agentId: "agent02", match: { channel: "discord", accountId: "agent02" } },
],
channels: {
discord: {
groupPolicy: "allowlist",
accounts: {
agent01: {
name: "Agent 01 Bot",
token: "DISCORD_BOT_TOKEN_FOR_AGENT01",
responsePrefix: "auto",
guilds: {
"YOUR_GUILD_ID": {
channels: {
"CHANNEL_ID_FOR_AGENT01": { allow: true, requireMention: false },
},
},
},
},
agent02: {
name: "Agent 02 Bot",
token: "DISCORD_BOT_TOKEN_FOR_AGENT02",
responsePrefix: "auto",
guilds: {
"YOUR_GUILD_ID": {
channels: {
"CHANNEL_ID_FOR_AGENT02": { allow: true, requireMention: false },
},
},
},
},
},
},
},
}
After editing:
openclaw doctor
openclaw gateway restart
openclaw agents list --bindings
openclaw channels status --probe
For Telegram, same idea, but use channels.telegram.accounts.<id>.botToken and create each bot in BotFather.
Docs: https://docs.openclaw.ai/concepts/multi-agent and https://docs.openclaw.ai/channels/channel-routing
for my head agent how do i configure both telegram and discord