Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

ci(release): add Windows x86_64 binary to tagged releases

Djalma Júnior56e7b7f4471e
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 50bdc692..6b6a2043 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -114,6 +114,60 @@ jobs:
${{ matrix.artifact }}.tar.gz
${{ matrix.artifact }}.tar.gz.sha256
+ windows:
+ name: windows x86_64 binary
+ needs: validate-version
+ runs-on: windows-latest
+ steps:
+ - uses: actions/checkout@v4
+
+ - uses: dtolnay/[email protected]
+
+ - uses: Swatinem/rust-cache@v2
+
+ - name: Build release binary
+ env:
+ TAILWIND_SKIP: "1"
+ run: cargo build --release -p ai-memory-cli
+
+ # Mirrors the Linux tarball, minus the Linux-only service assets
+ # (packaging/systemd|sysusers|tmpfiles|env). Ships the `.exe`, the full
+ # hooks bundle (the .ps1 + .sh scripts), the default config template, and
+ # the docs a Windows user needs (install.md + windows.md). Zipped (native
+ # Windows archive) with a sha256sum-format checksum so the release body's
+ # checksums block stays uniform across platforms.
+ - name: Create release zip
+ shell: pwsh
+ env:
+ RELEASE_ARTIFACT: ai-memory-windows-x86_64
+ run: |
+ $artifact = $env:RELEASE_ARTIFACT
+ $stage = "dist/$artifact"
+ New-Item -ItemType Directory -Force -Path $stage | Out-Null
+ Copy-Item target/release/ai-memory.exe "$stage/ai-memory.exe"
+ Copy-Item -Recurse hooks "$stage/hooks"
+ New-Item -ItemType Directory -Force -Path "$stage/crates/ai-memory-cli/templates" | Out-Null
+ Copy-Item crates/ai-memory-cli/templates/config.default.toml `
+ "$stage/crates/ai-memory-cli/templates/config.default.toml"
+ New-Item -ItemType Directory -Force -Path "$stage/docs" | Out-Null
+ Copy-Item README.md, LICENSE $stage
+ Copy-Item docs/install.md "$stage/docs/install.md"
+ Copy-Item docs/windows.md "$stage/docs/windows.md"
+ $zip = "$artifact.zip"
+ # Pipe the staged items in (rather than a "$stage/*" glob) so the
+ # archive is rooted at the files themselves — ai-memory.exe, hooks/,
+ # etc. land at the zip root, mirroring the Linux tarball layout.
+ Get-ChildItem $stage | Compress-Archive -DestinationPath $zip
+ $hash = (Get-FileHash $zip -Algorithm SHA256).Hash.ToLower()
+ "$hash $zip" | Out-File -Encoding ascii "$zip.sha256"
+
+ - uses: actions/upload-artifact@v4
+ with:
+ name: ai-memory-windows-x86_64
+ path: |
+ ai-memory-windows-x86_64.zip
+ ai-memory-windows-x86_64.zip.sha256
+
# Gate the publish on the Docker Hub secrets actually being present, so a
# fresh clone (or a fork) doesn't get a red failing run on every tag. The
# docker job activates automatically once DOCKERHUB_USERNAME + _TOKEN are
@@ -325,7 +379,7 @@ jobs:
github-release:
name: github release
- needs: [binary, validate-version]
+ needs: [binary, windows, validate-version]
runs-on: ubuntu-latest
steps:
- uses: actions/download-artifact@v4
@@ -349,6 +403,9 @@ jobs:
echo "# Docker" >> body.md
echo "docker pull akitaonrails/ai-memory:${{ needs.validate-version.outputs.version }}" >> body.md
echo "" >> body.md
+ echo "# Windows x86_64 (no toolchain): download ai-memory-windows-x86_64.zip below," >> body.md
+ echo "# extract it, and follow the bundled docs/windows.md." >> body.md
+ echo "" >> body.md
echo "# From source" >> body.md
echo "cargo install --git https://github.com/akitaonrails/ai-memory --tag ${GITHUB_REF_NAME}" >> body.md
echo '```' >> body.md
diff --git a/docs/windows.md b/docs/windows.md
index 84368f87..276f7698 100644
--- a/docs/windows.md
+++ b/docs/windows.md
@@ -114,7 +114,45 @@ the CLI to render hook commands for the native Windows agent:
Use the matching `--client` / `--agent` values for other clients, for
example `codex`, `cursor`, or `gemini-cli`.
-## Scenario C: Native Windows Source Build
+## Scenario C: Prebuilt Release Binary (No Toolchain)
+
+Use this when the agent CLI runs as a native Windows process and you want
+the fast native hook path **without** installing a Rust toolchain or
+Docker. Each tagged release publishes
+`ai-memory-windows-x86_64.zip` (see the repo's Releases page).
+
+```powershell
+# Download + extract into your user data dir (any stable path works; the
+# native hook command is rendered from wherever ai-memory.exe lives).
+$Dest = "$env:LOCALAPPDATA\ai-memory"
+New-Item -ItemType Directory -Force $Dest | Out-Null
+Invoke-WebRequest `
+ -Uri "https://github.com/akitaonrails/ai-memory/releases/latest/download/ai-memory-windows-x86_64.zip" `
+ -OutFile "$env:TEMP\ai-memory.zip"
+Expand-Archive "$env:TEMP\ai-memory.zip" -DestinationPath $Dest -Force
+Get-ChildItem "$Dest\ai-memory.exe" | Unblock-File
+
+# Put it on PATH for future terminals (optional but convenient).
+$UserPath = [Environment]::GetEnvironmentVariable("Path", "User")
+if (($UserPath -split ';') -notcontains $Dest) {
+ [Environment]::SetEnvironmentVariable("Path", "$UserPath;$Dest", "User")
+ $env:Path = "$env:Path;$Dest"
+}
+
+# Wire MCP + lifecycle hooks against your server.
+& "$Dest\ai-memory.exe" install-mcp --client claude-code --apply
+& "$Dest\ai-memory.exe" install-hooks --agent claude-code --apply `
+ --server-url "https://memory.example.com" --auth-token "<token>"
+```
+
+The zip mirrors the Linux release tarball, minus the Linux-only service
+assets: it contains `ai-memory.exe`, the full `hooks/` bundle (`.ps1` +
+`.sh`), `crates/ai-memory-cli/templates/config.default.toml`, `README.md`,
+`LICENSE`, and `docs/{install,windows}.md`. Because `install-hooks` reads
+the `ai-memory.exe` path from the running binary, keep the extracted `.exe`
+at a stable location (re-run `install-hooks` if you move it).
+
+## Scenario D: Native Windows Source Build
Use this when developing ai-memory itself on Windows or when you do not
want the Docker wrapper for CLI commands.