Skip to content

Releases

claw2 v0.2.6 — composer message queue and force-send

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 18:55

What's changed in 0.2.6

Added

  • Composer message queue and force-send: the composer stays usable while
    a reply is streaming — submitting puts the message into a visible numbered
    queue above the input. Rows can be dragged to reorder, edited back into
    the composer, removed, or sent immediately with ⚡ (interrupting the
    running reply; the partial answer stays in the tape). When a turn ends,
    the head of the queue sends itself. Attachments are not queued — they wait
    in the composer with a hint. The queue is per chat and does not survive a
    page reload. Web (full) and PWA (without drag reorder).

Full Changelog: v0.2.5...v0.2.6

claw2 v0.2.5 — sidebar attachment indicators fix

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 17:53

What's changed in 0.2.5

Fixed

  • Sidebar attachment indicators never showed (web): the server computed
    hasImages/hasDocs and the sidebar rendered them, but the chat-list
    merge into the local store dropped both fields — a chat could carry
    documents (the chat's documents panel listed them) with no icon in front
    of it. The merge now lives in one tested helper (serverChatToItem).
  • Attachment flags missed two document sources the chat panel counts:
    messages referencing files by bare relative paths (uploads/notes.txt
    without the /files/ prefix) were filtered out by the SQL prefilter, and
    forked chats did not inherit their ancestors' session-prefixed files from
    the disk scan. Both now light the icon, matching the documents panel.

Full Changelog: v0.2.4...v0.2.5

claw2 v0.2.4 — database upgrade fix: title_manual migration with a schema convergence guard

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 17:37

What's changed in 0.2.4

Fixed

  • Upgrading from 0.2.2 no longer breaks the chat list: 0.2.3 shipped the
    title_manual column in schema.sql but forgot the ALTER migration, so an
    existing database made the gateway fail with
    SqliteError: no such column: title_manual on the first chat-list query.
    initDb now adds the column on upgrade.

Added

  • Schema-upgrade guard: a convergence test upgrades a database built from
    schema.baseline.sql (the oldest supported schema, currently 0.2.2) through
    initDb and compares every table's shape with a fresh install. Adding a
    column to schema.sql without the matching ALTER in init.ts now fails the
    test with the exact table.column — the 0.2.3 class of bug can no longer
    ship silently.

Full Changelog: v0.2.3...v0.2.4

claw2 v0.2.3 — in-app update flow, fork-tree project adds, egress sidecar refresh

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 17:17

What's changed in 0.2.3

Added

  • In-app update flow: the gateway periodically checks the latest GitHub
    release (updates.check: false disables it) and the cabinet shows a toast
    when a newer version is available; an Update link next to Help opens
    a dialog that runs the update with a progress bar when the host-side
    watcher (scripts/update.sh --install) is installed, and otherwise shows
    the copy-paste command and watches the restart.

  • Rename a chat: a "Rename" item in the sidebar chat menu (web) and a
    pencil action in the mobile chat list (PWA). Enter saves, Escape cancels.

  • Add a fork tree to a project in one action: when the chat being added
    belongs to a fork tree, the sidebar asks whether to add the whole tree or
    only the selected chat.

  • Attachment indicators in the chat list: chats carrying images and/or
    documents show small image/document icons next to the title (web sidebar
    and the mobile chat list). Flags come from stored messages and the
    session-prefixed files on disk.

Fixed

  • New chats showed the "New chat" placeholder in the sidebar instead of the
    derived title when a per-chat model override had created the row first; the
    placeholder now gives way to the derived/loaded title.
  • Updates no longer leave a stale egress sidecar: a container keeps the
    image it was created from, so after docker compose up -d --build the
    running sidecar kept executing the old code. A skill run now recreates the
    sidecar when its image no longer matches the current tag. The README
    "Updating" section documents the full procedure (stash tracked-file edits,
    optional image prune, automatic schema migrations).
  • The sidebar fork tree stays still during generation: stream progress
    used to re-sort the chat list on every chunk (updatedAt ticks), visibly
    reshuffling the tree and moving the selected chat around. Progress now
    updates the row in place; the final order lands once when the reply
    completes.
  • A manually renamed chat keeps its name: the rename is recorded as
    manual (new title_manual flag) and automatic titling — including the
    browser page title a web-surface chat sends with every message — can no
    longer overwrite it.

Docs

  • Quick start now says explicitly to paste the generated key into .env as
    CLAW2_GATEWAY_API_KEY.

Full Changelog: v0.2.2...v0.2.3

claw2 v0.2.2 — personal hardening, chat-state fixes, docker guard CLI compatibility

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 14:25

What’s changed in 0.2.2

Follow-up to the 0.2.1 audit pass: personal-deployment hardening, chat-state
integrity fixes, and a compatibility pass that makes the validating docker
guard pass the stock docker CLI lifecycle — verified end to end on a live
daemon, including the full compose stack (networks, healthy egress sidecar,
foreground skill run with streamed output and auto-removal).

Security

  • Skill drafts are never executed. code_skill candidates now live in
    memory only and are checked statically (canonical Agent/Call/In/Out header +
    syntax parse without imports); accept_skill installs reviewed code without
    running it. The smoke-run path — which executed model-written code before
    confirmation, including freshly rewritten bodies under an already-allowed
    filename — is gone. coding.smokeArgs is retained for compatibility and
    ignored.
  • File grants are bound to the exact file. GET /api/files-token issues a
    short-lived grant for one decoded /files path; GET /files accepts the
    gateway key or that path-bound grant, and grants expire. Hosted JWT and
    companion gates are not bypassed; auth-off single-owner setups are unchanged.
  • The web client no longer attaches its file credential to third-party
    URLs
    (any URL containing /files/); only same-origin gateway file URLs
    are signed. The grant cache is dropped on login/logout/password change and
    in-flight responses from a previous session can no longer repopulate it.
  • Stored HTML cells are re-sanitized at both web render boundaries with
    the gateway's allowlist sanitizer (shared module), so cells stored before a
    sanitizer fix cannot bypass the current rules.
  • PWA embeddings follow the selected endpoint. An explicitly configured
    embedding URL gets only its own key (or an explicit no-auth request), and
    the fallback uses the active provider from the registry; the chat key can
    no longer ride to a different origin in either transport.
  • Docker guard hardening. Bind mounts must carry an explicit read-only
    mode outside /app/output (Docker mounts optionless binds read-write); the
    create-query name is validated, container network roles are enforced, and
    network properties (bridge driver, internal flag) are verified from the
    daemon's own inspect response.

Fixed

  • The docker guard now supports the stock docker CLI lifecycle — this was
    broken in 0.2.1, so every docker-sandbox skill run failed. The guard now:
    registers the hex IDs it created and allows lifecycle calls by them (foreign
    containers remain unreachable); relays the hijacked attach stream
    (HTTP Upgrade) for docker run -i; flushes long-poll (wait) response
    headers so the CLI proceeds to start; answers the CLI's pre-flight
    GET /containers/json with only claw2 containers; accepts the CLI's default
    LogConfig marker; and parses the daemon's array-shaped network inspect
    responses.
  • Partial forks no longer inherit a prompt recap that covers messages beyond
    the fork point (gateway and PWA).
  • Reminder delivery: scheduler ticks no longer overlap within one gateway
    process, and a stale acknowledgement cannot advance a recurrence twice. New
    reminders store UTC timestamps; legacy rows keep their previous
    interpretation.
  • The web client treats a chat stream that ends without the terminal JSON
    event as interrupted instead of success, and the full turn (both messages,
    transcript rows, chat timestamp and recap) is committed in a single SQLite
    transaction.
  • LLM-bridge replies are anchored to the exact polled message by ID; a newer
    room message no longer hijacks the turn.

Changed

  • Node 22 is the supported runtime: engines requires >=22.13.0 for
    source builds, CI runs on Node 22 and now builds and tests the web and PWA
    clients too, and the Docker image is rebuilt on node:22 (Debian) with the
    native build toolchain kept out of the runtime layer. A .dockerignore
    keeps local dependencies and secrets out of the build context.
  • Gateway /files responses set Cache-Control: private, no-store and
    Referrer-Policy: no-referrer, and serve audio/video with inline content
    types (they previously downloaded as octet-stream).

Full Changelog: v0.2.1...v0.2.2

claw2 v0.2.1 — fork & duplicate chats, security remediation pass

Choose a tag to compare

@bkisonka bkisonka released this 22 Nov 11:13

Everything below ships in one cut: the fork/duplicate-chats feature and a
security remediation pass (external audit + follow-up code audit).

Added

  • Fork and duplicate chats. Two entry points: "Duplicate chat" in the
    sidebar chat menu (full copy) and a per-message "Fork from here" button
    next to the copy button (branch cut at that message, after a confirm).
    The copy carries the history, project, per-chat model and prompt-summary
    context; pin/favorite are reset. Generated files stay shared between the
    original and its forks (media and documents surface in both), and a
    "Forked from chat …" banner above the log opens the original. (web,
    gateway, PWA)
  • Fork tree in the sidebar. Forked chats render nested under their
    parent in chain order with a connector line, collapse/expand and a
    "forked from …" tooltip; the same tree exists in the mobile client's
    chat list. Deleting a chat re-attaches its forks to the parent (graft) —
    the chain of reasoning stays connected.
  • Validating docker API guard (src/sandbox/docker-guard.ts).
    Replaces the generic docker-socket-proxy in the compose delivery: an
    endpoint allowlist (container/network lifecycle, image pull, health —
    no exec/build/volumes/swarm) plus structural validation of every
    container creation — mandatory hardening profile (cap-drop ALL,
    no-new-privileges, read-only rootfs), privilege widening rejected,
    bind sources restricted to the declared sandbox roots, containers and
    networks must be claw2-named, published ports / devices / host
    namespaces / restart policies / docker load refused. The guard also
    refuses operations targeting its own container.
  • Hosted (multi-user) isolation. Per-user config is default-deny
    filtered (only llm / assistant / voice / insights are
    user-settable — sandbox, fs allowlist, skills, channels, gateway policy
    stay operator-owned); an empty skills.allowlist is deny-by-default in
    hosted mode; skill authoring (POST /api/agents), /allow, gateway
    restart and remote-access control require the new
    gateway.auth.admins list; tenant-overridden llm.baseURL is
    DNS-validated (SSRF gate) and never inherits the operator's API keys.
  • Per-user file access token. GET /api/files-token issues a
    10-minute HMAC token; GET /files requires it whenever gateway
    authentication is on. This also fixes media (images/audio/video)
    failing with 401 under auth-on. Auth-off single-owner setups keep
    header-less /files as before.
  • Account hardening. Login/token verification enforce account status;
    JWTs carry a token version (password change invalidates outstanding
    tokens); brute-force limiter on login/register/password-change.
  • Symlink-safe filesystem layer (src/security/safe-fs.ts): every
    path component is verified (walk + realpath + O_NOFOLLOW opens) for
    the fs tools and /files serving; component identity re-checks detect
    mid-operation swaps. Planted symlinks in skill-writable mounts can no
    longer redirect reads/writes outside the sandbox roots.
  • Startup configuration-conflict warnings for the two compose sandbox
    conflicts that used to fail silently per skill run: uploads.hostPath
    outside the sandbox bind roots, and remote DOCKER_HOST without
    CLAW2_SIBLING_HOST_ROOT.

Changed

  • Chat attachment composer accepts up to 10 files (was 20); the
    gateway chat body limit is 224 MiB (was 512 MiB). The LLM-room body
    parser gained a 2 MiB streaming limit (was unbounded).
  • web_fetch streams the response with a byte counter and aborts at the
    limit instead of buffering the whole body first.
  • Registration (hosted) mode fails closed when sessionSecret is
    missing or shorter than 32 characters — the JWT gate no longer
    silently disappears.
  • GET /api/config tenant responses are policy-filtered and mask
    vision.recognizeSecret.

Security

  • Method-aware authentication: UI pages are public for GET/HEAD only;
    state-changing requests (including POST /chat) always require a
    verified identity in registration mode. /allow (skill approval) and
    skill authoring are admin-gated there.
  • Cross-site guard for auth-off deployments: requests marked cross-site
    by Origin / Sec-Fetch-Site are refused for state-changing routes
    (simple text/plain bodies used to reach the JSON parser).
  • Remote-access boundary: the HTTPS proxy stamps a per-process secret;
    the companion-auth path requires it, so the X-Claw2-Via header cannot
    be spoofed through the plain listener. A warning fires when remote
    HTTPS is open while the gateway binds non-loopback.
  • HTML-cell sanitizer hardened: entity/whitespace-encoded javascript:
    schemes (javascript:), data: navigations, CSS url()/@import
    exfiltration and <style> payloads are now stripped (vectors were
    model-output injectable; the PWA port already had the fix).
  • Cross-tenant file surface in hosted mode: /chat/session-files is
    scoped to the caller's own sessions; /chat/documents,
    /chat/assets-summary disk scans and DELETE /files require an owned
    session.
  • web_fetch, web.md hardening of unbounded reads; raw DB error text
    no longer reaches register clients; X-User-Id removed from CORS
    allow-headers; chat titles are capped server-side.

Full Changelog: v0.2.0...v0.2.1

v0.2.0 — open source under AGPL-3.0-only, CLA-based contributions

Choose a tag to compare

@bkisonka bkisonka released this 21 Nov 10:04

claw2 is now open source

Starting with this release, claw2 is licensed under the GNU Affero General Public License v3.0 only (AGPL-3.0-only) instead of the previous proprietary source-available license. The HSS core (hss.cjs) is under LGPL-3.0-only, which is compatible with AGPL-3.0. The "or any later version" option does not apply: the project is distributed under version 3 only, which is what makes the dual-license model below clean.

Why AGPL-3.0-only

The previous license permitted personal use only and forbade distribution — it protected against competition that did not exist and blocked the community this product needs. As a network service (gateway, web, API), claw2 needs a license that keeps forks open and closes the SaaS loophole:

  • Use, study, modify and redistribute claw2 for any purpose, including commercially.
  • Forks and modified versions you distribute must stay open under AGPL-3.0-only.
  • If you run a modified version as a network service, you must offer its source to your users (AGPL §13) — the anti-cloud-clone clause.
  • Contributions are accepted via a CLA with copyright assignment (see CONTRIBUTING.md), which is what allows clean commercial relicensing alongside AGPL.

What changed

  • LICENSE — canonical GNU AGPL-3.0 text; EULA.txt — removed (redundant and partially incompatible with AGPL)
  • SPDX headers and license prose across the tree: AGPL-3.0-only (HSS core: LGPL-3.0-only); verbatim license texts (LICENSE, COPYING, COPYING.LESSER) and third-party dependency licenses unchanged
  • NOTICE — rewritten; third-party components unchanged; trademark notice added
  • Contributions policy: copyright-assignment CLA (cla/CLA-individual.md, cla/CLA-corporate.md — English canonical, Russian translations provided); signatures collected as PRs to the cla-signatures branch; replaces the earlier "no CLA" rule
  • README.md / README.ru.md / LICENSE.ru.md — license sections rewritten; the README now leads with the pitch and the quick start
  • CONTRIBUTING.md — new: dual-license rationale, CLA signing process, alternative for non-signers

Nobody loses any rights: AGPL is strictly more permissive for personal use than the previous license. Contributors keep moral rights; a back-up license in the CLA guards against a failed assignment. The name "claw2" and the project logos are trademarks of Vitaliy Bondar — the license grants rights to the code, not to the branding.

Commercial licensing is also available on request — contact the copyright holder via the repository.

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

Choose a tag to compare

@bkisonka bkisonka released this 20 Nov 15:29

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.