v1.3.1 — Fix remote-VM Unreachable false positive

Fixes

• Remote server control panel no longer false-flags Unreachable. Status used to run multiple SSH docker compose commands and scan the entire container log history for the Funnel URL. On a long-running VM that often exceeded the UI’s fetch budget, so the panel showed Unreachable (and asked you to Reconnect) even when SSH worked, Logs loaded, and the bot/Funnel were fine.
• Status is now a single bounded SSH probe (recent logs first; full history only until the first *.ts.net match).
• Failed status checks surface the real error (e.g. timeout) instead of a blank Unreachable badge.
• Control-panel status fetch timeout raised so a slow SSH link has headroom.

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.3.0? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.

v1.3.0 — SDK file uploads, host blobs, private follow-ups

New

• SDK file uploads on slash commands. Extensions can declare type: "attachment" options. Metadata lands on i.options.<name>; load bytes with host.files.read (base64, up to ~20 MB) or host.files.ingest (host-held blobId, up to ~25 MB — preferred for large files).
• Host blob pipeline for external APIs. host.fetch accepts bodyBlobId (send raw blob as the request body) and responseBlob: true (store the response as a host blob). Reply/send with files: [{ name, blobId }] so compress-and-return (and similar) flows never put large binaries through the sandbox.
• File output on replies. i.reply / i.followUp / host.discord.send accept files with text, contentB64, or blobId (max 10 attachments, ~25 MB total).
• Private multi-step slash replies. If the first reply is ephemeral: true, later followUps stay private by default (override with ephemeral: false if you need a public result).

Other

• Soft caps raised for SDK/file fetch paths (20 MB base64 / 25 MB host blobs); command sandbox memory headroom increased for base64-heavy handlers.
• Docs for slash flows and the SDK host table cover attachments, blobs, and the compress-style pipeline.
• Automated coverage in tests/test_sdk_files.py (caps, blobs, mocked fetch, bridge ephemeral inheritance).

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.3? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.

v1.2.3 — Quieter logs + no leaked search scaffolding

Fixes

• Olisar no longer leaks its internal search scaffolding into replies. When it couldn't write a clean summary (for example when the Gemini quota was exhausted) and had gathered several message‑search batches, its fallback pasted the raw results — including the model‑only "…skim these and answer the question…" instruction header that was never meant for you. It now strips that header from every batch, so you just get the messages behind the short apology.
• The embedding model is now parked on a rate limit instead of being hammered. Embeddings power semantic memory/search and — unlike replies — have no fallback model. A 429 wasn't putting the model on cooldown, so every message and every background index tick re‑hit the exhausted quota: a flood of repeating 429s in the log and wasted quota. Now a rate limit briefly parks the model and recall quietly degrades to non‑semantic context, so the log settles down and quota isn't burned on doomed calls. (Replies were never affected — they fall back down the model chain.)

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.2? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.

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.net URL 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.

v1.2.1 — Desktop sign-in opens in your browser

Fixes

• Discord sign-in on the desktop app now opens in your system browser instead of inside the app window. Before, it navigated the app's own chromeless window to Discord — which could reject the request (a raw "Invalid Form Body") and strand you there with no way back. Now the app opens the real browser, keeps a Cancel / Reopen browser option on the sign-in screen, and logs itself in automatically once you authorize.

Other

• Redesigned the post–sign-in confirmation page into a branded Olisar card (success and access-denied states).

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.0? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.

v1.2.0 — Multiple bots & cloud hosting

New

• Run multiple bots from one app. Each bot is its own Discord application with its own token, persona, settings, memory, and database. Switch between them, rename them, set a default (the bot that opens on launch), and delete them — from Settings → Bot or the gear on the sign-in and setup screens. One local bot runs at a time; bots you host on a server stay online independently.
• Server hosting. Run Olisar on a free cloud VM instead of your own machine. Guided Oracle Cloud setup (or any provider), an app-generated SSH key, and an in-app control panel to start/stop the bot over SSH and open its console. You can also connect to a VM that already runs Olisar, with a reconnect affordance for a changed key or IP.
• Same bot, many servers. Background memory upkeep — channel summaries, member personas, and the glossary — and /forget-me now cover every server your bot is in, not just its home server.
• Settings on the sign-in and setup screens. A gear opens Appearance, Bot, Updates, Desktop app, and Feedback before you even sign in.

Other

• Landing page: a subtler grid-lit glow, a copyright line, and consistent spacing.
• Docs: new Running multiple bots and server-hosting sections.

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 running an earlier version? Open the tray → Check for Updates… (or wait for the automatic check) to install this in place.

v1.0.5 — GIF vision, send-to-channel & DM indexing

Fixes

• Glossary no longer duplicates or rephrases facts it already knows.
• Usage donut chart: tiny slices get a minimum arc so they no longer overlap.

New

• The bot reads GIFs. Both uploaded GIFs and Giphy/Tenor links (Discord's GIF picker) are read as images via their first frame — and the model is told it's a GIF and only sees that first frame.
• send_to_channel tool. Ask the bot to relay a message to a named channel and it resolves which channel you mean (fuzzy matching plus an in-context channel directory), instead of needing the exact name or ID.
• DM indexing. Olisar stores and indexes direct messages (as their own guild-0 channels), with a per-user opt-out (/dm-indexing); admins can recall DMs from search.
• Redesigned Usage & rate-limits page. Tracks per-model and per-process Gemini usage plus live requests-per-minute, with more chart headroom.

Other

• Hover tooltips are kept to icon-only buttons; the glossary shows the full fact text on hover.
• Refreshed the model's tools note to the current tool set, and loosened the operating rules for more flexibility.

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.

v1.0.4 — hotfix: backend bind regression

Fixes

• Fixed the backend crash-looping with "could not bind on any address" on cloud/headless deployments — and on desktop whenever remote access was enabled. A regression introduced in 1.0.3 where the funnel hostname was mistakenly used as the server's bind address.

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.

v1.0.3 — context window, glossary mining & KB source fixes

Fixes

• Knowledge base: sources added from the console no longer get stuck on "Pending", and sources added via Discord (/olisar learn-url, learn-site, learn-doc) now appear in that server's console — a multi-guild scoping fix.
• Cloud hosting: on a headless/server deployment the Remote access panel and the sidebar now show the live public URL instead of getting stuck on "Starting…".

New

• Behavior → Memory & summaries: a Context window setting to control how many recent messages Olisar keeps in its working context, per server.
• Knowledge → Glossary: Mine from memory and Deep mine from index buttons to build the server glossary on demand.

Other

• Docs: rewrote the Behavior section — a dedicated "Memory & summaries" subsection plus the new context-window documentation.

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.

1.0.2 — Correct version & update checker

A patch that fixes the version number and the built‑in update checker.

Fixed

• The app showed "v0.0.0" and kept offering an update that never seemed to apply.
  The installed app couldn't read its own version number, so Settings → Updates always
  displayed v0.0.0 and "update available" — even right after updating. Olisar now
  reports its real version, so the number is correct and the update prompt clears once
  you're on the latest build.

Upgrading

Update from inside the app (Settings → Updates, or the menu‑bar tray), or install the
build below. After moving to 1.0.2 the version will finally display correctly.