A focused patch release with one job: migrating to a managed install never locks you out again. If you migrated on v0.6.0 and your dashboard login broke — this is the fix, and your old token is recoverable (see below).
🔐 Upgrades never break existing auth
- 🛡️ #344 — The source migration now carries your operator config.
install-source.shmigrates the operator-identity keys —AUTONOMOS_TOKEN(your dashboard login),AUTONOMOS_HOST(your bind address, so a loopback restriction can't silently widen), andAUTONOMOS_CONFIG_DIR(where your agents and state live) — from the old install tree's.envinto the new managed clone, before the first boot. Tuning overrides are deliberately reset to defaults and listed by name in the install output with a one-copy restore hint. The invariant is pinned by a contract test whose failure message reads "UPGRADE BROKE EXISTING AUTH" — it can't quietly regress.
Hit by the v0.6.0 lockout? Your login didn't vanish — the daemon fell back to its token file. Read it with cat ~/.autonomos/token and log in with that, or restore your old token by recreating .env (with AUTONOMOS_TOKEN=…) in the new clone and running autonomos restart.
📦 Install / upgrade: curl -fsSL https://raw.githubusercontent.com/aterrylu/autonomOS/main/scripts/install.sh | sh && autonomos start
💾 Manual download: grab autonomos-<os>-<arch>.tar.gz for your platform from the assets below (verify against SHA256SUMS)
Thanks for using autonomOS! 💛