Repository navigation
Releases
glowcap v0.1.6 alpha
glowcap 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.6
Added
-
glowcap apps rooms pageprints the link that opens the Rooms page with
the running server filled in.rooms-web --page-linkand the server's
/pageroute answer the same link, anddeployment upprints it first. -
rooms-serverandrooms-webannounce any of the seven listener
transports with--transport=<transport>. A relay transport registers at
--relay=<ws-url>orGLOWCAP_ROOMS_RELAY_URL, and underrooms-webat
that server's own relay.--relay-public=<ws-url>names that relay as
peers dial it when a port forward or a proxy gives it another address, and
rooms-web --http-public=<url>does the same for its own relay. The
installedglowcap apps roomscommands take the same listener options,
servewith--listenand the shared session's as--session-<option>,
andsession startkeeps every one of them in its settings. -
rooms-web --session-transport=<transport>chooses the shared session's
announced listener the same way, and--session-<option>passes any other
rooms-sessionoption to it. A relay listener registers at that server's
own relay unless--session-relaynames one, an onion listener publishes
through the private Tor the server runs, and the page is offered the
session through any listener a browser can open. -
A relay listener whose configuration names a relay alias advertises the
alias in itsrendezvous-relayhint. Behind a port forward or a proxy,
peers dial the route they reach while the listener's own register socket
opens at the route it reaches. -
The relay admits dials of one registered directory at the rate its peer
may register, so a tighter registration bound throttles the whole directory. -
A relay that cannot complete a dial closes the browser's socket with the
cause, and the page's channel reports that cause instead of a bare
connection close. -
rooms-server --listen=<transport>[,<name>=<value>...](or
GLOWCAP_ROOMS_LISTEN) opens another listener to the same directory, once
per transport, and the server starts only once every declared listener is
open. The address it prints then names the directory by its key with every
listener listed. -
The Rooms page reaches a directory through a sealed relay listener the
directory declares, with no Rooms server chosen, and the directory's card
says the route the connection took.
Changed
-
--capabilities=all, or--capabilities=<name>[,<name>...], tells
rooms-serverandrooms-webwhich operator capabilities to mint, with
GLOWCAP_ROOMS_CAPABILITIESas the variable. It replaces the six flags
--admin-listeners,--diagnostics,--operator,--peering,--irc, and
--traceand their variables, so name the capabilities you want in one list.
A deployment or script that set those variables mints nothing until it
names the capabilities inGLOWCAP_ROOMS_CAPABILITIES. Reading the kept
capabilities again isglowcap apps rooms capabilities, or
rooms-web --print-capabilities, which takes the locators from the running
web server, from--url, or fromGLOWCAP_ROOMS_LOCATOR.rooms-server
no longer reads them, andglowcap apps rooms directory capabilitiesis
gone. -
The shared session writes its use link to
use.sturdyrefand its management
link tomanagement.sturdyrefin the state directory, the names every page
gives those links. The managed deployment's readiness file is
/run/rooms-session/use.sturdyref. Both files are rewritten at every start,
so an existing state directory needs no change. -
Four Rooms page names changed. The Settings tab Reachability is
Connection. The Operations tab Directory is Operator. The
Settings act Delete local session is Empty this session, since it
empties the open session and the browser stays on it, and the shared
session's Reset shared session is Empty this session for everyone
for the same reason. -
Rooms page copy says link, session, and message where it said capability,
workspace, and line. On a room card, the Capabilities tab is Links,
and every button on it grants, revokes, or discards a link. -
The Rooms deployment's managed Compose file holds only the settings every
deployment shares. Every setting a host chooses lives in
docker-compose.override.yml: the public address, allowed pages, trusted
proxies, trace routes, TURN, and admission overrides. The example override
shows public hosting behind an HTTPS proxy. A variable exported in the
shell that runsdeployment updoes not reach the services: move it
into the override. -
glowcap apps rooms deployment reset directorynames the unit that was
state, anddeployment upprints the directory locator and the shared
session's use link and management link under those names. -
Delete browser data in the Rooms page also forgets every Rooms
preference this browser kept: the chosen server, other tabs' session
choices, and the theme. Other open Rooms tabs reload. -
Every exported symbol of the nine
@glowcapJSR packages carries a doc
comment, including the generated C ABI constants and struct layouts, so
each package's documentation score on jsr.io reports no undocumented
symbol. -
A page with no Rooms server asks for one only for an address the browser
cannot open itself, and says which listener failed when one did. A relay
that does not answer is named on the join card. -
Every ask for a Rooms server says what the act needs one for. The needs
are an address this browser cannot open on its own, the home directory a
blank address means, a link other people reach this browser through, and
direct messages in the mode that goes through the server. -
Attaching to a session, holding a management control, taking an archive
peer, and holding an operator capability judge the pasted link by the
listeners its address names, so a session shared from another browser
attaches with no Rooms server. The ask comes only for a link this browser
cannot open on its own, and a break on the way to a session reached through
its relay listener names that relay. -
A blank directory address on a page with no Rooms server is refused on its
own field instead of asking for a server. -
The Session tab offers its unfinished-changes list only while a change is
unfinished, and the Connection tab drops this browser's own address,
which nothing on the page accepted. -
rooms-webserves its page before its directory is up, so the directory's
relay listeners can register with it, and/locatorwaits for the directory
instead of answering that there is none. -
GLOWCAP_ROOMS_SESSION_STATEserves the shared session the way
--session-statedoes, and the option wins when both are set. -
The host bindings in Rust, TypeScript, and Racket name a transport they have
no connector for asUnknownTransport, the name the Zig host uses for the
same condition, so one reader recognizes it from every binding. -
A C ABI content registration holds up to 128 methods, where it held 64. A
registration over the cap is refused withGLOWCAP_ERR_INVALID_ARGUMENT
and the last errorloam: TooManyMethods, so a too-long method table is
told apart from a missing callback. -
rooms-webprints one block at startup: the addresses first, then the
links to keep private under their own heading. A directory it runs hands
itsROOMS-*links to that block, and a restarted directory prints its
new links under the same heading. The directory's work budgets and their
counts read on the operator page under Work budgets. The HTTP,
browser, and session budgets come from your own arguments and are not
printed. -
The operator page's Rooms and their links section lists every room
someone is in and every room a link or a saved record stands for,
including rooms nobody is in, one line per room with a tag for each link
that stands. Links… opens a card for that room where each link is
issued, copied, and revoked. Forget room removes the room entirely:
its members, every link, its subject, its kept messages, its name, and its
settings. An IRC bridge's row takes no manager link and cannot be
forgotten here, and says so. A room's row carries each link itself in
place of an issued flag, and issuing a link answers the row as data, so
nothing enters the session's storage. The factory reset says that it
clears manager links too. -
Anyone in a room can take its manager link or moderator link there,
however they came in, and the room card's links tab says so. A room
answers its identity digest and its manager's identity to anyone in it,
which is how a link is checked against the room. A digest opens nothing. -
Commands answer where you typed them.
/link,/moderator,/kick,
/subject,/msg, and/invitesay the link, the refusal, or the way in,
in the conversation./link <room>for another room you are in answers in
place, and for one you are not in says to join it first./invitein a
room you joined by name says the room is not yours to hand on and names
the way in. -
/msgand/inviteto a name nobody registered say so./whoisin a
direct message answers about the person on the other end. Sending a third
line while two are still on their way says so. -
Commands take exactly their arguments. `...
glowcap v0.1.5 alpha
glowcap 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.5
Added
- The Rooms page is published at https://glowcap.org/rooms/app/ with the
website. A Rooms server lets that page use it unless--allow-origin(or
GLOWCAP_RELAY_ALLOW_ORIGINS) lists other pages. The link it prints under
open the page opens the page with this server. The page names the
browser's local network permission when that is what stands in the way. --http-public(orGLOWCAP_ROOMS_HTTP_PUBLIC) names the address browsers
reach a Rooms server at, so the links a deployed server prints are ones
other people can open.- The Rooms server card in Settings shows the server's address to copy.
- The theme chosen on the website or in the Rooms page it publishes is one
choice: both keep it under the same browser key. A presentation export
still carries it with the other view preferences. - Joining a room, connecting to a directory, or messaging someone from a page
with no Rooms server asks for one in place, the way Attach does, and the
page comes back to that act once the server is saved. rooms-web --export-static=<directory> --base=<path>writes the page as
plain files for any static host. It replaces only an export it wrote, and
a failed export leaves the one in place untouched.- A session's home directory is chosen in Settings. A room joined without a
directory address opens there, the choice is offered again after a Rooms
server restart, and a home that stopped answering stays visible.
Changed
- The release workflow points the Racket package catalog at each release's
binding archive and installs the package from the catalog, so a release
reaches Racket users without a maintainer editing the catalog entry. --allow-origin=with an empty value lets no other page in, and an option
given without its value names the form the help shows.- A session opens without a relay, and a page that did not open says why,
with Reload on a tab that has chosen no session. - Closing a Rust browser channel answers only a failure to retire the socket
itself. A channel that failed earlier closes cleanly, and that first failure
stays the answer to its reads and writes.
Every release is listed in the changelog.
Choose a download
For the CLI, Rooms, and agent skills, choose CLI + Rooms.
Its filename starts with glowcap-v0.1.5-. The C SDK starts with
glowcap-c-v0.1.5- 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.
For browser applications, download the browser bundle.
It includes prebuilt JavaScript, matching Wasm, and an example page. Extract
it into a new directory your web server serves and open index.html.
The Rust crate downloads the WebAssembly libraries
automatically when targeting wasm32-unknown-unknown. The archive includes
the matching C headers.
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.5 shTo do the same by hand, download your product archive and SHA256SUMS.
For example, on an Apple Silicon Mac:
archive=glowcap-v0.1.5-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.5 --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:b47e0c5bd0d87dddda8f1387dbd94f9bc35ad54148348dfdc23282c5ad0367e8. 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:b47e0c5bd0d87dddda8f1387dbd94f9bc35ad54148348dfdc23282c5ad0367e8 --repo glowcap-org/glowcapInstall a language package
Each package is version 0.1.5 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.5
pip install glowcap==0.1.5
deno add jsr:@glowcap/runtime@0.1.5 jsr:@glowcap/tcp@0.1.5
raco pkg install glowcapDeno's default dependency-age policy
delays new versions for 24 hours. Add an exception for the glowcap packages if
you need this release sooner.
The publish workflow uploads
the packages and points the Racket catalog's glowcap entry at this release's
source package. It 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.5 source. The browser files in the
product are the Rooms app...
glowcap v0.1.4 alpha
glowcap 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.4
Added
- A browser bundle with prebuilt JavaScript, matching Wasm, and a complete WebRTC
example. Serve its files directly without a compiler or repository checkout. - Prebuilt WebAssembly libraries that the Rust crate downloads when building
for the browser.
Changed
- Reduce event-queue overhead while preserving capacity reserved for promise
retirement.
Fixed
- Refresh build command environments on every invocation so release checks
use newly installed tools and the current GitHub step settings. - Load browser Wasm from ordinary binary responses as well as streaming Wasm
responses, and report HTTP errors before trying to compile them. - Complete package setup examples, correct browser relay routes, and use
installed Racket collection imports. - Verify newly published JSR packages without waiting for Deno's dependency
age window. The release check imports all nine packages and keeps the age
policy for third-party dependencies. - Resume partial release uploads with the original checksums, attestations,
and release notes. - Ship the Racket binding as a release archive. The catalog can install it
without checking out repository symlinks that Racket refuses to extract.
Every release is listed in the changelog.
Choose a download
For the CLI, Rooms, and agent skills, choose CLI + Rooms.
Its filename starts with glowcap-v0.1.4-. The C SDK starts with
glowcap-c-v0.1.4- 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.
For browser applications, download the browser bundle.
It includes prebuilt JavaScript, matching Wasm, and an example page. Extract
it into a new directory your web server serves and open index.html.
The Rust crate downloads the WebAssembly libraries
automatically when targeting wasm32-unknown-unknown. The archive includes
the matching C headers.
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.4 shTo do the same by hand, download your product archive and SHA256SUMS.
For example, on an Apple Silicon Mac:
archive=glowcap-v0.1.4-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.4 --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:6df85d29aa2b234835bd0f3b956b6c7a90576075555fa161a4e77f3771c647f3. 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:6df85d29aa2b234835bd0f3b956b6c7a90576075555fa161a4e77f3771c647f3 --repo glowcap-org/glowcapInstall a language package
Each package is version 0.1.4 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.4
pip install glowcap==0.1.4
deno add jsr:@glowcap/runtime@0.1.4 jsr:@glowcap/tcp@0.1.4
raco pkg install glowcapDeno's default dependency-age policy
delays new versions for 24 hours. Add an exception for the glowcap packages if
you need this release sooner.
The Racket catalog points to this release's
source package.
The 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.4 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: 396c02d64899e17b62fb77e1d9071205eb896083. Release run.
glowcap v0.1.2 alpha
glowcap 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"...glowcap v0.1.1 alpha
glowcap 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.1
Added
- Rust, Python, TypeScript, and Racket packages are published from the release
tag:glowcapon crates.io and PyPI,@glowcap/*on JSR, andglowcapin
the Racket catalog. Each downloads the C libraries of its version on first
use and verifies them against the release checksums. - Release notes carry a platform download table, verification and install
steps, a package install section, and this changelog's entry for the version. - Every release archive, the checksum file, and the Rooms container image
carry a build provenance attestation thatgh attestation verifychecks
against this repository. The provenance bundle of each download is published
beside it for offline checks, and the image's software bill of materials is
attested with the image. - The C SDK archive ships a README with a runnable C example.
Changed
- A binding outside a checkout downloads its own version unless
GLOWCAP_SKIP_DOWNLOADis set. Inside a checkout it useszig-outand
downloads only withGLOWCAP_DOWNLOAD. The contract'sreleases_published
switch is gone. - Release archives omit empty directories, and their README and provenance
links resolve from an extracted archive.
Fixed
- A release whose archive or image job was skipped is refused instead of
publishing nothing. Publication can be recovered from the signed tag's
original run without rebuilding or moving the tag.
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.1-. The C SDK starts with
glowcap-c-v0.1.1- 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.1 shTo do the same by hand, download your product archive and SHA256SUMS.
For example, on an Apple Silicon Mac:
archive=glowcap-v0.1.1-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.1 --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:1010fda6d08fd9a930cdad5135ab3b5e1ec10304e80c7e81a040e56434270325. 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:1010fda6d08fd9a930cdad5135ab3b5e1ec10304e80c7e81a040e56434270325 --repo glowcap-org/glowcapInstall a language package
Each package is version 0.1.1 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.1
pip install glowcap==0.1.1
deno add jsr:@glowcap/runtime@0.1.1 jsr:@glowcap/tcp@0.1.1
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.1 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: 153e593cc1c871c6c3dd966a557d4afefc6c8965. Release run.
glowcap v0.1.0 alpha
Choose a download
For the CLI, Rooms, browser assets, and agent skills, choose CLI + Rooms.
Its filename starts with glowcap-v0.1.0-. The C SDK starts with
glowcap-c-v0.1.0- and contains headers and libraries for building applications.
The SDK does not contain the CLI or Rooms.
| Platform | Product | Libraries | Requires |
|---|---|---|---|
| macOS, Apple Silicon (M1 and later) | 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 |
Windows and Linux musl distributions, including Alpine, have no prebuilt package.
GitHub's automatic Source code downloads contain source for building.
They are separate from the compiled downloads above.
Verify and install the product
Download your product archive and SHA256SUMS.
For example, on an Apple Silicon Mac:
archive=glowcap-v0.1.0-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.
With the GitHub CLI installed, also verify the signed publication attestation:
gh attestation verify "$archive" \
--repo glowcap-org/glowcap \
--signer-workflow glowcap-org/glowcap/.github/workflows/release.yml \
--predicate-type https://glowcap.org/attestations/release-publication/v1Then 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.
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.0 --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.
Libraries, source, and license
Zig users can depend on the v0.1.0 source. Rust,
Python, TypeScript, and Racket users can build the tagged
language bindings. The browser files in the
product are the Rooms application, not a separately published binding package.
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: 37c545ff231ccbfec305aba4fb8efe05dae8ee35. Original artifact run.