Relay

The v0.5.0 GitHub release was published on 27 September 2026 (Pacific time) and attaches the wheel, the source archive and SHA256SUMS.txt. The wheel and source archive digests in SHA256SUMS.txt match the digests PyPI reports for flywheel-relay 0.5.0. The release drops PATH entries that reach the folder a child works in, from the lookup and from the child's PATH, including for the git that --auto-commit runs. The folder of the interpreter relay runs on stays, and on Windows so do the Windows, System32 and SysWOW64 folders. When the working folder is a filesystem root or holds the home folder, only the entry naming that folder itself leaves. The release notes list the remaining limits.

PyPI serves flywheel-relay 0.5.0. A clean virtual environment installed it from PyPI on 27 September 2026, pip reported the installed version as 0.5.0, and relay --help listed the --health and --online options. This is distribution evidence; it does not establish that every feature works on every platform.

High severity security advisory, published on GitHub on 27 September 2026 (Pacific time). Affected: flywheel-relay before 0.5.0. Fixed in 0.5.0; install 0.5.0 or later. No CVE is assigned.

The v0.4.0 GitHub release was published on 26 September 2026 (Pacific time) and attaches the wheel, the source archive and SHA256SUMS.txt. The wheel and source archive digests in SHA256SUMS.txt match the digests PyPI reports for flywheel-relay 0.4.0. The release gives every child program an environment allowlist, runs the claude and codex tiers in an isolated empty folder, and keeps session reads inside the session store.

PyPI serves flywheel-relay 0.4.0. A clean virtual environment installed it from PyPI on 26 September 2026, and pip reported the installed version as 0.4.0. This is distribution evidence; it does not establish that every feature works on every platform.

High severity security advisory, published on GitHub on 26 September 2026 (Pacific time). Affected: flywheel-relay before 0.4.0. Fixed in 0.4.0. GHSA-82fg-qprm-q5r7 also affects 0.4.0, so install 0.5.0 or later. No CVE is assigned.

Medium severity security advisory, published on GitHub on 26 September 2026 (Pacific time). Affected: flywheel-relay 0.2.0 and later releases before 0.4.0. Fixed in 0.4.0. GHSA-82fg-qprm-q5r7 also affects 0.4.0, so install 0.5.0 or later. No CVE is assigned.

Relay 0.2.0 GitHub release resolves to commit 9efdd82a6ea47ea37b4771315529aa4a8b04de1b and is not draft or prerelease. Download-back verification covered relay_agent-0.2.0-py3-none-any.whl at 111,430 bytes with SHA-256 7b7f04ee9f393df2ec520110799ecd662033251b9dfcfaf1dad1d5727c717cee, relay_agent-0.2.0.tar.gz at 188,381 bytes with SHA-256 202c8ad1028eb1b2b45aa28801717246254ad837e7a5b1e37b26f1dc92d006c3, and SHA256SUMS.txt. A clean --no-index wheel install and MCP synthetic controls passed. No PyPI publication or install is claimed, and no real model or provider calls were in scope.

In August 2026 the source metadata named the package relay-agent 0.1.0; Relay now publishes on PyPI as flywheel-relay, and the PyPI name relay-agent belongs to another publisher. The README then described a permission-checked tool loop, hash-chained ledger, MCP surface, failover routes, and acceptance checks; no GitHub release tag was returned at that time.