---
app: agent
audience:
  - owner
since: 0.1.0
ui_only: false
agent_actions: []
agent_examples:
  - the chat panel says disconnected
  - MCP servers 0 connected
llm_weight: demote
title: Chat panel problems
description: '"Chat disconnected", MCP servers (0) connected, Windows without WSL2.'
editUrl: true
head: []
template: doc
sidebar:
  order: 6
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

**Who this is for:** an owner whose chat panel (the terminal-like chat on each desk) misbehaves.

| Symptom | Cause | Fix |
|---|---|---|
| **Chat disconnected** right after opening | The Node.js the runtime found is outside the supported range, so its web UI could not build. | Quit and reopen the app: it installs a managed Node.js on launch when the one it sees is unsuitable. If it persists, **Run agent health check** in Settings. |
| **MCP Servers (0) connected** in the first message of a new agent | The Bakulai tools were still loading when the banner printed. | Nothing to do; the next message has them. |
| The panel is blank and the desk says **Sleeping** | The chat works without the gateway, but the runtime must run. | Start the runtime from the top bar. |
| Windows: the panel shows a WSL2 notice | The chat panel needs a POSIX terminal; on native Windows it is not available yet. | Install WSL2 as the notice describes, or use the channels (Telegram, WhatsApp) and the Inbox tab meanwhile. |
| A conversation you continued shows old messages only | The panel resumed an archived session. | Start a new chat from the panel; the old one stays in the Inbox tab. |

## Related

[An agent is not working](/agent/troubleshooting/agent-not-working/) · [Inbox](/agent/inbox-tasks/inbox/)