Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: clowd.bot control panel stuck in onboarding for existing Fly app with working agents

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

App: clowdbot-0eebf25a (Fly.io, ord region) Version: OpenClaw 2026.3.12 (6472949)

Two working agents exist ("Helen" and "Max"), both active and responding via Telegram. But clowd.bot always opens the onboarding wizard (step 2/5 "Choose your claw") instead of the dashboard.

Clicking through onboarding creates duplicate partial agents, so I stopped.

Tried: incognito, clearing cache, direct fly.dev URL (returns "Unauthorized — Access from Clowdbot control panel").

The onboarding state for this app/account needs to be reset to recognize the existing agents.

Diagnostics: gateway healthy, both Telegram accounts OK, loopback-only on port 18790.

Error Message

Screenshot shows "Choose your claw" onboarding screen (step 2/5) instead of dashboard. No relevant error logs — gateway is healthy, agents respond via Telegram normally. Full "openclaw status --all" output confirms both agents active and Telegram channels OK.

Root Cause

App: clowdbot-0eebf25a (Fly.io, ord region) Version: OpenClaw 2026.3.12 (6472949)

Two working agents exist ("Helen" and "Max"), both active and responding via Telegram. But clowd.bot always opens the onboarding wizard (step 2/5 "Choose your claw") instead of the dashboard.

Clicking through onboarding creates duplicate partial agents, so I stopped.

Tried: incognito, clearing cache, direct fly.dev URL (returns "Unauthorized — Access from Clowdbot control panel").

The onboarding state for this app/account needs to be reset to recognize the existing agents.

Diagnostics: gateway healthy, both Telegram accounts OK, loopback-only on port 18790.

Fix Action

Fix / Workaround

Workaround: agent works fine via Telegram chat, but no UI access. Gateway and both agents are healthy per "openclaw status --all".

Code Example

Screenshot shows "Choose your claw" onboarding screen (step 2/5) instead of dashboard. No relevant error logs — gateway is healthy, agents respond via Telegram normally. Full "openclaw status --all" output confirms both agents active and Telegram channels OK.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

App: clowdbot-0eebf25a (Fly.io, ord region) Version: OpenClaw 2026.3.12 (6472949)

Two working agents exist ("Helen" and "Max"), both active and responding via Telegram. But clowd.bot always opens the onboarding wizard (step 2/5 "Choose your claw") instead of the dashboard.

Clicking through onboarding creates duplicate partial agents, so I stopped.

Tried: incognito, clearing cache, direct fly.dev URL (returns "Unauthorized — Access from Clowdbot control panel").

The onboarding state for this app/account needs to be reset to recognize the existing agents.

Diagnostics: gateway healthy, both Telegram accounts OK, loopback-only on port 18790.

Steps to reproduce

  1. Go to https://clowd.bot and log in
  2. Dashboard opens onboarding wizard (step 2/5 "Choose your claw") instead of showing existing agents
  3. Completing the wizard creates a new partial agent instead of showing the existing one

Expected behavior

clowd.bot should show the dashboard for the existing app (clowdbot-0eebf25a) with two working agents (Helen and Max).

Actual behavior

clowd.bot always opens the onboarding wizard. Direct fly.dev URL returns "Unauthorized — Access this dashboard from your Clowdbot control panel."

OpenClaw version

2026.3.12 (6472949)

Operating system

Linux 6.12.91-fly (Fly.io container)

Install method

Fly.io hosted via clowd.bot

Model

anthropic/claude-opus-4-6

Provider / routing chain

openclaw -> anthropic (via llm.atxp.ai)

Additional provider/model setup details

N/A — issue is with clowd.bot control panel, not model routing.

<img width="1897" height="903" alt="Image" src="https://github.com/user-attachments/assets/1c6566e2-7cfa-4822-aeb2-489c469de3a8" />

Logs, screenshots, and evidence

Screenshot shows "Choose your claw" onboarding screen (step 2/5) instead of dashboard. No relevant error logs — gateway is healthy, agents respond via Telegram normally. Full "openclaw status --all" output confirms both agents active and Telegram channels OK.

Impact and severity

Affected: single user (me), all browsers Severity: blocks dashboard access completely Frequency: 100% — every login attempt Consequence: cannot access dashboard, settings, or logs via UI

Additional information

Workaround: agent works fine via Telegram chat, but no UI access. Gateway and both agents are healthy per "openclaw status --all".

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

clowd.bot should show the dashboard for the existing app (clowdbot-0eebf25a) with two working agents (Helen and Max).

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING