#Clean startup

4 messages · Page 1 of 1 (latest)

inner basin
#

Got a sticking point with Claude. It should be easy for him I'm sure but he's wasted hours on it.
So if I ever lose power and have to reboot, I want it all clean with agent alive and no windows open on desktop. Just straight back in with telegram and not having to force gateway in wsl etc. I think that's it.
Anyway after changing a shit ton of stuff, if I get it opening up with agent alive, there's a window open on desktop (see vid) if I can attach.
And if I get rid of the window on reboot I don't have a live agent. Claude just can't figure it out. Any ideas? I feel it should be something easy it's missing. Just want a clean start on reboot with no windows open and agent running. Any ideas?

pseudo templeBOT
#

Let me check the docs and source paths first so I don’t make up the startup bits.

#

You’re not crazy, this is probably two different startup paths fighting each other.

Most likely:

  • Visible desktop window = Windows fell back to a Startup-folder launcher/login item
  • No window but no live agent = the proper WSL service boot chain is not fully set up yet

If you want clean reboot, no window, agent alive in Telegram, the path I’d aim for is:

  1. Inside WSL, enable systemd if needed
  2. Inside WSL:
    sudo loginctl enable-linger "$(whoami)"
openclaw gateway install
  3. In Admin PowerShell, auto-start WSL at boot:
# 
   schtasks /create /tn "WSL Boot" /tr "wsl.exe -d Ubuntu --exec /bin/true" /sc onstart /ru SYSTEM

Replace Ubuntu with your distro from:

wsl --list --verbose

Why I think this is it: the native Windows fallback launcher is documented as a Startup-folder launcher, and that path can leave a cmd window around. The clean headless route is the WSL systemd user service + linger + WSL boot task.

Docs:

Can you paste these and I can tell you exactly which branch you’re on: