#Discord-Terminal not communicating

4 messages · Page 1 of 1 (latest)

open ore
#

So when I first set up discord everything seemed fine. But then one day discord amd terminal stopped relaying information. I can chat with my openclaw in both locations perfectly fine but they have no idea about the other session. They cant see each others files or chat sessions. So moving from one to the other is starting completely fresh with no context of what we talked about all day on discord or what we built all night on the home terminal. We have tried to fix this problem multiple times but it keeps resulting in my openclaw breaking himself then having to use claude to help me find and fix what broke. Its usually a new problem also. The first time it was a "," that shouldn't be somewhere, another time the openclaw tried to use apply tools command i believe and it broke. Those are the only 2 I can actually recall. But this has happened 4 maybe 5 times now. I need my discord and terminal to work together, not be completely separate sessions

limpid domeBOT
#

That’s frustrating, and I think this is probably session routing, not “Discord relay broke”.

OpenClaw does not treat a Discord channel/thread and the terminal TUI as the same conversation by default:

  • Discord guild channels get their own isolated session
  • openclaw tui usually opens the main session unless you tell it otherwise

So they can look like two separate brains even when both are healthy. If the files also differ, you may also be landing on different agents/workspaces.

Please paste these first:

openclaw --version
openclaw status --all
openclaw sessions --active 1440 --json
#

And in Discord, run:

/status

Then paste the Agent and Session Key it shows, plus the exact terminal command you use (openclaw tui, ACP/Codex, etc.).

If you are using the TUI, the fastest test is:

openclaw tui --session '<paste the exact Discord session key here>' --deliver

That attaches the terminal to the same session instead of the default main.

Docs: