Onboarding session disappeared
โ
Solved
Hi, Krill! Last night I setup a gateway through the all in one script install to run on a Hetzner VPS that lives in my tailnet and is served so I can hit the dashboard directly from machines in my tailnet. That's mainly working fine and spun up once I abandoned the usage of docker the guide in the docs suggests. I completed the onboarding flow with the cli through SSH, Clawd ingested my identity, its identity, et cetera, and we chatted a bit before I went to sleep. This morning I woke up, noticed there had been a release and updated, which seemed to go fine, and only now a little while later that I'm looking it seems like my main original chat session has disappeared. I had yesterday setup and validated the discord integration, so I still have both of those sessions, paired to within a guild and to my DM, but that initial main session that I believe I was at some point interacting with through the dashboard is gone. I know I didn't hallucinate it because the memory files got written at some point, but I'm only mostly sure that the onboarding session was available / I saw it in the dashboard's session list. Does Clawd have some kind of session retention / automatic deletion scheme I can't find in the docs, or does that onboarding session never get saved, et cetera? I definitely know at one point where I was testing things I did the onboarding flow more manually myself through the dashboard chat and that session seemed to persist.
Solution
Based on my investigation of the codebase, here's what I found:
No automatic session deletion exists. Sessions are stored in
What likely happened:
The update process may have restarted the gateway in a way that caused issues. When you ran the update, the gateway likely restarted, and there could have been a race condition or the session file got corrupted during the transition.
Things to check on your VPS:
No automatic session deletion exists. Sessions are stored in
~/.clawdbot/agents/{agentId}/sessions/sessions.jsonWhat likely happened:
The update process may have restarted the gateway in a way that caused issues. When you ran the update, the gateway likely restarted, and there could have been a race condition or the session file got corrupted during the transition.
Things to check on your VPS:
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
