v0.2.2

One shared fridge door for every coding agent in your checkout.

Install

macOS and Linux:

curl -fsSL https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.sh | sh

Windows PowerShell:

irm https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.ps1 | iex

Or download the binary for your platform below and put it on your PATH. Every
asset has a matching .sha256, and checksums.txt covers the set.

Prefer a package manager?

go install github.com/RagnarPitla/agent-fridge/cmd/fridge@latest   # Go 1.21+
npm install -g github:RagnarPitla/agent-fridge                     # Node 20.11+

Verify what you downloaded

fridge version
fridge conform

fridge conform runs the protocol's conformance vectors against the binary you
are holding, offline, from vectors embedded in the binary itself. If it does not
say CONFORMANT, do not trust the binary.

What changed

v0.2.2 is the ownership and concurrency hardening release:

• Exact overlap decisions for ranges, negated classes, bounded braces, and
  case-insensitive Unicode simple folds in both Node and Go.
• Explicit mutation identity, strict corrupt-record reads, and stale
  FRIDGE_ACTOR recovery for identity-free administration.
• Generation-fenced mutex release, recovery, and renewable heartbeats for
  bounded batch operations.
• Serialized lease and session mutations, including the fridge run
  heartbeat shutdown race.
• Confined configured output paths, convergent rendering, and migration
  preflight that refuses changed, oversized, or secret-like sources.
• Native Windows batch execution and PATH precedence checks.

See CHANGELOG.md.

Evidence in this release

Nothing ships until it has proved itself. This release was published only after
the release workflow ran, in order: lint, generated-doc drift check, go vet,
the Go test suite, the Node suite including real multi-process concurrency
tests, fridge conform in both implementations, the command-by-command parity
diff between the Go and Node implementations, and the before/after demo that
shows the old shared-Markdown pattern losing notes and this one losing none.

The exact binary published here is the one that was run through conform and
had its checksum verified in CI.

v0.2.1

One shared fridge door for every coding agent in your checkout.

Install

macOS and Linux:

curl -fsSL https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.sh | sh

Windows PowerShell:

irm https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.ps1 | iex

Or download the binary for your platform below and put it on your PATH. Every
asset has a matching .sha256, and checksums.txt covers the set.

Prefer a package manager?

go install github.com/RagnarPitla/agent-fridge/cmd/fridge@latest   # Go 1.21+
npm install -g github:RagnarPitla/agent-fridge                     # Node 20.11+

Verify what you downloaded

fridge version
fridge conform

fridge conform runs the protocol's conformance vectors against the binary you
are holding, offline, from vectors embedded in the binary itself. If it does not
say CONFORMANT, do not trust the binary.

What changed

See CHANGELOG.md.

Evidence in this release

Nothing ships until it has proved itself. This release was published only after
the release workflow ran, in order: lint, generated-doc drift check, go vet,
the Go test suite, the Node suite including real multi-process concurrency
tests, fridge conform in both implementations, the command-by-command parity
diff between the Go and Node implementations, and the before/after demo that
shows the old shared-Markdown pattern losing notes and this one losing none.

The exact binary published here is the one that was run through conform and
had its checksum verified in CI.

v0.2.0

Superseded by v0.2.1. Use that instead.

The binaries below contain a liveness bug in the registry mutex. A release
that hit a transient filesystem failure abandoned the lock instead of
retrying, leaving a lock that nobody held and nobody could take until the
stale window expired. This is routine on Windows, where any process reading
owner.json blocks rename, unlink and rmdir. In CI one blocked release
stranded fifteen of sixteen workers. Fixed in v0.2.1 by protocol invariant
I7c.

Correctness of claims was never affected: no two agents could hold the same
path. The failure mode was that work stopped, not that work was lost.

---

One shared fridge door for every coding agent in your checkout.

Install

macOS and Linux:

curl -fsSL https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.sh | sh

Windows PowerShell:

irm https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.ps1 | iex

Or download the binary for your platform below and put it on your PATH. Every
asset has a matching .sha256, and checksums.txt covers the set.

Prefer a package manager?

go install github.com/RagnarPitla/agent-fridge/cmd/fridge@latest   # Go 1.21+
npm install -g github:RagnarPitla/agent-fridge                     # Node 20.11+

Verify what you downloaded

fridge version
fridge conform

fridge conform runs the protocol's conformance vectors against the binary you
are holding, offline, from vectors embedded in the binary itself. If it does not
say CONFORMANT, do not trust the binary.

What changed

See CHANGELOG.md.

Evidence in this release

Nothing ships until it has proved itself. This release was published only after
the release workflow ran, in order: lint, generated-doc drift check, go vet,
the Go test suite, the Node suite including real multi-process concurrency
tests, fridge conform in both implementations, the command-by-command parity
diff between the Go and Node implementations, and the before/after demo that
shows the old shared-Markdown pattern losing notes and this one losing none.

The exact binary published here is the one that was run through conform and
had its checksum verified in CI.

v0.1.0 (superseded preview, no downloadable assets)

Superseded, and there is nothing to download here.

This release has no installable assets. It was tagged before the project
had a native binary or a release pipeline, and before it was renamed from
FridgeBoard to Agent Fridge. It is kept only so the tag and its notes stay
readable.

Install the current release instead:
latest release

# macOS and Linux
curl -fsSL https://github.com/RagnarPitla/agent-fridge/releases/latest/download/install.sh | sh

The notes below are the original v0.1.0 text, left unedited. They describe a
Node-only CLI and an earlier product name, and are historical rather than
current. Agent Fridge is not published to the npm registry.

---

Multiple AI agents and humans work in one Git checkout without overwriting each other. Local-first, zero runtime dependencies, model-neutral.

The problem this exists for

Two agent terminals coordinated through one shared Markdown file, each doing read-modify-write. One write destroyed about 128 lines of the other agents work. No error. Exit code 0. The losing process had no way to find out.

npm run demo reproduces the class of failure on any machine: 191 lines lost the old way, 0 lost through fridge.

What is in this release

• The protocol (spec/protocol-v0.1.md): on-disk layout, record schemas, atomic writes, the mkdir registry mutex, claim and scope semantics, leases and staleness, crash recovery, and 12 testable invariants. Enough to reimplement in another language.
• The exit-code contract (spec/exit-codes.md): 20 codes, generated from source and drift-checked in CI. Exit codes are the public API.
• Conformance vectors (test/vectors/*.json): language-neutral, so a second implementation can prove conformance without reading any JavaScript.
• The CLI: 28 commands, zero runtime dependencies, Node >= 20.11.
• Instruction adapters: one canonical block spliced into AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, Codex, and a generic snippet.
• Migration: fridge migrate imports To-do.done.md and shared-development-updates.md into immutable notes, with author attribution.
• 88 tests: unit, integration, and real multi-process concurrency with a start barrier, an unmocked clock, and an unmocked filesystem.

Verified on

Ubuntu, macOS, and Windows, on Node 20 and 22, plus a PowerShell job that asserts the exit-code contract in PowerShell quoting. All 8 CI jobs green.

The design in one line

One writer per record. A claim, a note, and a session are each owned by exactly one actor, so the multi-writer single-file failure mode is structurally absent rather than mitigated. Human-readable views are generated from that state and never edited by hand.

Honest positioning

The shared-board idea is old: blackboard architectures, advisory locking, leases, and tuple spaces all predate this by decades. What is on offer is an open, model-neutral, dependency-free, cross-platform implementation with a written protocol and proof that it holds under real concurrency.

FridgeBoard is cooperative and advisory. It is not a security boundary, and SECURITY.md says so plainly.