Skip to content

Cloister 0.3.0

Choose a tag to compare

@yi427 yi427 released this 10 Oct 06:47
· 6 commits to main since this release
f883ea1

Cloister 0.3.0

Release tag: v0.3.0. The matching base image is
ghcr.io/yi427/cloister:0.3.0.

This breaking release uses Profile V7. Older Profiles are rejected; no migration
or backwards compatibility is provided. Create a new Profile explicitly.

The base image no longer downloads or includes Codex or Claude Code. First use
installs the selected official npm package in a dedicated preparation container.
Cloister manages automatic update checks, exact-version selection, and cached
offline launches independently of the base image release.

Base tool Version
Node.js 24.19.0
Rust 1.97.1

Profile [agent] now requires codex, claude, and update_interval_hours in
addition to state. Versions accept latest or an exact stable semantic version.
New Profiles select latest and a 24-hour check interval. --agent-version,
--update-agent, and --offline expose per-invocation controls.

Each Agent session uses an OS-allocated bridge port, a separate bearer token,
execution records, fixed workspace, and named container. Explicit ports remain
available. Installation uses a cross-process lock and atomic inventory updates;
running sessions keep their software directory while new versions are prepared.

Software caches are separate from credentials and mounted read-only in Agent
sessions. Preparation containers receive no workspace, Agent credentials, or Host
MCP token. Shared Agent state is still shared across projects when selected.
The workspace remains read-write and Host Exec still runs with macOS user
permissions. Network access remains unrestricted by Cloister's default network.

Automatic update failures reuse an installed version with a warning; first-use
and explicit-update failures stop launch. Corrupt metadata fails closed. Old
software versions remain on disk; automatic garbage collection is deferred.
--offline disables software downloads/checks only, not Agent network access.

CLI/image pairing now covers base runtime integration only. Independent Agent
updates may introduce upstream integration incompatibilities; record actual
versions during acceptance and select an exact version to recover.

SIGINT, SIGTERM, and SIGHUP request container and bridge cleanup. Runtime removal
failures report the container name. SIGKILL and machine failure cannot guarantee
cleanup.

Readiness checks recognize both Apple container PF-anchor layouts and verify
container-to-host HTTP connectivity with a bounded, isolated temporary container.
DNS and on-disk forwarding configuration alone do not establish connectivity.

Real Apple-container smoke checks passed, and the user accepted the current
development build on 2026-10-10; see the
acceptance record for the tested versions and
coverage limits. Authenticated task, tool-approval, and Host Exec behavior were
not independently recorded against every subsequently installed Agent version.

Release validation on 2026-10-10

  • Local make verify passed all 212 tests and Clippy; GitHub CI passed for the release commit f883ea1901188dfad0bf9610e07321907c5b23f4.
  • Anonymous GHCR access, Linux ARM64 architecture, and the image's source revision were verified. The exact image digest is sha256:bf2528421b37aaf89863a76576b0a4375e8841c3549a99481d5cbe07733ff02d.
  • Installation from v0.3.0 with cargo install --locked, Homebrew source installation, strict online audit, and brew test passed.
  • The published base image started with Node.js 24.19.0 and Rust 1.97.1, with neither Agent preinstalled.
  • Isolated-state first-use launches installed Codex 0.162.1 and Claude Code 2.1.296. Cached offline launches, exact installed-version selection, an explicit update check, and two concurrent Codex launches with distinct bridge ports passed.
  • init and the upgraded default Profile passed readiness checks, including actual container-to-host connectivity. The final local check reported no warnings.

These release smoke checks did not perform authenticated model tasks. Agent software remains independently updated; these versions identify the tested launches.