Repository navigation
What's new in 0.9.0
Full list: CHANGELOG.md.
Operator actions on upgrade
- Source builds need Rust 1.89 (was 1.88), required by the patched
rusqlite(ADR-189). Prebuilt binaries and Homebrew are unaffected. - Bot readers stop after an HTTP/API 409 and stay stopped until an explicit local reconciliation; fenced and transferred sources cannot reconcile. See the bot-reader runbook (#146).
Highlights
- New adapter:
agy(Google Antigravity CLI) forcs tackleworkers and as a pilot provider incs sessions launch. The pane command is portable POSIX sh. [harvest] on_pane_died = "merge" | "mark"in.cosmon/config.toml:markrecords the worker's exit and leaves the molecule in the harvest queue instead of runningcs done. Default staysmerge.cs donereports a post-merge-gate rollback as a rollback: the action list (text and--json) readsmerge rolled back by post-merge gate (NOT merged)instead ofmerged; exit code 1 and the molecule staying harvestable are pinned by tests.- Cross-machine
workexchange (#147): a container acceptance run where twocosmon-remoteclients with distinct OIDC identities exchangeworkmessages through the RPP adapter. - Container witnesses for harvest grants, remote harvest refusals, the legacy
required = trueupgrade and service crashes inside the gate andpost_mergewindows (#128). - opencode liveness probe now matches only a full
> <mode> · <model>line. - Security: bundled SQLite via
rusqlite0.41.1 (RUSTSEC-2026-0459) andrmcp3.9.0 for the MCP transport (RUSTSEC-2026-0462).
Signed release
Every binary attached below is reproducibly built (cargo build --release --locked, SOURCE_DATE_EPOCH pinned), cosign-signed (keyless, Sigstore),
and anchored in the public Rekor transparency log. An SPDX SBOM is attached
per target.
Install
All three routes below deliver the same signed bytes — the tarballs
attached to this release. They cover macOS and Linux alike, on arm64 and
x86_64 (Linux builds are statically linked against musl, so no glibc version
to match).
Native install script (recommended, macOS + Linux):
curl -fsSL https://noogram.org/cosmon/install.sh | sh
cs --versionIt detects your platform, downloads the matching tarball, and fails closed
if the sha256 does not match the published SHA256SUMS.
The installer itself is attached below as cosmon-install-<version>.sh, signed
and Rekor-anchored like the binaries. Piping it into sh consumes it before
that signature can be checked, so if you want the signature to actually do work
— shared machine, CI, first install — take the verify-then-run form instead:
ver=<version> # the release version, without the leading v
base="https://github.com/noogram/cosmon/releases/download/v${ver}"
curl -fsSLO "${base}/cosmon-install-${ver}.sh"
curl -fsSLO "${base}/cosmon-install-${ver}.sh.sig"
curl -fsSLO "${base}/cosmon-install-${ver}.sh.pem"
cosign verify-blob \
--certificate-identity-regexp 'https://github.com/.*/cosmon/.github/workflows/release.yml@.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--signature "cosmon-install-${ver}.sh.sig" \
--certificate "cosmon-install-${ver}.sh.pem" \
"cosmon-install-${ver}.sh" \
&& sh "cosmon-install-${ver}.sh"The && is load-bearing: cosign verify-blob exits non-zero on anything it
cannot tie back to release.yml at a cosmon tag, and that exit status is what
stops the script from running.
Homebrew (macOS + Linuxbrew):
brew install noogram/tap/cosmon
cs --versionThe tap formula points at these very tarballs; brew checks the same digests.
From source (any platform with a Rust toolchain, MSRV 1.89):
cargo install --git https://github.com/noogram/cosmon.git --locked cosmon-cliThis compiles locally, so it produces your binary rather than the signed one
attached here — the verification steps below apply to the first two routes.
Verify the binary you installed
cosign verify-blob \
--certificate-identity-regexp 'https://github.com/.*/cosmon/.github/workflows/release.yml@.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--signature cosmon-<version>-<target>.sig \
--certificate cosmon-<version>-<target>.pem \
"$(which cs)"
# exits 0 on a green signatureSelf-host the remote service
Each target also ships a cosmon-service-<version>-<target>.tar.gz bundle
containing the cosmon-rpp-adapter (HTTP fente) and cs-oidc-mock (demo IdP)
binaries — signed and Rekor-anchored like the cs tarball. The
Run cosmon as a remote service
how-to deploys directly from this bundle; no Rust toolchain required.
Full operator instructions:
docs/guides/release-verification.md.
Full Changelog: v0.8.0...v0.9.0