user: A new session was started via /new or /reset. Say hi briefly (1-2 sentences) and ask what the user wants to do next. If the runtime model differs from default_model in the system prompt, mention the default model in the greeting. Do not mention internal steps, files, tools, or reasoning. [message_id: d06ecc71-3ac5-4c6a-8a4a-77af7c84da7c] assistant: Hi snake — fresh session. What do you want to do next? user: we added a chat ui to the openclaw dashboard, but i can't start a new conversation, the new button is disabled [message_id: 0f9319f6-885c-429d-ab85-67b96b07d4de] assistant: The “New” button is disabled because it was hard-gated on connected (disabled={!connected}), so if the dashboard hasn’t connected to the Gateway yet you can’t create a conversation.

I just pushed a fix to openclaw-dashboard main: New is now enabled even when disconnected (it’ll attempt to connect first; if it still can’t connect, it’ll show “Not connected to gateway.” instead of blocking the button).

To pick it up on your server:

In the meantime (before updating), the workaround is: click “Connect” first, then “New”.

If after updating it still won’t connect, tell me what the UI shows in the top-right (“Connected/Disconnected”) and any error text in the red error box (or paste the browser console error). user: you should know how this dashboard is deployed and run by now... [message_id: f2820775-c9a6-4746-9fce-22679650feee] assistant: You’re right to call that out — I should have. It wasn’t in long-term memory, but I’ve now checked the host and this is how your dashboard is running:

So you don’t need to manually pull/build/restart: the fix I pushed will be picked up automatically on the next timer tick (worst case ~5 minutes), or you can force it with:

If it’s still disabled after the update runs, then it’s not the deploy—it’s that the UI thinks it’s disconnected. In that case, tell me what “Connected/Disconnected” shows in the chat header and any error message shown under it. user: System: [2026-04-12 14:45:10 UTC] Cron: Synced Dashboard Activity:

Commit: 6700460 — chore: sync activity System: [2026-04-12 15:00:10 UTC] Cron: ok

seems like it's stuck on connecting [message_id: 2c60fc63-eb77-4c27-8ea9-643d8154b6e5] assistant: Yeah — this one’s on us: the chat page’s default Gateway WS URL was wrong (.../gateway), so the connect handshake never completes and the UI sits on “Connecting…”.

Your actual deployment is:

So the WS should be the :444 endpoint, typically:

I just pushed a fix that:

Give the auto-update timer ~5 minutes, then refresh.
If you want the immediate workaround right now: in the chat page, set Gateway WS URL to:

wss://openclaw.tail18850e.ts.net:444/ws

…then hit Connect. user: System: [2026-04-12 15:21:47 UTC] Exec completed (oceanic-, code 0) :: ode/node.d.ts:1381: * const response = await chat.sendMessage({ /home/ubuntu/.npm-global/lib/node_modules/openclaw/node_modules/@google/genai/dist/node/node.d.ts:1402: * const response = await chat.sendMessageStream({ /home/ubuntu/.npm-global/lib/node_modules/openclaw/node_modules/@google/genai/dist/node/node.d.ts:8662: These parameters are used with the chat.sendMessage() method. */ System: [2026-04-12 15:30:15 UTC] Cron: Synced dashboard activity:

for all the content on my openclaw dashboard now, are they all scoped to the agent? if i create a new agent, i'd have a new set of everything? [message_id: 81e9e971-5161-449d-a289-4ed55ab4d43e] assistant: No — almost everything you see in the dashboard is scoped to the machine/OpenClaw instance, not to an “agent.” Creating a new agent won’t magically give you a clean slate of docs/memory/cron/activity.

Concretely, in the current dashboard code:

If you want a “new agent == new set of everything”, you’d need to separate the underlying storage (and usually the runtime), e.g.:

If you tell me what you mean by “new agent” in your setup (OpenClaw agent id? a new gateway? just a new prompt/persona?), I can recommend the cleanest way to get true isolation. user: like multiple openclaw agent https://docs.openclaw.ai/concepts/multi-agent [message_id: e4b24f0a-3dc8-43aa-96b6-ddac69a54703] assistant: Yes—with OpenClaw “multi-agent” enabled, most core things are agent-scoped. Per the multi-agent concept doc:

Agent-scoped (you get a “new set” per agent):

Not automatically agent-scoped (depends on how the dashboard is wired):

So: creating a new OpenClaw agent can give you a clean set of workspace + sessions, but only if the dashboard is pointed at / aware of that agent.

If you want the dashboard to behave “agent = separate everything”, the clean options are:

Tell me which UX you want: