Repository navigation
glowcap v0.1.2 alpha
Pre-releaseglowcap is a Zig library for capability-based networking (OCapN and CapTP) and
durable application state, with a CLI, the Rooms chat app, and packages for
Rust, Python, TypeScript, and Racket. This page is the complete release: every
download, how to verify it, and how to install each piece. Read the
documentation, report a problem in the
issues, and report a vulnerability as
SECURITY.md describes.
What changed in 0.1.2
Added
- Build-time interface generation feeds the Tasks client from authored Tasks
and shared Loam definitions. Rust calls check declared replies and keep
prepared mutation requests for explicit replay. Creation and read handlers
in Zig check their declared arguments and results. - Generated Rust and TypeScript callers preserve positional calls, named
methods, omitted arguments and explicit undefined values. Both decode lists,
tuples and tagged records. TypeScript keeps arbitrary bigint integers and
checks text bounds in UTF-8 bytes. - Interface text supports rooted imports and positional containers. The
compiler checks the complete authored bundle against independent Syrup
descriptions. These are qualified projections, not a general-purpose
interface compiler or an adopted language. - Rust
Ref::retain_forowns a capability independently of the original
reference's explicit release. Prepared Rust calls retain their target and
reference arguments before acquiring a mutation sequence. - Product and C SDK archives include the original license and attribution
texts for their bundled Rust and JavaScript dependencies.
Changed
- Zig event consumers use
Event.kind()instead ofEvent.tagand access
wire data only on wire events. For cross-session promise forwarding, custom
Nodeembeddings installNode.pipeline_projectionand dispatch callable
deliveries and retirement events in FIFO order.Hosthandles both. - Zig driver callers replace
AcceptIdentitywithIdentity. Keyed
identities use.keyed = keyinstead of a secret/designator struct. The
unused designator override anddialedDesignatorhelper are removed.
Caller-supplied iroh endpoints must share the Host's identity seed.
Fixed
- Calls queued on a promise keep working when it settles to an object on
another session. Forwarded capability replies retain their references until
their owners release them. If allocation failure prevents even a failure
reply, the source session closes rather than leaving the call pending. - Callbacks can claim a reference's session when an ordinary Host call drives
the callback outsidestep. A released session cannot be reclaimed while
its teardown is pending. - The Racket iroh connector uses its Host's identity for the endpoint. The
Goblins iroh adapter checks claimed locators against authenticated endpoints
even with tracing disabled. - The Goblins Rooms peer rejects calls and late introductions to a DM inbox
after its registration ends, including when someone reuses the nickname. - A refused TypeScript
Host.closeleaves the Host usable and keeps later
errors visible. - Rooms link previews reject non-public special-purpose IPv6 destinations
and the local-use NAT64 prefix. - Goblins comparison runs stop on failed or stalled children instead of
retrying failed samples or counting them as successful measurements. The
performance pages contain a complete fresh run and label language
throughput in task-board units. - Build-step documentation checks use the same reference graph regardless
of the caller's optimization flags. - The Racket catalog setup uses a Git source URL, so the package manager
checks out the selected release and its binding directory instead of
treating the GitHub page as a package download directory. - TypeScript packages imported over HTTP load their bundled release settings
without treating the module URL as a local file path. Published JSR imports
can use the versioned SDK cache and automatic downloads. - Generated TypeScript calls support checked
awaitwhile preserving raw
pipelining. The export namethenis refused, but a wire method can still be
namedthen. - The interface CLI refuses output paths that name an input or import, including
symlink aliases. It writes output atomically and preserves existing regular
file permissions. Invalid targets, selections and API names report contextual
errors without a Zig trace. - Tasks clients in Rust, TypeScript, Python and Racket order mutations per client
while allowing reads to proceed independently. Overlapping identical actions
no longer collapse into one receipt. - A failed first watcher poll in TypeScript, Python or Racket attempts
cancellation and preserves the original failure alongside any cleanup error. - Rust and TypeScript clean up discarded references in generated and internal
replies, and after failed fetch/enliven calls, when automatic release is
disabled. Successful manual results keep their existing release policy.
JavaScript aliases retain their shared finalizer lifetime. - A failed session open or handshake keeps its original error when channel
cleanup also fails. Cleanup runs once and remains visible beside that error. - The portable deadline wrapper reaps children that exit during group signalling
on macOS, while preserving real signal-permission failures. - Pending calls settle with their original failure when progress or close
fails. Cleanup failures preserve the primary construction error. - Rooms and its test processes use the ports their children actually bind,
avoiding races from choosing a free port before starting a listener. Room
selection waits for directory registration before opening the session. - The TypeScript argument encoder rejects sparse arrays instead of silently
converting missing slots into integer zero. - The C SDK archive ships the WebRTC transport's shared library and header
beside the iroh one, so the Rust crate'swebrtcfeature links against the
release SDK instead of failing to findlibglowcap_net_transport_webrtc. - Every
@glowcap/*package publishes to JSR. The runtime's generated FFI
loaders and the relay's serve entry reach their own package by relative path,
which JSR requires, and the browser import maps carry the file entry that
keeps the Wasm adapter in place of the C library loader. - The package pages on crates.io, PyPI, JSR, and the Racket catalog read as
package home pages: each opens with the package name and install line, leaves
the package only through absolute links, and keeps contributor checks in the
repository. Every@glowcap/*package ships a README, andsource-check
holds both rules.
First-run examples name their server and runtime requirements. The Zig
package's README links work without a repository checkout.
Every release is listed in the changelog.
Choose a download
For the CLI, Rooms, browser assets, and agent skills, choose CLI + Rooms.
Its filename starts with glowcap-v0.1.2-. The C SDK starts with
glowcap-c-v0.1.2- and contains headers and libraries for building applications.
The SDK does not contain the CLI or Rooms.
| Platform | Product | Libraries | Requires |
|---|---|---|---|
| macOS, Apple Silicon | CLI + Rooms | C SDK | macOS 15.0.0 or newer |
| macOS, Intel | CLI + Rooms | C SDK | macOS 15.0.0 or newer |
| Linux, ARM64 | CLI + Rooms | C SDK | glibc 2.39.0 or newer |
| Linux, x86-64 | CLI + Rooms | C SDK | glibc 2.39.0 or newer |
The Linux archives need the glibc version shown or newer. ldd --version prints
yours. Windows and musl distributions such as Alpine have no prebuilt package.
GitHub's automatic Source code downloads contain source for building and are
separate from the compiled downloads above.
Verify and install the product
One command downloads this release for your machine, verifies it against
SHA256SUMS, and runs the product's installer:
curl -fsSL https://glowcap.org/install.sh | GLOWCAP_VERSION=0.1.2 shTo do the same by hand, download your product archive and SHA256SUMS.
For example, on an Apple Silicon Mac:
archive=glowcap-v0.1.2-aarch64-macos.tar.gz
shasum -a 256 "$archive"On Linux, choose the Linux archive and use sha256sum "$archive" instead.
Compare the result with the same filename in SHA256SUMS.
Every archive and SHA256SUMS carries a signed build provenance attestation
from this repository's release workflow. With the GitHub CLI 2.49 or newer:
gh attestation verify "$archive" --repo glowcap-org/glowcapThe same check works offline with the bundle published beside each file:
gh attestation verify "$archive" --repo glowcap-org/glowcap --bundle "$archive.sigstore.json"Then extract into a new directory and install the complete product:
mkdir glowcap-unpacked
tar -xzf "$archive" -C glowcap-unpacked
./glowcap-unpacked/bin/glowcap install
export PATH="$HOME/.local/bin:$PATH"
glowcap help
glowcap apps rooms serveOpen the browser URL printed by serve. Ctrl-C stops the service.
Add the PATH entry to your shell configuration. Keep the installed product's
files together, rather than moving only bin/glowcap. To remove an
installation, delete its directory under ~/.local/lib/glowcap/ and the
~/.local/bin/glowcap link.
macOS executables are not Developer ID signed or notarized. After verification,
use Open Anyway under System Settings, Privacy & Security if macOS
blocks execution. Keep Gatekeeper enabled.
Inside the product, bin/glowcap is the CLI, libexec/ contains Rooms services,
share/glowcap/rooms/ holds browser assets, and share/glowcap/skills/ holds
agent skills. Installation and Rooms commands.
Use the C SDK
Extract the C SDK into an empty directory. Use include/ and lib/ with
your C compiler, following the C ABI guide.
It has no CLI to install. Use libraries from the same SDK build.
Run the Rooms container
The public image supports Linux amd64 and arm64. Docker selects the architecture,
including on macOS with Docker Desktop. This command keeps state in a named volume:
docker run --rm --name glowcap-rooms \
-p 127.0.0.1:8080:8080 \
-v glowcap-rooms-state:/state \
-e GLOWCAP_ROOMS_STATE=/state \
ghcr.io/glowcap-org/glowcap-rooms:v0.1.2 --http-bind=0.0.0.0Open http://127.0.0.1:8080. The web port is local to this machine. The directory
uses encrypted iroh discovery and can be reached by peers holding its locator.
For persistent supervised hosting and HTTPS, use the
deployment guide.
The image's digest is sha256:b3dea6a2b51a5fdfc1a4bc236646919fae0b2002f7952e39ce78bb91143b7f03. Its build provenance and its software
bill of materials (SPDX) are attested
in the registry:
gh attestation verify oci://ghcr.io/glowcap-org/glowcap-rooms@sha256:b3dea6a2b51a5fdfc1a4bc236646919fae0b2002f7952e39ce78bb91143b7f03 --repo glowcap-org/glowcapInstall a language package
Each package is version 0.1.2 and downloads this release's C SDK for its
platform on first use, verified against SHA256SUMS. Set GLOWCAP_LIB_DIR to
an extracted SDK's lib/ to use a local copy instead.
cargo add glowcap@=0.1.2
pip install glowcap==0.1.2
deno add jsr:@glowcap/runtime@0.1.2 jsr:@glowcap/tcp@0.1.2
raco pkg install glowcapThe packages are uploaded by the
publish workflow, which starts
when this page is published and waits for the maintainer's approval at each
registry, so a registry can lag this page by a few hours. The
bindings guide lists every package. Zig users
depend on the v0.1.2 source. The browser files in the
product are the Rooms application, not a published package.
Source and license
Apache-2.0 alpha software. APIs, ABIs, and storage formats may change before 1.0.
Read the project provenance and the LICENSE-APACHE
and LICENSE-THIRD-PARTY files included in each archive.
Source commit: 3ccf153c71b0912518469702638e07fc86c80a5a. Release run.