Releases: GregsGreyCode/Logos
v1.0.20 — SEARXNG_URL wired end-to-end; chat status reflects sandbox
Highlights
SearxNG is actually usable by agents out of the box now. /setup
used to start the SearxNG container but never tell anyone its URL:
the gateway's forwarding logic (_FORWARDED_HOST_ENV) copies
SEARXNG_URL from its own process env into each sandbox's .env,
but the gateway's env had no SEARXNG_URL unless you were running
Logos under the docker-compose profile. Direct-host installs ended
up with a healthy SearxNG container and every agent correctly but
uselessly reporting "SearxNG isn't configured for this session".
Fixed: on /setup completion, SEARXNG_URL=http://host.openshell.internal:8888
is written to ~/.logos/.env and seeded into the live process env,
so fresh sandbox spawns get the variable forwarded and agents can
actually call the search tool. User-set values win — someone pointing
at a custom SearxNG instance on another host keeps their override.
Chat page status circle now means what it looks like it means.
The green/red/gray dot next to the agent portrait was bound to
agentAlive, which is true whenever Logos's own process can answer
/status — i.e. always, for as long as the gateway itself is up.
Net effect: the dot was green even while the active agent's sandbox
was still provisioning, its hermes runtime was disconnected, or the
sandbox had been manually stopped. You could see "Connected" green,
type a message, and get "Something went wrong" because the sandbox
wasn't actually ready.
Fixed: the dot now reflects the active agent's sandbox state from
/api/admin/sandboxes:
- green — pod Ready AND worker connected AND healthy
- red — pod Ready but hermes runtime disconnected
- gray pulsing — provisioning / starting / unknown
Polls every 6 s unconditionally (not only when you're on the
Dashboards tab), so the dot stays fresh while you're chatting.
Upgrade notes
-
If you installed from v1.0.19 and SearxNG was broken for your
agent, you can fix an existing sandbox without reinstalling:echo "SEARXNG_URL=http://host.openshell.internal:8888" >> ~/.logos/.envlogos gateway restart- In Admin → Sandboxes, click Restart on the agent's sandbox.
Reinstalling from v1.0.20 does this automatically on
/setup. -
No migration needed for the status-circle change — it reads
/api/admin/sandboxeswhich already exists.
v1.0.19 — async /setup/complete, pin openshell 0.0.33, hardened install/uninstall
Highlights
/setup no longer 504s behind reverse proxies. /api/setup/complete
is now async: returns 202 in milliseconds, actual provisioning runs in
a background task, frontend polls /api/setup/progress for the
terminal state. On a Cloudflare-fronted deployment this eliminates
the 100-second origin-timeout class of failure that masked successful
background work as "HTTP 504".
openshell CLI pinned to 0.0.33. NVIDIA's 0.0.35 release bundles a
0.0.33 supervisor binary with a 0.0.35 gateway binary — the two can't
complete their mTLS handshake, so every sandbox exec returns
"supervisor session not connected". Pinning to 0.0.33 (the last
internally-consistent release) restores a working end-to-end setup.
Override via LOGOS_OPENSHELL_VERSION=latest once a fixed upstream
release lands.
fresh-uninstall.sh is now full-wipe by default. One top-level
confirmation replaces the per-step prompts. Wipes containers,
openshell/hermes-sandbox images, ~/.logos, ~/.config/openshell,
the repo, and ~/.local/bin/logos. Still asks once before removing
~/.local/bin/openshell (standalone tool). Per-step prompts kept
producing partial states where one source of truth was wiped but
another wasn't (e.g. containers gone, stale model_routes rows
left behind, next /setup hangs on a phantom gateway).
Fixes
- Install script pre-pulls the matching openshell cluster image so
fresh gateways come up fast on first/setupinstead of spending
3-5 min on the wizard's Finish click. - Install script shows docker-pull progress (was piped to /dev/null).
- Install script removes stale cluster image tags before the fresh
pull, preventing Docker from caching the wrong version. /api/setup/progress+/api/setup/sessionnow send
Cache-Control: no-storeso Cloudflare's edge doesn't freeze the
setup stepper on a stale poll response.- Setup client-side abort lifted to 12 minutes so the reverse proxy
stays the authoritative timeout (not the browser).
Upgrade notes
- If you were on openshell 0.0.35 and hit the "supervisor session not
connected" or "no hermes_server_setup on state record" errors, the
pinned 0.0.33 install fixes the root cause. - The new
fresh-uninstall.shis more aggressive. Back up anything
outside~/.logosyou care about before running it.
v1.0.0
First 1.x release. Tagged after thought-bubble fix so the world view
shows live dispatch activity end-to-end.
Highlights since v0.13.3:
- v2 runtime hardening (LOG-44 Phase 1 / dispatch_task_v2 over hermes
gateway run HTTP server inside the sandbox) - Per-agent cloud-tool env credentials
- Compare-tab polish + Claude route fix + LOG-66
- Admin UI cleanup: delete Platforms/Routing UI, hide Approvals tab,
STAMP-row chat controls - Cost fix: fall back to route.model when hermes usage lacks a model
- CLI: skip sandbox-internal hermes PIDs when stopping the gateway
- World view: 💭 thought bubble now renders while agents are dispatching
A lot went into this and I'm so excited for people to try it.
Install
Fresh machine — one-liner (clones the repo, pulls the sandbox image, wires the CLI):
curl -fsSL https://raw.githubusercontent.com/GregsGreyCode/Logos/v1.0.0/scripts/fresh-install.sh | bashContainer images (pulled automatically by the installer):
- Gateway:
ghcr.io/gregsgreycode/logos:1.0.0 - Sandbox:
ghcr.io/gregsgreycode/hermes-sandbox:v1.0.0 - Sandbox base:
ghcr.io/gregsgreycode/hermes-upstream:v1.0.0
The gateway image + tagged sandbox images are what you actually run. The "Source code" zip/tarball below is GitHub's auto-generated snapshot of the tag — you can ignore it unless you want to read the code without cloning.
v0.12.0
Logos v0.12.0 — Windows Installer
Download LogosSetup-0.12.0.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.12.0.exe |
273947224a1acbee816e66221b6b46e3c0ed27f393a672ed9a1185fb5a7654ba |
Logos.exe (inner binary) |
cdbcb704732cb9bdf4403ec71f6df0934a2d18ac0857fb55eabc891fb8bbe872 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.12.0.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.12.0.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.11.0
Logos v0.11.0 — Windows Installer
Download LogosSetup-0.11.0.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.11.0.exe |
713bd141094576647386a25ee32fe92a34d3375e9420af802a1d091f4f5a54ff |
Logos.exe (inner binary) |
5ad4c92bdc424919d0797d6772421c1e3b0ef5c1b39bf526c03c0063de8df883 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.11.0.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.11.0.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.10.2
Logos v0.10.2 — Windows Installer
Download LogosSetup-0.10.2.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.10.2.exe |
c8dd3adc5fc8d891c401dec8e0eb496c74d68f6780101f4862ea3b936f64ee4c |
Logos.exe (inner binary) |
a795430a32ed86ca5e1cad3d85b79a6bc80ba41f851eb1dc826c8086ffd394a4 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.10.2.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.10.2.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.10.1
Logos v0.10.1 — Windows Installer
Download LogosSetup-0.10.1.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.10.1.exe |
b9f6bf58aeb358ee47ace3e373f53046b578ba21841db1a2342622c39672f9ed |
Logos.exe (inner binary) |
52a66dbc231dbcd009ac29ead78661eea05453e0c9237042e6edacf21ca22ed5 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.10.1.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.10.1.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.10.0
Logos v0.10.0 — Windows Installer
Download LogosSetup-0.10.0.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.10.0.exe |
622ec7b644b60173f23af6d701f77ffcafcc2a2edbaa4cbb0930b7362e297099 |
Logos.exe (inner binary) |
3b9bde2991518f51f6ef8976535977c2db55b26d0480529b76447f76d9a59b57 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.10.0.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.10.0.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.9.19
Logos v0.9.19 — Windows Installer
Download LogosSetup-0.9.19.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.9.19.exe |
c406790a8e544c925a453c8f82e05ed0b5978c4fda928924d671fce9c680a5f9 |
Logos.exe (inner binary) |
25df96cbe027341b763ab8c355812aa2867657e10756d74014dab0dd7d15aef9 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.9.19.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.9.19.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.
🧪 VirusTotal scan
v0.9.18
Logos v0.9.18 — Windows Installer
Download LogosSetup-0.9.18.exe from the assets below.
⚠️ Why Windows shows a warning
Logos is currently unsigned. Code signing certificates is either quite expensive at this time or seems to require an identity validation process that is not yet available to us in the UK.
We publish full build transparency instead.
Windows SmartScreen may show "Windows protected your PC" on first run — click "More info" → "Run anyway". This is safe once you have verified the SHA256 hash below.
🔐 Build transparency
- Built exclusively by GitHub Actions — no local machines, no manual steps
- View this exact workflow run
- View source at this tag
🔑 SHA256 verification
| File | SHA256 |
|---|---|
LogosSetup-0.9.18.exe |
8de2ae85f66f1de52139ece3173e7ccc8ea7028a587aa72a8194cc8a68cd09fe |
Logos.exe (inner binary) |
cb350841be078974f7a9bf3f16f543f7972316f5cd378b25777013afb0465128 |
Windows (PowerShell / certutil):
certutil -hashfile LogosSetup-0.9.18.exe SHA256macOS / Linux:
sha256sum LogosSetup-0.9.18.exeSHA256SUMS.txt and a .sha256 sidecar are also attached to this release.
📦 Prerequisites
Logos is self-contained — no Python or runtime install required.
MCP servers (optional): if you want to connect stdio-based MCP servers (anything using npx or node in its config), you must install Node.js (LTS) separately. HTTP/StreamableHTTP MCP servers work without it.