xcb v0.20.10

A stopped Codex run on a shared account is freed when another run already saved its own refresh. (0.20.9 was tagged with a mis-edited changelog heading and never published; this release carries its change.)

Changes

• xcb recover now also frees a run whose Codex copy was refreshed at a different moment than the saved sign-in, as long as both belong to the same account. 0.20.8 only accepted a saved sign-in refreshed later, but concurrent runs often finish with the saved one earlier. The saved sign-in is kept and never overwritten; equal or unreadable refresh times still refuse.

Install

Install the native xcb binary from this release. The installer downloads the archive for your platform, checks it against its .sha256 file, and installs ~/.local/bin/xcb:

git clone --depth 1 --branch v0.20.10 https://github.com/hraness/xcb.git xcb
cd xcb && XCB_VERSION=0.20.10 ./scripts/install-native.sh

On Windows x86_64, this installs xcb.exe from the release's .zip into %LOCALAPPDATA%\Programs\xcb\bin. It is not code-signed, and Claude Code and Codex run only in the Linux build inside WSL2:

$env:XCB_VERSION = '0.20.10'; irm https://raw.githubusercontent.com/hraness/xcb/v0.20.10/scripts/install.ps1 | iex

Install the TypeScript SDK and xcb-compat CLI from the release tarball:

npm install https://github.com/hraness/xcb/releases/download/v0.20.10/hraness-xcb-0.20.10.tgz

Verify

• Checksums: SHA256SUMS lists the SHA-256 of hraness-xcb-0.20.10.tgz, and each xcb-0.20.10-<platform>.tar.gz and xcb-0.20.10-windows-x86_64.zip has its own .sha256 file.
• Source commit: a50946ffe65201aea70333da0713ffaa059c31c7
• Build provenance: gh attestation verify xcb-0.20.10-<platform>.tar.gz -R hraness/xcb. The publishing guide describes how each file is built and checked.