Troubleshooting

Why Dashboard and Discord Don’t Share One Chat

If your agent remembers things in one place but not another, this is usually expected behavior—not a broken bot.

A recurring community confusion is: “I talked to my agent in the dashboard, then moved to Discord and it seemed to forget everything.”

Short answer: your agent identity can be the same, but each conversation surface (dashboard chat, Discord DM, Discord channel) has its own context thread.

What’s separate vs shared

Shared: Your agent persona/instructions (for example SOUL.md behavior).
Shared: Access to files/tools configured in the same workspace.
Not automatically shared: live chat history between dashboard, DM, and server channels.
Not automatically shared: temporary context from one thread to another.

Why this feels like “memory loss”

You solved something in one thread, then switch surfaces expecting the same short-term chat context.
Discord DMs and server channels behave differently (permissions, mention requirements, channel rules).
Long chats can get bloated, so a fresh thread may produce cleaner results than your old one.
You may have accidentally logged into a second account and are now talking to a different agent workspace.
Memory add-ons/search tools can help retrieval, but they do not magically merge separate live chat threads.

High-friction confusion: “Did I create a second bot?”

Common onboarding trap: users sometimes sign in with a different email/provider and unknowingly create a second account. It looks like the same product, but you are now in a different workspace/agent context.

Confirm the email/login method in dashboard and Discord-linked account are the same.
Ask the agent to print a stable identity check (workspace/project name) in both surfaces.
If identity differs, sign out and re-enter from the original Heyron account path.

Fast handoff pattern (copy/paste)

When moving between dashboard and Discord, paste a short state block first:

Context handoff: - Goal: [what I'm trying to finish] - Current status: [where things left off] - Decisions made: [bullet list] - Files or links: [important references] - Next step: [exact task to continue]

Pro move: ask your agent to generate this handoff before you switch surfaces.

2-minute verification test

1) Create a unique marker in dashboard

Example: “Remember token: BLUE-FOX-741.”

2) Ask in Discord DM without handoff

If it does not know the marker, that confirms contexts are separate (expected).

3) Paste handoff and ask again

Now it should continue correctly because you provided the missing thread context.

How to avoid losing progress

Use shorter, focused sessions instead of one huge chat.
Save key outcomes to files (notes, checklists, memory docs) instead of only chat messages.
Before switching channels, ask for a one-screen summary + next actions.
For important workflows, keep a running “project state” file the agent can update.

Don’t assume: “same bot avatar” means “same active conversation context.” Same identity, different thread history.

Support-ready escalation message

I think I have cross-surface context loss (dashboard vs Discord). Checks completed: - Same agent identity verified: [yes/no] - Dashboard test marker: [value] - DM/channel saw marker before handoff: [yes/no] - DM/channel saw marker after handoff: [yes/no] - Approx time + timezone: [time] Expected behavior: Actual behavior: