Troubleshooting
"Meet [Agent]" Opened an OpenClaw Dashboard — Is That Wrong?
Short answer: usually no. For many users, that dashboard is the correct control center for your Heyron agent.
If you clicked "Meet [Agent]" and landed on an OpenClaw Gateway Dashboard, it can feel like you were redirected to the wrong product. In most cases, that page is expected.
Good news: You likely did not lose your agent. The dashboard is where your Heyron agent actually runs and where channels/tools are managed.
Why this happens
- Heyron is built on OpenClaw infrastructure. The dashboard is the runtime/control UI layer.
- Your branded onboarding page and runtime page are different surfaces. One introduces your agent; the other is where it lives.
- Current rollout behavior: some users are sent directly to dashboard/control views after onboarding.
Fast verification checklist (2 minutes)
1) Confirm agent name + session area
In the dashboard, verify your configured agent name appears in the expected workspace/session view.
2) Send a simple test message
Use a clean prompt like: "Reply with: Dashboard test successful."
If it replies, your core runtime is healthy.
3) Check channel connection status
If you plan to use Discord/Telegram, confirm your channel integration is connected before expecting replies there.
4) Start a fresh chat if behavior feels odd
Long or stale sessions can feel "off." A fresh session often clears confusion quickly.
Common confusion to avoid
"I got OpenClaw, not Heyron" is usually a branding/UX expectation mismatch, not an account issue.
- Not a wrong login: same account context can legitimately surface OpenClaw runtime UI.
- Not a second bot: dashboard + Discord/DM can be different conversation contexts for the same agent identity.
- Not immediate data loss: if agent settings and responses are present, your setup is intact.
"I can’t find my agent name anywhere" (Eva/Frankie confusion)
This is a frequent onboarding confusion: users expect to see their custom name everywhere, but some pages still show system/runtime labels (for example, OpenClaw or a default assistant name in shared/public examples).
- Verify account context first: make sure you are signed into the same email/account used during Heyron signup.
- Open your direct runtime entry point: use the Heyron chat entry URL you were given and launch from there, not a random shared dashboard link.
- Run identity prompt in the active chat: ask "What is your configured name in this workspace?" and compare the answer to what you set.
- Ignore names seen in other people's screenshots/chats: those can be different users, different sessions, or default assistant labels.
Important: seeing another name in community screenshots (like "Frankie") does not mean your agent was replaced. Validate inside your own active chat/session only.
When it is actually a problem
- You see a blank screen or repeated load failures
- Your configured agent name is missing
- You cannot run any prompt in dashboard
- Connected channels also fail to respond after clean tests
If any of those apply, use these guides first:
Copy/paste message for #help
I clicked "Meet [Agent]" and landed on an OpenClaw dashboard.
Expected: [what you expected to see]
Current behavior: [what page appears + what still works/doesn't]
Agent name shown in dashboard: [yes/no + name]
Quick test result: [did "Dashboard test successful" reply?]
Channel status: [Discord/Telegram connected or not]
Time + timezone: [example: 9:08 AM ET]
Security reminder: never post API keys, tokens, or private config values in public support channels.
Bottom line: landing on OpenClaw Dashboard after clicking "Meet [Agent]" is often expected behavior. Verify with the 2-minute checklist, then escalate only if core runtime tests fail.