Skip to content

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