Skip to content

v0.1.1 — first-visit fix, exact LGPL boundary, non-root

Choose a tag to compare

@bkisonka bkisonka released this 20 Nov 15:29
· 60 commits to main since this release

Fixed: the first visit dead end

The web client shipped in hosted mode (login/register UI) while the gateway
runs in personal key-auth mode — every sign-in attempt returned 401 and the
quick start dead-ended on the very first screen.

  • The delivered image now builds the web client in single-user mode: no
    login theater, straight to the chat.
  • On first visit a gateway-key screen appears; the key is verified against
    the gateway (wrong keys get a clear rejection message) and stored in the
    browser. VITE_API_KEY baked at build time still wins when present.
  • If the key is rotated on the server, the client notices on the next load
    and asks again instead of failing silently.
  • Chats persist in the mounted data/ volume (gateway.chatsDbPath
    enabled in the example config); the sidebar no longer shows the red
    "not configured" label out of the box.

License: the LGPL boundary made exact

LICENSE-HSS.md is rewritten. The LGPL-3.0-or-later scope is now exactly
one file — hss.cjs — aligned with LICENSE section 3. The TypeScript
stabilizer layer is a proprietary combined work that uses the core through
its public API (LGPL-3.0 section 4); 15 TypeScript files carried SPDX LGPL
headers that contradicted the license and have been fixed. Canonical
license texts (COPYING.LESSER, COPYING) are now part of the repository.

Hardening

  • Non-root: the runtime image runs as node (uid 1000) — the gateway
    and sibling skill containers alike; files written into agents/output
    are no longer root-owned on the host.
  • The docker API proxy no longer grants exec. Sidecar readiness moved
    to the container's own HEALTHCHECK (inspected via docker inspect);
    docker exec through the proxy is denied (verified: 403).
  • Sidecar settings drift: a running sidecar with stale egress settings
    (e.g. after changing allowPrivateHosts) is now recreated instead of
    living with old env.

Upgrade: git pull && docker compose up -d --build. Your .env,
config, chats and memory live in mounted volumes and are not touched.
44/44 tests in CI, full run verified live on the compose stack.