Changelog
Every release of recoil, newest first. Versions follow Semantic Versioning and match the git tags.
The canonical file is CHANGELOG.md in the repository; this page is rendered from it.
Unreleased
0.3.1 — 2026-09-21
Fixed
- The test suite passes on Windows. The agent-session discovery tests and the project-DB fallback test assumed
HOME, forward-slash paths and an XDG config directory; they now isolateUSERPROFILEand%AppData%too and JSON-encode fixture paths. CI runs the suite onwindows-latest, and the release workflow no longer lets a Windows test failure through as a warning.
0.3.0 — 2026-09-21
Recoil is one local store per machine again. The sharing experiment, its relay server and the Docker image are gone; nothing in the binary talks to a network except the optional embedding providers.
Removed
- Memory sharing. The
swarm,channelandrelaycommands, the relay server and its Docker image, the--relay,--relay-agent,--standalone,--collaborativeand--manual-shareflags onsetup, the--publish/--no-publishflags onadd,remember,decide,supersede,handoffand the MCP write tools, the sevenchannel.*settings, the Peer Memory lane, and thechannel_*,peer_memory_received,memory_shared,pending_shareandpublishfields in text and JSON output. Recoil is one local store per machine; nothing in it talks to a network except the optional embedding providers.
Changed
- Store schema version 2. The first command that opens an older store drops the channel tables it carries; memories, sources and embeddings are untouched.
recoil setupprints the project, chunk and hook counts and nothing about posture or sharing.- The agent contract (
recoil instruct) describes a memory store, not a memory tree, and no longer promises automatic sharing.
0.2.0 — 2026-09-21
The repository now ships the way the other chain.sh tools do: CI on every push, lint and vulnerability gates, contributor docs, and a grouped --help. The MCP SDK and Go toolchain move past four SDK advisories and ten standard-library ones.
Added
- A CI workflow: build, golangci-lint, the test suite on Linux and macOS, and govulncheck, on every pull request and push to
main.make lint,make vulncheck,make build-checkandmake cirun the same checks locally, and.githooks/pre-commitruns them before a commit (git config core.hooksPath .githooks). AGENTS.md(code layout and conventions, withCLAUDE.mdpointing at it),CONTRIBUTING.md, andRELEASING.md.recoil --helpgroups the commands the way the manual does: session, writing memory, reading memory, sources, sharing, for agents, operator.recoil versionreports the module version and VCS stamp for ago install github.com/1broseidon/recoil@vX.Y.Zbuild instead ofdev (unknown, unknown).
Changed
modelcontextprotocol/go-sdk1.2.0 → 1.8.0, which closes GO-2026-4569, GO-2026-4770, GO-2026-4773 and GO-2026-5771.- Go toolchain floor raised from 1.26.2 to 1.26.7: govulncheck flagged ten standard-library findings against 1.26.2 (
net/http,crypto/tls,crypto/x509,net/url,net/textproto,encoding/asn1,net), all fixed by 1.26.6. CI builds withgo-version-file: go.mod; local builds with Go 1.21+ fetch the toolchain automatically. recoil instructionsis a hidden alias ofrecoil instruct; the two commands already printed the same text.ProjectScopeno longer resolves a subdirectory to itself when recoil runs inside a git hook: thegitit spawns now ignores theGIT_DIR,GIT_WORK_TREEandGIT_INDEX_FILEa hook exports.- The
cmdtest suite redirectsHOMEand the XDG and AppData directories to a throwaway directory and unsetsRECOIL_DBandRECOIL_PROJECT, so a test run can no longer open or mine into the developer's real store.
0.1.1 — 2026-09-21
The first release with published binaries. v0.1.0 was tagged, but its release build failed on the macOS runner and never published anything.
Added
install.sh, served athttps://recoil.sh/install: detects the OS and architecture, verifies the archive againstchecksums.txt, and installsrecoilinto/usr/local/binor~/.local/bin.install.ps1anduninstall.ps1are served athttps://recoil.sh/install.ps1andhttps://recoil.sh/uninstall.ps1.- The manual at recoil.sh, printed from
MANUAL.mdby inkcap on GitHub Pages.
Fixed
- Relay: a single-use invite that has already been claimed now answers
403 invite has already been usedinstead of404 invite not found. The loser of two concurrent joins got one or the other depending on timing, which is also what made the release test suite fail on macOS.
0.1.0 — 2026-09-19
First tagged release. Until now recoil was install-from-source only: go install with CGO_ENABLED=1 and CGO_CFLAGS=-DSQLITE_ENABLE_FTS5, which required a Go toolchain and a C compiler on every machine that wanted it. This release publishes prebuilt binaries so that stops being a prerequisite.
Added
- Prebuilt binaries attached to each tagged release, with a
checksums.txtcovering every archive:linux/x86_64,linux/arm64,darwin/arm64,darwin/x86_64, andwindows/x86_64. install.ps1anduninstall.ps1for Windows, installing to%LOCALAPPDATA%\recoiland adding it to the userPATH.uninstall.ps1keeps your memory database by default;-Purgeremoves it too.- A release workflow that builds each target on a native runner, so the CGO build linking SQLite with FTS5 is compiled for the platform it ships to rather than cross-compiled.
Notes
- FTS5 remains mandatory. It is compiled into every published binary, so the requirement no longer shows up as a build flag you have to remember — but a binary built without it still will not work, and there is no degraded fallback.
- Building from source is unchanged and still supported:
make buildandmake installset the CGO flags for you.