You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature] Please provide bsk daemon install-autostart (and document the 10-minute idle exit) #337
Please provide bsk daemon install-autostart / bsk daemon uninstall-autostart.
Why
The daemonize-mode error message recommends running the daemon "in a persistent host task". That is the right shape — but creating such a task is not possible from an agent / sandboxed environment, so every user has to invent their own launcher. We ended up writing a VBS launcher and reverse-engineering the constraints; that shouldn't be necessary.
What fails from an agent environment
Approach
Result
Start-Process <bsk> daemon start
daemon may appear, then is killed together with the spawning command (see #268 — fixed in 0.3.1, which we confirm improves this)
schtasks /create /tn ... /sc onlogon
ERROR: Unspecified error
Register-ScheduledTask ...
Unspecified error
What works today (user-side only, found by trial and error)
A silent launcher in the Startup folder. Two non-obvious requirements:
the file must be pure ASCII — VBScript reads ANSI, and a UTF-8 file fails with a misleading unterminated string constant / object required error that points nowhere near the real cause.
' bsk daemon autostart (silent, at logon)Setsh=CreateObject("WScript.Shell")sh.Run"""C:\Users\<user>\.local\bin\bsk.exe"" daemon start --foreground",0,False
This works because explorer.exe spawns it, outside restricted job objects.
Also please document
Idle exit: daemon exceeded idle threshold; exiting idle_secs:600. Note the timer starts after the browser disconnects (with Edge connected we observed >44 min uptime). The practical rule a user needs is: "Edge open ⇒ the daemon should be up" — it is not a start-once-forever service, and after Edge has been closed for ~10 minutes the daemon is gone and must be relaunched.
If autostart is out of scope for now, publishing the recommended launcher snippet and the ASCII caveat in the README would save every user the same rediscovery.
I plan to implement an idempotent bsk daemon install-autostart / uninstall-autostart flow for the supported local platform, using the existing --foreground daemon mode so the daemon survives short-lived agent commands. I will also document the 10-minute idle-exit behavior and add focused tests for command parsing, installation/removal decisions, and safe path handling.
I will keep the change scoped and will first verify the current repository behavior before opening a PR.
Activity
legend91019 commentedon Oct 4, 2026
I would like to work on this issue.
I plan to implement an idempotent
bsk daemon install-autostart/uninstall-autostartflow for the supported local platform, using the existing--foregrounddaemon mode so the daemon survives short-lived agent commands. I will also document the 10-minute idle-exit behavior and add focused tests for command parsing, installation/removal decisions, and safe path handling.I will keep the change scoped and will first verify the current repository behavior before opening a PR.