v1.2.2 — Move a bot between hosts + a fixed server control panel
Fixes
- The server control panel no longer gets stuck once your bot is configured. In server‑hosting mode every control — status, the SSH key, start/stop, reconnect — was being blocked after setup, so the panel showed Unreachable, the SSH‑key field spun on "generating…" forever, and reinstalling didn't help. It's reachable again, with real timeouts and a Retry instead of an endless spinner.
- "Open console" is no longer greyed out on a long‑running server — the public
…ts.netURL is now found even after it has scrolled out of the recent logs.
New
- Move a bot between hosts. A new Move / change hosting action on the active bot moves it between this computer and a cloud server — Olisar carries the bot's data across itself (persona, memory, knowledge, uploaded docs) and keeps the old copy as a backup. Covers local → server, server → local, and server → server.
- Reset a bot's configuration. A per‑bot Reset configuration clears its Discord credentials, API keys, and server/hosting config while keeping everything it has learned — persona, memory, knowledge, and settings. A server‑hosted bot is sent to Reconnect afterwards.
- Reconnect to a server by IP alone. The app reuses the SSH key it already holds, so re‑adopting a VM just needs its IP address (with an "add this key" fallback for a brand‑new VM).
- Settings + Logs on the server control panel. The control panel gained a settings gear, including a Logs view — bot logs, Tailscale Funnel logs, and this app's own logs.
Other
- Tidied the server control panel — removed the raw log dump under the buttons; use the gear → Logs instead.
Install
Download the macOS .dmg (Apple Silicon) or Windows .exe below. The app is unsigned:
- macOS — clear Gatekeeper once:
xattr -dr com.apple.quarantine /Applications/Olisar.app - Windows — SmartScreen may warn; choose More info → Run anyway.
Already on 1.2.1? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.