Skip to content

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

Rust

chore: post-audit follow-ups (Windows auth remedy, eval-knob note, TMPDIR fix)

AkitaOnRails3c4ab000350c
diff --git a/docs/benchmarks/README.md b/docs/benchmarks/README.md
index d5787366..2f7753c3 100644
--- a/docs/benchmarks/README.md
+++ b/docs/benchmarks/README.md
@@ -182,7 +182,9 @@ run to the last digit, and the 100-question FTS wall clock fell from
(`env:AI_MEMORY_EVAL_SKIP_WIKI_CHECKPOINTS=1`), so a run that used it
says so. Accuracy, latency and context-token numbers stay comparable with
earlier releases; only ingest wall clock differs, because runs before
-October 2026 paid for the commits.
+October 2026 paid for the commits. The variable is an eval-only escape, not
+a supported product configuration: no product path sets it, and its only
+reader is the server's startup check.
```bash
ai-memory-eval retrieval \
diff --git a/docs/windows.md b/docs/windows.md
index db3b7800..27b0aef2 100644
--- a/docs/windows.md
+++ b/docs/windows.md
@@ -188,6 +188,24 @@ container, which has no host CLIs.
- The native client inherits `AI_MEMORY_SERVER_URL`. Leave it unset and it
talks to `http://127.0.0.1:49374`, the port the container publishes on the
host; a remote-server URL wins, as with every other wrapper command.
+- When the container server has auth enabled (a fresh install mints a root
+ bearer into the volume), the native client needs that token or the server
+ rejects these commands with `401`. The Linux/macOS wrapper copies the
+ token out of the named volume for its native host commands; the
+ PowerShell wrapper does not do that yet
+ ([#1603](https://github.com/akitaonrails/ai-memory/issues/1603)). Until it
+ does, copy the token out once yourself and point the client at the file:
+
+ ```powershell
+ New-Item -ItemType Directory -Force "$env:LOCALAPPDATA\ai-memory" | Out-Null
+ $token = docker run --rm -v ai-memory-data:/data:ro --entrypoint /bin/sh akitaonrails/ai-memory:latest -c "cat /data/auth-tokens/default"
+ Set-Content -NoNewline "$env:LOCALAPPDATA\ai-memory\server-token" $token.Trim()
+ $env:AI_MEMORY_AUTH__BEARER_TOKEN_FILE = "$env:LOCALAPPDATA\ai-memory\server-token"
+ ```
+
+ Setting `AI_MEMORY_AUTH__BEARER_TOKEN_FILE` in your user environment covers
+ every terminal. A plain `$env:AI_MEMORY_AUTH_TOKEN = "<token>"` also works
+ for a single session. Refresh the copy whenever the volume's token rotates.
- A managed launch does not rewire hooks or MCP: what `install-hooks` and
`install-mcp` rendered through the container stays in place (the wrapper
sets `AI_MEMORY_RUN_AUTOWIRE=false` for the intercepted commands unless you
diff --git a/scripts/check-native-packaging.sh b/scripts/check-native-packaging.sh
index 18c321cf..f86f1581 100755
--- a/scripts/check-native-packaging.sh
+++ b/scripts/check-native-packaging.sh
@@ -124,7 +124,10 @@ main() {
log "Skipping RPM spec check (rpmspec unavailable)"
fi
- TMP_ROOT="$(mktemp -d /tmp/ai-memory-native-root.XXXXXX)"
+ # Honor TMPDIR: mktemp ignores it once the template carries an explicit
+ # directory, and a host whose /tmp is small or quota-limited would reject
+ # the writes below.
+ TMP_ROOT="$(mktemp -d "${TMPDIR:-/tmp}/ai-memory-native-root.XXXXXX")"
cleanup() {
if [ -n "${TMP_ROOT}" ]; then
rm -rf "${TMP_ROOT}"