diff --git a/.cursor-plugin/plugin.json b/.cursor-plugin/plugin.json
index 4cabbe100c..ff685266d2 100644
--- a/.cursor-plugin/plugin.json
+++ b/.cursor-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "agentmemory",
- "version": "0.9.31",
+ "version": "0.9.33",
"description": "Persistent memory for Cursor: auto-captures sessions, prompts, and tool use via hooks, recalls with hybrid BM25 + vector + graph search, and exposes 54 memory tools over MCP. Keyless by default, runs entirely on your machine.",
"author": {
"name": "Rohit Ghumare",
diff --git a/.env.example b/.env.example
index c8a9c3d57c..532080f879 100644
--- a/.env.example
+++ b/.env.example
@@ -13,14 +13,19 @@
# place automatically. Run `npx -y @agentmemory/agentmemory@latest doctor`
# to verify that the daemon reads the env you expect.
#
-# Defaults shown in comments. Listed in priority order — the first key
-# present wins on the LLM detection path (see src/config.ts::detectProvider).
+# Defaults shown in comments. No provider is ever picked from a key alone:
+# agentmemory sends session content to an outside AI provider only after you
+# name one with AGENTMEMORY_LLM_PROVIDER or EMBEDDING_PROVIDER, or opt into the
+# Claude subscription fallback with AGENTMEMORY_ALLOW_AGENT_SDK=true.
# -----------------------------------------------------------------------------
-# 1. LLM provider — pick ONE
+# 1. LLM provider: off unless you choose one
# -----------------------------------------------------------------------------
#
-# Without a provider key, agentmemory runs in noop mode: observations are
+# Without AGENTMEMORY_LLM_PROVIDER or AGENTMEMORY_ALLOW_AGENT_SDK=true, agentmemory
+# runs in noop mode and sends no session content to an LLM, even when a provider
+# key is in the environment.
+# In noop mode: observations are
# indexed via zero-LLM synthetic compression and BM25 recall still works,
# but LLM-backed summarisation / reflection / consolidation are disabled.
# A provider key alone does not enable LLM-written observation compression;
@@ -39,13 +44,12 @@
# AGENTMEMORY_CAPTURE_SPOOL_DIR= # Spool folder (default /capture-spool)
# AGENTMEMORY_CAPTURE_SPOOL_MAX_BYTES=5242880 # Spool size limit
# AGENTMEMORY_CAPTURE_SPOOL_MAX_AGE_HOURS=168 # Spooled records older than this are dropped
-# The detection order is OPENAI_API_KEY → MINIMAX_API_KEY → ANTHROPIC_API_KEY
-# → GEMINI_API_KEY → OPENROUTER_API_KEY → noop.
+# To turn on LLM summaries, set AGENTMEMORY_LLM_PROVIDER and that provider's key.
+# AGENTMEMORY_LLM_PROVIDER=anthropic # anthropic | openai | gemini | openrouter | minimax
-# OPENAI_API_KEY=sk-... # Activates both the OpenAI-compatible LLM provider (DeepSeek, SiliconFlow, vLLM, LM Studio, Ollama via `/v1`) and OpenAI embeddings. Set OPENAI_API_KEY_FOR_LLM=false to scope it to embeddings only.
+# OPENAI_API_KEY=sk-... # Used by AGENTMEMORY_LLM_PROVIDER=openai (OpenAI-compatible: DeepSeek, SiliconFlow, vLLM, LM Studio, Ollama via `/v1`) and by EMBEDDING_PROVIDER=openai
# OPENAI_BASE_URL=https://api.openai.com # Override for OpenAI-compatible providers
# OPENAI_MODEL=gpt-5.6-luna # Default OpenAI-compatible chat model
-# OPENAI_API_KEY_FOR_LLM=false # Skip OpenAI auto-detection for LLM; key stays active for embeddings
# ANTHROPIC_API_KEY=sk-ant-...
# ANTHROPIC_MODEL=claude-sonnet-5 # Default Anthropic model
@@ -75,18 +79,17 @@
# Stop-hook recursion when invoked from inside Claude Code.
# AGENTMEMORY_ALLOW_AGENT_SDK=true
-# FALLBACK_PROVIDERS=anthropic,gemini # Comma-separated chain tried after the primary provider returns an error (e.g. rate limit)
+# FALLBACK_PROVIDERS=anthropic,gemini # Comma-separated chain tried after the chosen AGENTMEMORY_LLM_PROVIDER returns an error (e.g. rate limit); ignored when zero-LLM is active
# -----------------------------------------------------------------------------
-# 2. Embedding provider — auto-detected, override via EMBEDDING_PROVIDER
+# 2. Embedding provider: off unless you set EMBEDDING_PROVIDER
# -----------------------------------------------------------------------------
#
# Without an embedding provider, vector embeddings are disabled. `mem::search`
# uses BM25; `mem::smart-search` can also fuse structural graph matches when
-# graph data exists. Remote
-# provider detection order: EMBEDDING_PROVIDER override → GEMINI_API_KEY →
-# OPENAI_API_KEY → VOYAGE_API_KEY → COHERE_API_KEY → OPENROUTER_API_KEY →
-# BM25-only. Local embeddings are an explicit opt-in, not the keyless default.
+# graph data exists. Cloud embeddings send memory text to that provider and run
+# only when EMBEDDING_PROVIDER names it; a key alone never turns them on.
+# Local embeddings are an explicit opt-in too, not the keyless default.
# `EMBEDDING_PROVIDER=local` uses Xenova/all-MiniLM-L6-v2 (384-dim) on-device;
# the first embedding request downloads the model and needs network access.
@@ -124,10 +127,13 @@
# VECTOR_WEIGHT=0.6 # Hybrid search weight for vector leg
# AGENTMEMORY_GRAPH_WEIGHT=0.2 # Graph traversal bonus on smart-search ranking
# AGENTMEMORY_GRAPH_COMPACT_ON_BOOT=false # Report boot compaction as off (otherwise deferred; manual maintenance only)
+# AGENTMEMORY_GRAPH_IMPORT_MAX_NODES=5000 # Node limit for POST /graph/import-graphify; nodes over it are dropped and reported
+# AGENTMEMORY_GRAPH_IMPORT_MAX_EDGES=20000 # Edge limit for POST /graph/import-graphify; edges over it are dropped and reported
# TOKEN_BUDGET=2000 # Max tokens injected via mem::context per session
-# MAX_OBS_PER_SESSION=500 # Per-session observation cap before consolidation kicks in
+# MAX_OBS_PER_SESSION=500 # Hard per-session cap: later observations of that session are refused; only capture-worker refusals are parked as dead letters (0 = no cap)
# SUMMARIZE_CHUNK_SIZE=400 # When mem::summarize sees a session larger than this, it chunks observations and map-reduces (chunk-summarize → reduce-merge) to stay within the LLM's context window. Default 400 ≈ 50k tokens per chunk at ~110 tok/obs. Native sessions are capped by MAX_OBS_PER_SESSION; chunking primarily matters for bulk-imported jsonl sessions, which bypass that cap.
# SUMMARIZE_CHUNK_CONCURRENCY=6 # Parallel chunk LLM calls during chunked summarize. Default 6 fits ~100-chunk sessions under iii's 180s function-invocation timeout at typical ~8s/call. High-throughput providers (Novita, DeepInfra, DeepSeek) commonly allow 100+ concurrent — bump this for very large imported sessions.
+# AGENTMEMORY_SUMMARY_TIMEOUT_MS=120000 # Total time budget in whole milliseconds for one mem::summarize run, shared by every chunk call. Default 120000 (2 min). Raise it for slow or local LLMs (Ollama, LM Studio, vLLM) on large chunked sessions that fail with summary_timeout. Session-end and recovery summaries wait this budget plus 60 s; POST /agentmemory/summarize is still cut off by the 180 s HTTP worker timeout, but the summary keeps running and is saved.
# -----------------------------------------------------------------------------
# 5. Behaviour flags
@@ -135,6 +141,7 @@
# AGENTMEMORY_AUTO_COMPRESS=true # Run LLM-written compression on every observation batch. Requires BOTH this flag and a configured provider; a provider alone leaves synthetic compression active.
# AGENTMEMORY_INJECT_CONTEXT=true # Opt in to Claude-style hook context injection. Pi/OMP use 1 in their launch environment for file enrichment; native prompt recall is independent.
+# AGENTMEMORY_ENRICH_TIMEOUT_MS=2000 # PreToolUse hook wait (default 2000 ms). Set this in the hook process environment; setting it only in this server env file does not change the hook timeout.
# CONSOLIDATION_ENABLED=false # Disable the consolidation pipeline. Otherwise enabled when an LLM provider is configured, unless AGENTMEMORY_PROVIDER=noop.
# CONSOLIDATION_DECAY_DAYS=30 # Age (days) after which non-reinforced memories decay during consolidation
# GRAPH_EXTRACTION_ENABLED=true # Extract concept-graph edges on remember; powers the graph-traversal recall path
@@ -166,6 +173,7 @@
# AGENTMEMORY_DEBUG=1 # Trace MCP shim probe + standalone fallback decisions to stderr
# AGENTMEMORY_FORCE_PROXY=1 # Skip the MCP shim livez probe and trust AGENTMEMORY_URL (for sandboxed MCP clients that can't reach localhost)
# AGENTMEMORY_PROBE_TIMEOUT_MS=2000 # MCP shim livez probe timeout
+# AGENTMEMORY_CALL_TIMEOUT_MS=190000 # MCP shim and plugin bridge timeout for each proxied REST call, read from the MCP host environment or this file. Default 190000, a little above the 180 s worker invocation limit, so long calls such as memory_consolidate and memory_reflect end on the server first
# AGENTMEMORY_READY_TIMEOUT_MS=300000 # CLI worker readiness deadline, including state loading (5 minutes)
# AGENTMEMORY_ENGINE_READY_TIMEOUT_MS=120000 # CLI engine readiness deadline (2 minutes)
# Startup deadlines accept whole milliseconds from 1 to 3600000. Shell
@@ -213,10 +221,10 @@
# 8. iii engine pin
# -----------------------------------------------------------------------------
#
-# agentmemory pins iii-engine and its iii-sdk dependencies to v0.25.0.
-# The CLI downloads the engine into ~/.agentmemory/bin on macOS/Linux.
-# Native Windows requires installing the matching iii.exe manually.
-# AGENTMEMORY_III_VERSION=0.25.0 # Override only when deliberately matching a different engine
+# agentmemory pins iii-engine and its iii-sdk dependencies to v0.25.1.
+# The CLI downloads the engine into ~/.agentmemory/bin, including the Windows ZIP.
+# AGENTMEMORY_III_VERSION=0.25.1 # Override only when deliberately matching a different engine
+# AGENTMEMORY_LOCAL_DISPATCH=true # iii 0.25 runs calls to the worker's own functions in-process; set false for full engine traces
# Engine usage telemetry (iii). Off unless you set it; true opts in.
# III_TELEMETRY_ENABLED=false
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 97f74c44b2..2806b98182 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -57,7 +57,7 @@ jobs:
os: [ubuntu-latest, macos-latest]
node-version: [20, 22, 24, 26]
steps:
- - uses: actions/checkout@v6
+ - uses: actions/checkout@v7
with:
persist-credentials: false
- uses: actions/setup-node@v6
diff --git a/.github/workflows/docker-image.yml b/.github/workflows/docker-image.yml
new file mode 100644
index 0000000000..840601edfc
--- /dev/null
+++ b/.github/workflows/docker-image.yml
@@ -0,0 +1,217 @@
+name: Docker image
+
+on:
+ release:
+ types: [published]
+ workflow_dispatch:
+ inputs:
+ version:
+ description: "Release version to build, without the leading v (for example 0.9.32)"
+ required: true
+ type: string
+
+permissions:
+ contents: read
+
+env:
+ IMAGE: docker.io/ghumarerohit/agentmemory
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ timeout-minutes: 90
+ permissions:
+ contents: read
+ outputs:
+ version: ${{ steps.v.outputs.version }}
+ steps:
+ - name: Resolve version
+ id: v
+ env:
+ EVENT: ${{ github.event_name }}
+ RELEASE_TAG: ${{ github.event.release.tag_name }}
+ INPUT_VERSION: ${{ inputs.version }}
+ run: |
+ if [ "$EVENT" = "release" ]; then
+ tag="$RELEASE_TAG"
+ version="${RELEASE_TAG#v}"
+ else
+ version="${INPUT_VERSION#v}"
+ tag="v$version"
+ fi
+ if ! printf '%s' "$version" | grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$'; then
+ echo "Not a release version: $version" >&2
+ exit 1
+ fi
+ if [ "${#version}" -gt 128 ]; then
+ echo "Version is longer than the 128-character Docker tag limit: $version" >&2
+ exit 1
+ fi
+ {
+ echo "version=$version"
+ echo "tag=$tag"
+ } >> "$GITHUB_OUTPUT"
+
+ - uses: actions/checkout@v6
+ with:
+ ref: refs/tags/${{ steps.v.outputs.tag }}
+ persist-credentials: false
+
+ - uses: docker/setup-qemu-action@v3
+
+ - uses: docker/setup-buildx-action@v3
+
+ - name: Image metadata
+ id: meta
+ uses: docker/metadata-action@v5
+ with:
+ images: ${{ env.IMAGE }}
+ tags: |
+ type=raw,value=${{ steps.v.outputs.version }}
+ labels: |
+ org.opencontainers.image.version=${{ steps.v.outputs.version }}
+ org.opencontainers.image.licenses=Apache-2.0
+
+ - name: Build for smoke test
+ uses: docker/build-push-action@v6
+ with:
+ context: .
+ file: deploy/Dockerfile
+ platforms: linux/amd64
+ load: true
+ tags: agentmemory-smoke:${{ steps.v.outputs.version }}
+ cache-from: type=gha,scope=docker-image
+ cache-to: type=gha,scope=docker-image,mode=max
+
+ - name: Smoke test
+ env:
+ SMOKE_IMAGE: agentmemory-smoke:${{ steps.v.outputs.version }}
+ run: |
+ docker run -d --name am-smoke -p 127.0.0.1:3111:3111 "$SMOKE_IMAGE"
+ for i in $(seq 1 90); do
+ if curl -fsS http://127.0.0.1:3111/agentmemory/livez >/dev/null; then
+ echo "livez ok after $((i * 2)) s"
+ docker rm -f am-smoke >/dev/null
+ exit 0
+ fi
+ if [ "$(docker inspect -f '{{.State.Running}}' am-smoke)" != "true" ]; then
+ echo "container exited" >&2
+ break
+ fi
+ sleep 2
+ done
+ docker logs am-smoke >&2 || true
+ docker rm -f am-smoke >/dev/null || true
+ exit 1
+
+ - name: Build multi-platform archive
+ uses: docker/build-push-action@v6
+ with:
+ context: .
+ file: deploy/Dockerfile
+ platforms: linux/amd64,linux/arm64
+ labels: ${{ steps.meta.outputs.labels }}
+ provenance: false
+ sbom: false
+ outputs: type=oci,dest=${{ runner.temp }}/image.tar
+ cache-from: type=gha,scope=docker-image
+ cache-to: type=gha,scope=docker-image,mode=max
+
+ - uses: actions/upload-artifact@v4
+ with:
+ name: agentmemory-image-${{ steps.v.outputs.version }}
+ path: ${{ runner.temp }}/image.tar
+ retention-days: 14
+ if-no-files-found: error
+
+ publish:
+ needs: build
+ runs-on: ubuntu-latest
+ timeout-minutes: 30
+ environment: docker-hub
+ permissions:
+ contents: read
+ id-token: write
+ attestations: write
+ env:
+ VERSION: ${{ needs.build.outputs.version }}
+ steps:
+ - uses: actions/download-artifact@v4
+ with:
+ name: agentmemory-image-${{ needs.build.outputs.version }}
+ path: ${{ runner.temp }}/image
+
+ - name: Log in to Docker Hub
+ env:
+ DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}
+ DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
+ run: |
+ printf '%s' "$DOCKERHUB_TOKEN" | skopeo login --username "$DOCKERHUB_USERNAME" --password-stdin docker.io
+ printf '%s' "$DOCKERHUB_TOKEN" | docker login --username "$DOCKERHUB_USERNAME" --password-stdin docker.io
+
+ - name: Push version tag
+ id: push
+ run: |
+ skopeo copy --all --preserve-digests \
+ --digestfile "$RUNNER_TEMP/digest" \
+ "oci-archive:$RUNNER_TEMP/image/image.tar" \
+ "docker://$IMAGE:$VERSION"
+ echo "digest=$(cat "$RUNNER_TEMP/digest")" >> "$GITHUB_OUTPUT"
+
+ - name: Verify platforms
+ run: |
+ platforms=$(docker buildx imagetools inspect --raw "$IMAGE:$VERSION" \
+ | jq -r '.manifests[].platform | "\(.os)/\(.architecture)"' | sort -u | tr '\n' ' ')
+ echo "platforms: $platforms"
+ for p in linux/amd64 linux/arm64; do
+ case " $platforms " in
+ *" $p "*) ;;
+ *) echo "missing $p in $IMAGE:$VERSION" >&2; exit 1 ;;
+ esac
+ done
+
+ - uses: actions/attest-build-provenance@v4
+ with:
+ subject-name: ${{ env.IMAGE }}
+ subject-digest: ${{ steps.push.outputs.digest }}
+ push-to-registry: true
+
+ latest:
+ needs: publish
+ runs-on: ubuntu-latest
+ timeout-minutes: 15
+ environment: docker-hub
+ permissions:
+ contents: read
+ concurrency:
+ group: docker-hub-latest
+ cancel-in-progress: false
+ steps:
+ - name: Log in to Docker Hub
+ env:
+ DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}
+ DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
+ run: printf '%s' "$DOCKERHUB_TOKEN" | skopeo login --username "$DOCKERHUB_USERNAME" --password-stdin docker.io
+
+ - name: Point latest at the newest stable release
+ env:
+ GH_TOKEN: ${{ github.token }}
+ REPO: ${{ github.repository }}
+ run: |
+ tags=$(gh api --paginate "repos/$REPO/releases" \
+ --jq '.[] | select(.draft | not) | select(.prerelease | not) | .tag_name')
+ newest=$(printf '%s\n' "$tags" \
+ | sed 's/^v//' \
+ | { grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' || true; } \
+ | sort -t. -k1,1n -k2,2n -k3,3n \
+ | tail -n 1)
+ if [ -z "$newest" ]; then
+ echo "No stable release found; leaving latest unchanged."
+ exit 0
+ fi
+ if ! skopeo inspect --raw "docker://$IMAGE:$newest" >/dev/null 2>&1; then
+ echo "Image for the newest stable release ($newest) is not pushed yet; leaving latest unchanged."
+ exit 0
+ fi
+ skopeo copy --all --preserve-digests "docker://$IMAGE:$newest" "docker://$IMAGE:latest"
+ echo "latest -> $newest"
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index af230453fc..fec9218700 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -25,7 +25,7 @@ jobs:
contents: read
id-token: write
steps:
- - uses: actions/checkout@v6
+ - uses: actions/checkout@v7
with:
persist-credentials: false
@@ -56,7 +56,7 @@ jobs:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- if: always()
- uses: actions/upload-artifact@v4
+ uses: actions/upload-artifact@v7
with:
name: npm-release-${{ github.run_id }}-${{ github.run_attempt }}
path: ${{ runner.temp }}/npm-release
diff --git a/.github/workflows/release-gate.yml b/.github/workflows/release-gate.yml
index 05ee45938c..c5b24a0d1e 100644
--- a/.github/workflows/release-gate.yml
+++ b/.github/workflows/release-gate.yml
@@ -34,7 +34,7 @@ jobs:
strategy:
fail-fast: false
matrix:
- os: [ubuntu-latest, macos-latest]
+ os: [ubuntu-latest, ubuntu-24.04-arm, macos-latest, macos-15-intel]
steps:
- uses: actions/checkout@v6
with:
@@ -49,9 +49,9 @@ jobs:
shell: bash
run: |
engine_pin=$(node --import tsx --input-type=module -e 'import { III_PINNED_VERSION } from "./src/version.ts"; console.log(III_PINNED_VERSION)')
- engine_bin="$HOME/.cache/agentmemory-release-gate/iii-${engine_pin}-linux-x64"
+ engine_bin="$HOME/.cache/agentmemory-release-gate/iii-${engine_pin}-linux-$(node -p process.arch)"
test -x "$engine_bin"
- AGENTMEMORY_TEST_III="$engine_bin" AGENTMEMORY_REQUIRE_LIVE_TESTS=1 npx vitest run test/compose-supervision-integration.test.ts test/codex-live-daemon.test.ts
+ AGENTMEMORY_TEST_III="$engine_bin" AGENTMEMORY_REQUIRE_LIVE_TESTS=1 npx vitest run test/compose-supervision-integration.test.ts test/codex-live-daemon.test.ts test/compose-c1-integration.test.ts
- run: npm run test:startup:packaged -- --skip-build --out "${{ runner.temp }}/startup-gate"
- name: Test packaged vector recovery
shell: bash
@@ -74,9 +74,9 @@ jobs:
archives=("$RUNNER_TEMP"/graph-index-pack/*.tgz)
npm run test:graph-index:packaged -- --tarball "${archives[0]}" --out "$RUNNER_TEMP/graph-index-gate"
- if: always()
- uses: actions/upload-artifact@v4
+ uses: actions/upload-artifact@v7
with:
- name: release-gate-${{ matrix.os }}
+ name: release-gate-${{ matrix.os }}-${{ github.run_attempt }}
path: |
${{ runner.temp }}/release-gate
${{ runner.temp }}/startup-gate
@@ -86,3 +86,44 @@ jobs:
${{ runner.temp }}/graph-index-gate
if-no-files-found: ignore
retention-days: 14
+
+ windows-smoke:
+ name: windows smoke (${{ matrix.os }})
+ runs-on: ${{ matrix.os }}
+ timeout-minutes: 30
+ strategy:
+ fail-fast: false
+ matrix:
+ os: [windows-latest, windows-11-arm]
+ steps:
+ - uses: actions/checkout@v6
+ with:
+ persist-credentials: false
+ - uses: actions/setup-node@v6
+ with:
+ node-version: 22
+ - run: npm install --legacy-peer-deps --no-audit --no-fund
+ - name: Build and pack with the POSIX build script
+ shell: pwsh
+ env:
+ npm_config_script_shell: C:\Program Files\Git\bin\bash.exe
+ run: |
+ New-Item -ItemType Directory -Force -Path "$env:RUNNER_TEMP\windows-smoke-pack" | Out-Null
+ npm run build
+ if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
+ npm pack --pack-destination "$env:RUNNER_TEMP\windows-smoke-pack"
+ if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
+ - name: Install and run the packed CLI under Windows Worker Compose
+ shell: pwsh
+ run: |
+ $tarballs = @(Get-ChildItem "$env:RUNNER_TEMP\windows-smoke-pack\agentmemory-agentmemory-*.tgz")
+ if ($tarballs.Count -ne 1) { throw "expected one packed tarball, found $($tarballs.Count)" }
+ node scripts/release-gate/windows-smoke.mjs --tarball $tarballs[0].FullName --out "$env:RUNNER_TEMP\windows-smoke"
+ if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
+ - if: always()
+ uses: actions/upload-artifact@v7
+ with:
+ name: windows-smoke-${{ matrix.os }}-${{ github.run_attempt }}
+ path: ${{ runner.temp }}/windows-smoke
+ if-no-files-found: ignore
+ retention-days: 14
diff --git a/AGENTS.md b/AGENTS.md
index c53122c1e1..c2e9d97cc5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -4,7 +4,7 @@
agentmemory is a persistent memory system for AI coding agents, built on iii-engine's three primitives (Worker/Function/Trigger). Everything goes through `registerFunction`/`registerTrigger`/`sdk.trigger()` — never bypass iii-engine with standalone SQLite or in-process alternatives.
-- **Engine**: iii-sdk 0.25.0 with @iii-dev/helpers 0.25.0 (Worker Compose-managed iii-engine 0.25.0 on port 49134; the client type is `IIIClient`, HTTP requests are `HttpRequest` from `@iii-dev/helpers/http`)
+- **Engine**: iii-sdk 0.25.1 with @iii-dev/helpers 0.25.1 (Worker Compose-managed iii-engine 0.25.1 on port 49134; the client type is `IIIClient`, HTTP requests are `HttpRequest` from `@iii-dev/helpers/http`)
- **State**: iii state worker with a file-backed KV store by default (`./data/state_store.db`); Docker pins `save_interval_ms` to 2000 ms
- **Build**: TypeScript → ESM via tsdown, output to `dist/`
- **Test**: vitest (`npm test` excludes integration tests)
@@ -101,17 +101,17 @@ Hook scripts in `src/hooks/` are standalone Node.js scripts (no iii-sdk import).
## Testing
-- Before every commit run, in order: `npm run build`, `npm run skills:gen`, `npm run docs:sync`, `npm run skills:check`, `npm test` (4,100+ tests). Commit anything the generators changed. CI runs the same build, skills check and tests.
+- Before every commit run, in order: `npm run build`, `npm run skills:gen`, `npm run docs:sync`, `npm run skills:check`, `npm test` (4,900+ tests). Commit anything the generators changed. CI runs the same build, skills check and tests.
- Before any npm publish: `npm run release:gate` must pass. It installs the packed tarballs into a clean home and runs capture, recovery, restart, export/import, MCP and status checks against the installed CLI (see CONTRIBUTING.md, Release process)
- Mock pattern: `vi.mock("iii-sdk")` with mock `sdk.trigger`, `kv.get/set/list`
- Test files go in `test/` with `.test.ts` extension
- Follow existing patterns in `test/crystallize.test.ts` for function tests
-## Current Stats (v0.9.31)
+## Current Stats (v0.9.33)
- 54 MCP tools visible by default; `AGENTMEMORY_TOOLS=core` selects 8 essentials
-- 146 REST endpoints
+- 147 REST endpoints
- 6 MCP resources, 3 MCP prompts
- 12 hooks, 17 skills
- 322+ iii functions
-- 4,100+ tests
+- 4,900+ tests
diff --git a/CHANGELOG.md b/CHANGELOG.md
index abac402cbc..16a6992fab 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,83 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
## [Unreleased]
+## [0.9.33] — 2026-11-09
+
+### Upgrade notes
+
+- agentmemory now pins iii 0.25.1 (engine, `iii-sdk` and `@iii-dev/helpers`) with state 0.22.22 and http 0.22.8. The first start after the upgrade installs them (#1634, #1694).
+- `GET /agentmemory/memories` and `GET /agentmemory/relations` without `limit` return 413 with a paging hint when the full list is larger than the transport limit, as `/semantic` and `/procedural` already did. Use `?limit=N` and `nextCursor`. The viewer and CLI already page (#1636).
+- Docker installs: the root and Coolify Compose files now forward `AGENTMEMORY_LLM_PROVIDER`. A provider key alone does not turn on LLM features; set `AGENTMEMORY_LLM_PROVIDER` to the provider whose key you configured. Docker installs that set only a key ran without LLM summaries since 0.9.32 (#1700).
+
+### Added
+
+- **State scopes above 64 MiB keep working.** Whole-scope reads page through `state::list_keys` instead of one frame, and mesh export pages when given `limit` or `cursor` (#1636). The transport cap is 64 MiB, up from 16 MiB (#1634).
+- `GET /agentmemory/sessions` filters by `startedAfter`, `startedBefore`, `endedAfter` and `endedBefore` (#1527 by @yxtay).
+- `AGENTMEMORY_SUMMARY_TIMEOUT_MS` sets the summary budget for large chunked sessions on slow or local LLMs (default 120 s) (#1689).
+- `memory_diagnose` and `memory_heal` have a `facets` category that finds and removes facets whose target was deleted (#1698).
+
+### Fixed
+
+- **Search:** saved memories are no longer capped at three per search (#1696). Evicted memories leave the search indexes (#1601 by @DimitriChrysafis). Boot detects historical gaps in a partially embedded vector index (#1687 by @mvanhorn). CLIP text queries use the CLIP text tower, so text-to-image search returns matching images (#1250 by @anhtahaylove).
+- **Hooks:** PreToolUse sends its context in the hook envelope, so the model sees it (#1693). Enrichment is scoped to the current project (#1220 by @devon3000). The Claude Code SessionEnd hook has time to finish (#1692). Captured text is redacted before it is cut to length, and compound secret key names are redacted (#1695, #1701). Cursor subagent stop type and summary fields are mapped (#1684 by @mothieras).
+- **Providers:** placeholder keys such as `sk-...` count as unset when agentmemory picks the LLM provider (#1588 by @dmazhukov). A success clears the circuit breaker failure count (#1350 by @redeye1011), and content-filter rejections no longer open the breaker (#1277 by @dKaulig).
+- The MCP shim waits 190 s for proxied calls instead of 15 s, past the server's 180 s limit, so long consolidate and reflect calls finish (#1691). `memory_action_create` records the creating agent (#1697).
+- Consolidation keeps provenance and version heads across retries, and saved pattern memories reach the procedural tier (#1545, #1690). Reflection bounds its evidence and insight responses and keeps other projects' crystals out of a scoped reflection (#1544).
+- `health` reports CPU relative to the machine's cores, not one core (#1286 by @DanielCarmingham).
+- `agentmemory demo` stops the Compose workers it started on Windows (#1688 by @Mike-Animal-Counseling). Generated Compose values keep newlines (#1708 by @zhichao-poper).
+- Fresh installs retry the iii engine download up to three times within two minutes on network errors, timeouts and HTTP 408, 429 and 5xx responses, and wait as long as `Retry-After` asks (#1719).
+- `agentmemory connect` honors `CLAUDE_CONFIG_DIR` for Claude Code detection, MCP configuration and hooks (#1703 by @mothieras).
+
+### Infrastructure
+
+- `@agentmemory/pi` 0.1.1 and `@agentmemory/fs-watcher` 0.2.0 (#1683). GitHub Actions bumps (#967, #1473). Config reference env count regenerated (#1705). The Windows release gate fails when its leftover-process query fails (#1711), and the CLIP tests check both towers (#1712). The release gate runs the packed package on Linux x64 and arm64, macOS arm64 and Intel, and Windows x64 and arm64 (#1716).
+
+## [0.9.32] — 2026-11-04
+
+### Upgrade notes
+
+- **Breaking: an API key alone no longer turns on an outside provider.** LLM summaries, compression, consolidation and reflection run only when `AGENTMEMORY_LLM_PROVIDER` names `anthropic`, `openai`, `gemini`, `openrouter` or `minimax` and that provider's key is set. `AGENTMEMORY_ALLOW_AGENT_SDK=true` stays the other route. Cloud embeddings run only when `EMBEDDING_PROVIDER` names the provider; `EMBEDDING_PROVIDER=local` stays on-device, and unset means BM25 and graph search only. If a key is present without a choice, boot, `doctor`, `status` and the viewer name the exact line to add (#1664).
+- `OPENAI_API_KEY_FOR_LLM` is removed. Set `AGENTMEMORY_LLM_PROVIDER` instead (#1664).
+- **Hooks send nothing to a remote `http://` server.** A non-loopback `AGENTMEMORY_URL` must use HTTPS; captures for a plain-HTTP remote server are dropped, not spooled. The secret is sent only to loopback or HTTPS addresses (#1664).
+- The PreCompact hook prints stored memory only with `AGENTMEMORY_INJECT_CONTEXT=true`, the same gate as SessionStart (#1664).
+- The Claude Code plugin asks for the server URL and secret through plugin settings. The secret is kept in the system credential store. The Devin plugin no longer forwards `AGENTMEMORY_SECRET` from the environment (#1664).
+
+### Added
+
+- **iii installs itself on Windows.** A fresh `agentmemory` on win32 downloads the pinned iii zip, checks its SHA-256 and extracts it with the system `tar.exe`, falling back to PowerShell `Expand-Archive` (#1670).
+- MCP tools carry `readOnlyHint` and `destructiveHint` annotations, and the plugin README states what the hooks record, where it is kept and how to delete it. Privacy policy: https://agent-memory.dev/privacy (#1664).
+- `memory_lesson_save` accepts `sourceIds` (#1661).
+- agentmemory is listed in the [OpenAI plugin directory](https://chatgpt.com/plugins/plugins_6ac50a1b89948191906ff15c72357972) for Codex (skills; pair with `agentmemory connect codex`), the Hermes plugin catalog and ClawHub. For Hermes and OpenClaw, install with `hermes plugins install agentmemory` or `openclaw plugins install clawhub:agentmemory`; the README and the Hermes and OpenClaw guides describe both routes beside `agentmemory connect`.
+- Each published release builds a `linux/amd64` and `linux/arm64` image and pushes it to Docker Hub as `ghumarerohit/agentmemory:`; `latest` follows the highest stable version (#1677).
+- The MCP stdio shim records why it exits in `mcp-crash.log` in the data directory (owner-only, rotated at 1 MiB) and saves its fallback store before writing to stderr (#1662, #1674).
+
+### Fixed
+
+- **Worker Compose starts on native Windows.** Worker commands, the worker PATH and project ownership checks with `\\?\` and 8.3 paths are fixed; `agentmemory stop` waits long enough for every worker (#1641). The launcher retries a slow `iii --version` probe and never waits on a hidden install prompt (#1658). `doctor` does not prompt without a terminal or with `CI` set (#1671). `status` and `stop` output no longer include iii SDK debug lines (#1672).
+- **Boot no longer races the state worker.** agentmemory waits up to 120 s for the state worker to register before boot reads, and the keyword rebuild keeps retrying, so a slow start no longer leaves vector recovery paused or the keyword index empty until restart (#1627 by @cbsincool, #1626 by @Tyxiel, #1660).
+- A stale Worker Compose PID reused by an unrelated process after a reboot no longer causes a start crash loop (#1622 by @pei711).
+- The Docker image keeps the optional dependencies that local embeddings need (#1651 by @mothieras).
+- Slot tools are hidden and return 503 when `AGENTMEMORY_SLOTS` is off (#1659).
+- Search: CJK queries recall core observations again (#1553 by @akushonkamen); scoped smart-search fills short pages from a deeper window (#1669 by @dmazhukov); project-filtered recall excludes unscoped memories (#1647 by @reevesc88); search responses keep the original memory type (#1646 by @reevesc88).
+- An OpenAI reply cut off at `max_tokens` fails over instead of being stored as the result (#1495 by @Rex57).
+- Orphaned index generations are reclaimed (#1256 by @inix-x), and the MCP graph stats resource reads a bounded snapshot instead of listing the whole graph (#1260 by @inix-x).
+- Facet tags are removed when lessons are deleted or observations forgotten (#1642 by @xh123637). The session sweep skips rows without an id (#1645 by @dmazhukov). Hook truncation keeps surrogate pairs whole (#1598 by @dmazhukov).
+- Copilot CLI subagent reports are stored with their reply. The `subagentStop` hook reads Copilot's camelCase fields, so a report is no longer empty and a retry is no longer stored twice. The reply is redacted before it is cut to 4000 characters (#1599 by @dmazhukov).
+- The Hermes project git probe no longer inherits the worker's stdin, which could hang on Windows (#1663). The Cline CLI MCP configuration uses its native settings path (#1633).
+- A superseded memory gets a strictly later `updatedAt`, so mesh sync carries the change to peers (#1665 by @egantz).
+- pi includes recalled lessons in search and can read a full lesson by ID, scoped to its project (#1605 by @YeChenglin8888).
+- `npm run build` works under the Windows `cmd.exe` shell (#1362 by @mattamundson).
+- `.env.example` names the Agent SDK route and documents `MAX_OBS_PER_SESSION` as a hard per-session cap (#1675, from #1503 by @Rex57).
+- The Claude Code plugin passes its URL and secret settings to the MCP server as `CLAUDE_PLUGIN_OPTION_AGENTMEMORY_URL` and `CLAUDE_PLUGIN_OPTION_AGENTMEMORY_SECRET`, the names the plugin directory accepts. An empty URL setting no longer hides `AGENTMEMORY_URL` from the environment, and an empty secret setting still never sends `AGENTMEMORY_SECRET` from the environment.
+
+### Changed
+
+- The Claude Code plugin hooks run in exec form (`command` plus `args`), so the plugin path reaches Node as one argument with no shell quoting. The plugin and `connect claude-code --with-hooks` now need Claude Code 2.1.139 or later.
+
+### Known issues
+
+- On Windows, `agentmemory stop` takes about 60 s and each start opens empty console windows for the engine and workers. Both come from iii (iii-hq/iii#2430).
+
## [0.9.31] — 2026-10-25
### Upgrade notes
@@ -297,6 +374,8 @@ Wave release closing several breaking regressions reported against v0.9.26, plus
- `/agentmemory:forget` skill still calls `memory_governance_delete` which only touches `KV.memories` and never observations ([#833](https://github.com/rohitg00/agentmemory/issues/833)). Skill rewrite + new `memory_forget` MCP tool tracked separately.
- `crypto.randomUUID()` global-only on Node <19 ([#715](https://github.com/rohitg00/agentmemory/issues/715)). Drop-in import fix tracked.
+[0.9.33]: https://github.com/rohitg00/agentmemory/compare/v0.9.32...v0.9.33
+[0.9.32]: https://github.com/rohitg00/agentmemory/compare/v0.9.31...v0.9.32
[0.9.31]: https://github.com/rohitg00/agentmemory/compare/v0.9.30...v0.9.31
[0.9.30]: https://github.com/rohitg00/agentmemory/compare/v0.9.29...v0.9.30
[0.9.29]: https://github.com/rohitg00/agentmemory/compare/v0.9.28...v0.9.29
diff --git a/INSTALL_FOR_AGENTS.md b/INSTALL_FOR_AGENTS.md
index 49d6e11120..4464c49ad3 100644
--- a/INSTALL_FOR_AGENTS.md
+++ b/INSTALL_FOR_AGENTS.md
@@ -4,9 +4,9 @@ You are a coding agent. Follow this runbook top to bottom to install agentmemory
## What you are installing
-agentmemory is a local memory server for coding agents. Its CLI starts an iii Worker Compose runtime using the pinned iii 0.25.0 engine and registry workers `state@0.22.20` and `http@0.22.7`. The default listeners are REST/MCP HTTP on port 3111, the viewer on 3113, and the internal engine WebSocket on 49134. The viewer receives live updates as SSE through `GET /agentmemory/viewer/events` on the REST port.
+agentmemory is a local memory server for coding agents. Its CLI starts an iii Worker Compose runtime using the pinned iii 0.25.1 engine and registry workers `state@0.22.22` and `http@0.22.8`. The default listeners are REST/MCP HTTP on port 3111, the viewer on 3113, and the internal engine WebSocket on 49134. The viewer receives live updates as SSE through `GET /agentmemory/viewer/events` on the REST port.
-The CLI downloads the pinned engine into `~/.agentmemory/bin` on macOS/Linux. Native Windows needs a manually installed pinned `iii.exe`; WSL2 follows the Linux path. Persistent state defaults to `~/Library/Application Support/agentmemory` on macOS, `$XDG_DATA_HOME/agentmemory` or `~/.local/share/agentmemory` on Linux, and `%APPDATA%\agentmemory` on Windows. Override the directory with `--data-dir ` or `AGENTMEMORY_DATA_DIR`, and reuse the same override on every restart. `AGENTMEMORY_ENV_FILE` selects a non-default env file. Instance 0 reuses an existing `./data/state_store.db` when present. `--instance N` creates an isolated directory and port set for another runtime.
+The CLI downloads the pinned engine into `~/.agentmemory/bin`. On native Windows it downloads and extracts the pinned ZIP; WSL2 follows the Linux path. Persistent state defaults to `~/Library/Application Support/agentmemory` on macOS, `$XDG_DATA_HOME/agentmemory` or `~/.local/share/agentmemory` on Linux, and `%APPDATA%\agentmemory` on Windows. Override the directory with `--data-dir ` or `AGENTMEMORY_DATA_DIR`, and reuse the same override on every restart. `AGENTMEMORY_ENV_FILE` selects a non-default env file. Instance 0 reuses an existing `./data/state_store.db` when present. `--instance N` creates an isolated directory and port set for another runtime.
Default keyless mode needs no API key or cloud account and disables vector embeddings. `memory_recall` (`mem::search`) uses BM25, while `memory_smart_search` can also fuse structural graph matches when graph data exists. Semantic vector recall is an explicit opt-in: set `EMBEDDING_PROVIDER=local` for on-device `Xenova/all-MiniLM-L6-v2`, or configure a supported remote embedding provider. Local inference is free, but the first embedding request downloads the model and therefore needs network access and extra startup time. An LLM provider is separate; LLM-written observation compression requires both a provider and `AGENTMEMORY_AUTO_COMPRESS=true`.
@@ -14,7 +14,7 @@ Default keyless mode needs no API key or cloud account and disables vector embed
- Node.js >= 20 with npm and npx. Check with `node -v`, `npm -v`, and `npx -v`.
- macOS/Linux automatic iii installation also requires `curl`, a POSIX `sh`, and `tar`. Check with `command -v curl sh tar`. Minimal images such as `node:20-slim` may not include them.
-- Windows: WSL2 follows the Linux path. Native Windows requires the pinned iii-engine v0.25.0 binary installed manually. Native automated `connect` supports only `copilot-cli`; configure other Windows agents manually. WSL `connect` applies only to agents installed in that same WSL environment.
+- Windows: WSL2 follows the Linux path. Native Windows installs the pinned iii-engine v0.25.1 ZIP automatically. Native `connect` works for every adapter. WSL `connect` applies only to agents installed in that same WSL environment.
- Default ports 3111 (REST), 3113 (viewer), and 49134 (engine) must be free. Viewer events are carried over REST.
## Running non-interactively
@@ -34,20 +34,20 @@ command -v curl sh tar
Expect: Node prints v20 or newer, npm succeeds, and macOS/Linux prints a path for each automatic-installer dependency.
-For native Windows, install the engine before continuing:
+If the automatic install fails on native Windows, install the engine manually:
```powershell
# Download the matching archive from the pinned release:
-# https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0
+# https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1
# Extract iii.exe to a directory on PATH, such as $HOME\.local\bin, then verify:
iii.exe --version
```
-Expect: exactly `0.25.0`. Verify the archive against its matching SHA-256 asset before extracting it. Do not install an unpinned iii release.
+Expect: exactly `0.25.1`. Verify the archive against its matching SHA-256 asset before extracting it. Do not install an unpinned iii release.
## 2. Start the server
-The canonical command downloads the npm package and, on macOS/Linux, auto-installs its pinned iii-engine into the private agentmemory bin directory. Run it in a dedicated terminal:
+The canonical command downloads the npm package and auto-installs its pinned iii-engine into the private agentmemory bin directory. Run it in a dedicated terminal:
```bash
npx -y @agentmemory/agentmemory@latest
@@ -61,7 +61,7 @@ npx -y @agentmemory/agentmemory@latest --data-dir /absolute/path/to/agentmemory-
For a second isolated runtime, add `--instance 1`; it stores data under `instance-1` and defaults to ports 3211 (REST), 3213 (viewer), and 49234 (engine). `--instance N` supports N from 0 to 50. Do not use `--port` alone for concurrent daemons: it changes ports but preserves instance 0's canonical lifecycle ownership. Use `--instance` for isolation.
-Expect: iii 0.25.0 starts, the agentmemory worker registers with iii, and the ready panel lists REST, viewer, and engine addresses. First boot can take longer while the engine binary and registry workers are installed.
+Expect: iii 0.25.1 starts, the agentmemory worker registers with iii, and the ready panel lists REST, viewer, and engine addresses. First boot can take longer while the engine binary and registry workers are installed.
## 3. Validate the server and runtime ports
@@ -100,7 +100,7 @@ The first embedding request downloads `Xenova/all-MiniLM-L6-v2`; wait for that d
## 5. Wire MCP into the calling agent
-Detect which agent is running this runbook, then wire its MCP config. On native Windows, run this automated step only for `copilot-cli`:
+Detect which agent is running this runbook, then wire its MCP config:
```bash
npx -y @agentmemory/agentmemory@latest connect
@@ -110,7 +110,7 @@ Supported agent names:
`claude-code`, `copilot-cli`, `codex`, `cursor`, `gemini-cli`, `opencode`, `cline`, `continue`, `droid`, `hermes`, `openclaw`, `openhuman`, `pi`, `omp`, `qwen`, `warp`, `zed`, `antigravity`, `kiro`.
-If you cannot tell which agent you are, default to `claude-code` on macOS/Linux. On native Windows, `copilot-cli` is the only automated adapter; configure all other agents with the manual MCP block in the README. Run `connect` inside WSL only when the target agent is installed inside the same WSL environment. After wiring, restart the agent or run its MCP reload command (for example `/mcp` in Claude Code) so it picks up the server.
+If you cannot tell which agent you are, default to `claude-code` on macOS/Linux. Run `connect` inside WSL only when the target agent is installed inside the same WSL environment. After wiring, restart the agent or run its MCP reload command (for example `/mcp` in Claude Code) so it picks up the server.
Expect: the agent now lists agentmemory's tools. With the server running you should see the full set of 54 tools (for example `memory_save`, `memory_smart_search`, `memory_sessions`). If you see only 7 tools, the MCP shim could not reach the server; see Troubleshooting.
@@ -216,7 +216,7 @@ The MCP server exposes 54 tools by default (`--tools all`). Use `--tools core` (
- `The engine process started but the REST API never responded.`: inspect the REST, viewer, and engine ports, confirm the pinned iii process stayed alive, and use `--verbose` for captured engine stderr.
- Engine version conflict / another iii engine already running: if an unmanaged engine is already listening on the engine port, agentmemory will not adopt it. Stop that engine or choose another `--instance` or `--port`. The CLI keeps its private pinned binary separate from a user-managed `iii` on `PATH`.
- Only 7 tools visible in the agent: the MCP shim is in local fallback because it could not reach a server. Start `npx -y @agentmemory/agentmemory@latest`, ensure `AGENTMEMORY_URL` points at it (default `http://localhost:3111`), then reload MCP.
-- Native Windows: install the pinned v0.25.0 `iii.exe` manually or use WSL2. Automated `connect` supports only `copilot-cli`; configure other native agents manually.
+- Native Windows: if the automatic engine install fails, install the pinned v0.25.1 `iii.exe` manually or use WSL2.
- Semantic demo query returns zero hits: this is expected with vectors disabled in default keyless mode. Set `EMBEDDING_PROVIDER=local`, restart, allow the first model download to complete, and rerun the demo.
## Report success
@@ -224,7 +224,7 @@ The MCP server exposes 54 tools by default (`--tools all`). Use `--tools core` (
Report back to the user:
- agentmemory installed, version, and the server running on port 3111
-- iii-engine v0.25.0 running, the selected platform data directory, REST/viewer/engine ports, and the status `enginePinnedVersion`
+- iii-engine v0.25.1 running, the selected platform data directory, REST/viewer/engine ports, and the status `enginePinnedVersion`
- which agent was wired via `agentmemory connect`, and the tool count the agent now sees
- the save and recall round-trip returned the probe memory after a full stop/start
- the viewer is available at `http://localhost:3113`
diff --git a/README.md b/README.md
index b371b080e4..e12cba755a 100644
--- a/README.md
+++ b/README.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -332,14 +332,14 @@ Latest release notes: [CHANGELOG.md](CHANGELOG.md).
---
-### What's new in 0.9.31
+### What's new in 0.9.33
-- **More focused recall:** project and agent scopes, saved-memory retrieval, explicit context budgets and full-source expansion.
-- **Less repeated work:** incremental session summaries skip unchanged observations; exports page through stored data.
-- **More native integrations:** installable Pi package, OMP and DeepSeek Harness plugins, and improved Cursor workspace attribution.
-- **Safer recovery:** compression, import validation and runtime recovery fixes, with status and activity visible in the viewer.
+- **Large stores keep working:** state reads page, so scopes above 64 MiB no longer fail, on iii 0.25.1.
+- **Better recall:** saved memories are no longer capped at three per search, and evicted memories leave the indexes.
+- **Hooks reach the model:** PreToolUse context arrives in the hook envelope, scoped to the current project.
+- **Steadier providers:** placeholder keys count as unset, and the circuit breaker resets on success.
-[Release notes and contributor credits](https://github.com/rohitg00/agentmemory/releases/tag/v0.9.31).
+[Release notes and contributor credits](https://github.com/rohitg00/agentmemory/releases/tag/v0.9.33).
@@ -474,7 +474,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code without the plugin install (MCP-standalone path)
-If you wire agentmemory's MCP server through `~/.claude.json` directly instead of using `/plugin install`, Claude Code never resolves `${CLAUDE_PLUGIN_ROOT}` and you have to point hook scripts at absolute paths in `~/.claude/settings.json`. Those paths typically embed the agentmemory version (e.g. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), so the next upgrade silently breaks every hook.
+If you wire agentmemory's MCP server directly through the default `~/.claude.json` file instead of using `/plugin install`, Claude Code never resolves `${CLAUDE_PLUGIN_ROOT}` and you have to point hook scripts at absolute paths in the default `~/.claude/settings.json` file. Those paths typically embed the agentmemory version (e.g. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), so the next upgrade silently breaks every hook.
Workaround:
@@ -482,11 +482,16 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-This merges the same hook commands into `~/.claude/settings.json` with absolute paths resolved to the bundled `plugin/` directory of the currently installed `@agentmemory/agentmemory` package. Re-run the command after upgrading agentmemory to refresh the paths. User entries in the same file are preserved; only previous agentmemory entries are replaced. Using the `/plugin install` path remains the recommended approach.
-For remote or protected deployments, launch Claude Code with `AGENTMEMORY_URL` and `AGENTMEMORY_SECRET` set. The plugin passes both values through to its bundled MCP server; when `AGENTMEMORY_URL` is empty, the MCP shim uses `http://localhost:3111`.
+This command configures the MCP server and merges the bundled hooks into Claude Code’s user configuration. When `CLAUDE_CONFIG_DIR` is unset, empty, or whitespace-only, it uses `~/.claude.json` for MCP and `~/.claude/settings.json` for hooks. Other directory values are used exactly as provided, including leading and trailing whitespace. For a custom directory, set `CLAUDE_CONFIG_DIR` to the same non-empty value for this command and Claude Code; the files are then `$CLAUDE_CONFIG_DIR/.claude.json` and `$CLAUDE_CONFIG_DIR/settings.json`, respectively. Claude Code must receive this value in its launch environment, even if the connector reads it from AgentMemory’s `.env`. Create the custom directory before running this command; otherwise, the connector skips Claude Code as not detected. If the shell value is whitespace-only, unset `CLAUDE_CONFIG_DIR` before launching Claude Code so it also uses the default profile. Use an absolute path. Relative paths are resolved from the working directory, so both commands must run from the same directory.
+
+Hook commands use absolute paths to the installed package’s bundled `plugin/` directory. Re-run the command after upgrading agentmemory to refresh those paths. User entries in the configuration files are preserved; only previous agentmemory entries are replaced. Using `/plugin install` remains the recommended approach.
+
+For a remote server with the plugin, enter its `https://` URL and secret in the plugin settings that Claude Code asks for when you enable the plugin. The hooks and the bundled MCP server read both from there. With the URL setting empty, they use `AGENTMEMORY_URL` from your environment, then `http://localhost:3111`; with the secret setting empty, they send only the local server's own secret, and only to a loopback address. With `agentmemory connect claude-code` there are no plugin settings: set `AGENTMEMORY_URL` and `AGENTMEMORY_SECRET` in the environment that starts Claude Code.
### Codex CLI (Codex plugin platform)
+Agent Memory is listed in the [OpenAI plugin directory](https://chatgpt.com/plugins/plugins_6ac50a1b89948191906ff15c72357972). That listing adds the 17 skills only. Start the memory server and wire its MCP server with `agentmemory connect codex` so the skills can call the memory tools. For the MCP server, hooks and skills in one plugin, use the repository marketplace below.
+
```bash
# 1. start the memory server in a separate terminal
npx -y @agentmemory/agentmemory@latest
@@ -528,7 +533,7 @@ agentmemory connect copilot-cli
copilot plugin install rohitg00/agentmemory:plugin
```
-`agentmemory connect copilot-cli` merges `mcpServers.agentmemory` into `~/.copilot/mcp-config.json` (or `$COPILOT_HOME/mcp-config.json` when `COPILOT_HOME` is set) and preserves existing servers. On native Windows this is the only automated `connect` adapter; configure every other native Windows agent manually. WSL `connect` is supported only when the target agent is installed in that same WSL environment. Copilot picks up the MCP server on next launch or after `/mcp`. Install the plugin as well when you want the full hook/skill experience.
+`agentmemory connect copilot-cli` merges `mcpServers.agentmemory` into `~/.copilot/mcp-config.json` (or `$COPILOT_HOME/mcp-config.json` when `COPILOT_HOME` is set) and preserves existing servers. WSL `connect` is supported only when the target agent is installed in that same WSL environment. Copilot picks up the MCP server on next launch or after `/mcp`. Install the plugin as well when you want the full hook/skill experience.
### Cursor
@@ -557,51 +562,39 @@ Pi also supports an installable `@agentmemory/pi` package. See the [Pi package g
Guides: [Pi](integrations/pi/), [Oh My Pi](integrations/omp/), [DSH](docs/dsh.md).
-
-OpenClaw (paste this prompt)
+### OpenClaw (ClawHub)
-```text
-Install agentmemory for OpenClaw. Run `npx -y @agentmemory/agentmemory@latest` in a separate terminal to start the memory server on localhost:3111. Then add this to my OpenClaw MCP config so agentmemory is available with all 54 memory tools:
+agentmemory is listed on ClawHub: [clawhub.ai/plugins/agentmemory](https://clawhub.ai/plugins/agentmemory).
-{
- "mcpServers": {
- "agentmemory": {
- "command": "npx",
- "args": ["-y", "@agentmemory/mcp"],
- "env": {
- "AGENTMEMORY_URL": "http://localhost:3111"
- }
- }
- }
-}
+```bash
+# 1. start the memory server in a separate terminal
+npx -y @agentmemory/agentmemory@latest
-Restart OpenClaw. Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper memory-slot integration, copy `integrations/openclaw` to `~/.openclaw/extensions/agentmemory` and enable `plugins.slots.memory = "agentmemory"` in `~/.openclaw/openclaw.json`.
+# 2. install the plugin from ClawHub
+openclaw plugins install clawhub:agentmemory
```
-Full guide: [`integrations/openclaw/`](integrations/openclaw/)
+Then select agentmemory as the memory plugin and allow it to read conversations in `~/.openclaw/openclaw.json`: set `plugins.slots.memory` to `"agentmemory"` and `plugins.entries.agentmemory.hooks.allowConversationAccess` to `true`. Without conversation access, capture is blocked. Restart OpenClaw and run `openclaw config validate`.
-
-
-
-Hermes Agent (paste this prompt)
+`agentmemory connect openclaw` does the same from an installed package: it installs the plugin and skills, selects the memory slot and grants conversation access. Add `--with-mcp` for the full MCP tool set. Full guide: [`integrations/openclaw/`](integrations/openclaw/).
-```text
-Install agentmemory for Hermes. Run `npx -y @agentmemory/agentmemory@latest` in a separate terminal to start the memory server on localhost:3111. Then add this to ~/.hermes/config.yaml so Hermes can use agentmemory as an MCP server with all 54 memory tools:
+### Hermes Agent (Hermes plugin catalog)
-mcp_servers:
- agentmemory:
- command: npx
- args: ["-y", "@agentmemory/mcp"]
+agentmemory is listed in the Hermes plugin catalog: [hermes-agent.nousresearch.com/marketplace/agentmemory](https://hermes-agent.nousresearch.com/marketplace/agentmemory).
-memory:
- provider: agentmemory
+```bash
+# 1. start the memory server in a separate terminal
+npx -y @agentmemory/agentmemory@latest
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+# 2. install the reviewed catalog entry, then select it as the memory provider
+hermes plugins install agentmemory
+hermes memory setup
+hermes memory status
```
-Full guide: [`integrations/hermes/`](integrations/hermes/)
+In `hermes memory setup`, select AgentMemory and enter the server URL and its secret. Hermes Desktop can install it from the link `hermes://plugin/install?catalog=agentmemory`. The catalog installs the commit that Hermes reviewed, so it can lag the latest npm release.
-
+`agentmemory connect hermes` installs the provider and the bundled skills from the installed package instead. Add `--with-mcp` for the full MCP tool set. Full guide: [`integrations/hermes/`](integrations/hermes/).
### Other agents
@@ -653,14 +646,15 @@ The agentmemory entry is the **same MCP server block** across every host that us
| **Gemini CLI** | `~/.gemini/settings.json` | `gemini mcp add agentmemory npx -y @agentmemory/mcp --scope user` (auto-merges). |
| **GitHub Copilot CLI (MCP only)** | `~/.copilot/mcp-config.json` | `agentmemory connect copilot-cli` merges `mcpServers.agentmemory`; Copilot picks it up on next launch or `/mcp`. |
| **GitHub Copilot CLI (full plugin)** | Copilot plugin install | `copilot plugin install rohitg00/agentmemory:plugin` for the plugin from the GitHub subdir. |
-| **OpenClaw** | OpenClaw MCP config | Same `mcpServers` block. Deeper: `openclaw plugins install ./integrations/openclaw` claims OpenClaw's memory slot (auto-switches from `memory-core`); set `plugins.entries.agentmemory.hooks.allowConversationAccess=true` or turn capture is silently blocked. See [`integrations/openclaw`](integrations/openclaw/). |
+| **OpenClaw** | `~/.openclaw/openclaw.json` | `openclaw plugins install clawhub:agentmemory` installs the [ClawHub listing](https://clawhub.ai/plugins/agentmemory); `agentmemory connect openclaw` installs the same plugin and also selects `plugins.slots.memory` and grants `hooks.allowConversationAccess`, without which capture is blocked. Add `--with-mcp` for the full tool set. See [`integrations/openclaw`](integrations/openclaw/). |
| **Codex CLI (MCP only)** | `.codex/config.toml` | TOML shape: `codex mcp add agentmemory -- npx -y @agentmemory/mcp`, or add `[mcp_servers.agentmemory]` manually. |
+| **Codex CLI (skills, official listing)** | [OpenAI plugin directory](https://chatgpt.com/plugins/plugins_6ac50a1b89948191906ff15c72357972) | Adds the 17 skills. Pair it with `agentmemory connect codex` for the MCP server. |
| **Codex CLI (full plugin)** | Codex plugin marketplace | `codex plugin marketplace add rohitg00/agentmemory` then `codex plugin add agentmemory@agentmemory`. Registers MCP + 6 lifecycle hooks + 17 skills. Trust hooks and verify capture in your host; see [Codex setup and validation](docs/plugins/codex-local.md). |
| **OpenCode (MCP only)** | `opencode.json` | Different shape: top-level `mcp` key, command as array: `{"mcp": {"agentmemory": {"type": "local", "command": ["npx", "-y", "@agentmemory/mcp"], "enabled": true}}}`. |
| **OpenCode (full plugin)** | `plugin/opencode/` | 22 auto-capture hooks covering session lifecycle, messages, tools, errors. Project attribution is per-session, so one OpenCode process spanning several repositories files each session under its own project. Two slash commands (`/recall`, `/remember`). Copy `plugin/opencode/` into your OpenCode workspace and add the plugin entry to `opencode.json`. See [`plugin/opencode/README.md`](plugin/opencode/README.md) for the full hook table + gap analysis. |
| **pi** | Active Pi agent directory, default `~/.pi/agent` | `agentmemory connect pi --with-mcp` installs native recall/capture, offline replay, 17 skills and the full MCP toolset. Or build `integrations/pi` and use `pi install ./integrations/pi`; after npm publication, `pi install npm:@agentmemory/pi`. Use one method and run `/reload`. See [setup and migration](integrations/pi/). |
| **Oh My Pi (OMP)** | Active OMP agent directory, default `~/.omp/agent/config.yml` | `agentmemory connect omp --with-mcp` installs native recall/capture, offline replay, 17 skills and the full MCP toolset. Restart OMP and run `/agentmemory-status`. See [setup, profiles and commands](integrations/omp/). |
-| **Hermes Agent** | `$HERMES_HOME/config.yaml`, default `~/.hermes/config.yaml` | `agentmemory connect hermes` installs the native provider and skills. Configure its scoped credentials with `hermes memory setup`. Add `--with-mcp` for the wider tool surface. See [setup and scope](integrations/hermes/). |
+| **Hermes Agent** | `$HERMES_HOME/config.yaml`, default `~/.hermes/config.yaml` | `hermes plugins install agentmemory` installs the [Hermes catalog entry](https://hermes-agent.nousresearch.com/marketplace/agentmemory) at its reviewed commit. `agentmemory connect hermes` installs the native provider and skills. Configure its scoped credentials with `hermes memory setup`. Add `--with-mcp` for the wider tool surface. See [setup and scope](integrations/hermes/). |
| **Qwen Code** | `~/.qwen/settings.json` | `agentmemory connect qwen` writes the standard `mcpServers` block. Hook payload is field-compatible with Claude Code, so the existing 12-hook scripts work without modification; wire them via the `hooks` section in the same `settings.json`. |
| **Antigravity IDE / 2.0** | `~/.gemini/config/mcp_config.json` | `agentmemory connect antigravity --with-hooks` installs MCP and capture hooks in the shared customization directory. See [Antigravity setup and limits](docs/plugins/antigravity.md). |
| **Antigravity CLI** (`agy`) | `~/.gemini/config/mcp_config.json` | `agentmemory connect antigravity-cli --with-hooks` uses the same MCP and hook configuration as current IDE versions. Existing installations should refresh with `--force`; see the [upgrade notes](docs/plugins/antigravity.md). |
@@ -694,9 +688,9 @@ npm install && npm run build && npm start
### Windows
-agentmemory runs on Windows 10/11. WSL2 follows the Linux path and can install the pinned engine automatically. Native Windows requires the pinned iii-engine v0.25.0 binary installed manually; download the matching archive from the [iii v0.25.0 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verify its checksum, and place `iii.exe` on `PATH` (for example `%USERPROFILE%\.local\bin\iii.exe`). The CLI does not extract the Windows ZIP automatically.
+agentmemory runs on Windows 10/11. WSL2 follows the Linux path and can install the pinned engine automatically. Native Windows also installs the pinned iii-engine v0.25.1 automatically: the CLI downloads the Windows ZIP, verifies its SHA-256 and extracts `iii.exe` into `%USERPROFILE%\.agentmemory\bin`. If that fails, download the matching archive from the [iii v0.25.1 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verify its checksum, and extract `iii.exe` into the same directory.
-Native Windows automated MCP wiring supports only `agentmemory connect copilot-cli`. For other native Windows agents, use the manual MCP block from [Other agents](#other-agents). Run `connect` inside WSL only when the target agent is installed in that same WSL environment.
+`agentmemory connect ` works on native Windows. It writes the MCP server as `cmd /c npx -y @agentmemory/mcp`, because Windows cannot start `npx` without a shell, and it writes hook script paths as absolute paths with forward slashes, either quoted or passed as a separate argument, so a home folder with spaces is safe. Antigravity hooks cannot use quoted paths. When the install path has spaces, `connect antigravity --with-hooks` uses the Windows short (8.3) path. If the short path is not available, it prints the hook JSON to paste by hand, and the MCP wiring still applies. Run `connect` inside WSL only when the target agent is installed in that same WSL environment.
**Standalone MCP only (no engine).** If you only need MCP tools and do not need the REST API, viewer, or runtime services:
@@ -866,6 +860,8 @@ Fused with Reciprocal Rank Fusion (RRF, k=60) and session-diversified (max 3 res
When a vector index is populated, `mem::search` (behind `memory_recall`) uses the hybrid BM25 + vector ranker. Without embeddings it uses BM25. `smart-search` can additionally fuse structural graph matches when graph data exists, including in keyless mode. Lesson recall runs on a dedicated in-memory BM25 index instead of scanning the whole corpus per query. Superseded memory versions are excluded from every recall path; the version chain keeps their history.
+Filtered `memory_recall` expands its ranked candidate window until it fills the requested result limit, exhausts the candidate source, or reaches 1,000 candidates. This bound limits work for queries with many unrelated matches. Results can contain fewer items when qualifying records rank below that budget.
+
Vectors survive a crash or force-kill. The vector index is saved in buckets at most every `AGENTMEMORY_INDEX_SAVE_INTERVAL_MS` (10 minutes). Every vector added or removed in between is also written right away to a small pending log in the state store, and the next start replays it without calling the embedding provider. Each successful save empties the log. For older documents without vectors, `AGENTMEMORY_VECTOR_BACKFILL=all` opts into a bounded backfill at startup, capped by `AGENTMEMORY_VECTOR_BACKFILL_MAX` (500). Keep the opt-in set across restarts to process more documents. See [source and vector recovery](docs/reliability/source-and-vector-recovery.md). `/agentmemory/status` and the viewer show the pending log size and the backfill state. Keyless installs write nothing.
BM25 tokenizes Greek, Cyrillic, Hebrew, Arabic, and accented Latin out of the box. For Chinese / Japanese / Korean memories, install the optional segmenters (`npm install @node-rs/jieba tiny-segmenter`) to split CJK runs into word-level tokens; without them, agentmemory soft-falls to whole-run tokenization and prints a one-time hint on stderr.
@@ -878,7 +874,7 @@ Keyless installs disable vector embeddings: `mem::search` uses BM25, while `smar
EMBEDDING_PROVIDER=local
```
-The normal npm install includes the optional `@huggingface/transformers` runtime. The first embedding request downloads `Xenova/all-MiniLM-L6-v2`, so it needs network access and can take longer; subsequent inference runs on-device. Remote providers are auto-detected from their keys unless `EMBEDDING_PROVIDER` overrides them.
+The normal npm install includes the optional `@huggingface/transformers` runtime. The first embedding request downloads `Xenova/all-MiniLM-L6-v2`, so it needs network access and can take longer; subsequent inference runs on-device. Remote embedding providers run only when `EMBEDDING_PROVIDER` names one of them (`gemini`, `openai`, `voyage`, `cohere`, `openrouter`) and its key is set. A key on its own never turns on remote embeddings.
| Provider | Model | Cost | Notes |
|---|---|---|---|
@@ -899,7 +895,7 @@ The normal npm install includes the optional `@huggingface/transformers` runtime
### 54 Tools
-Three tool surfaces, smallest to largest: `AGENTMEMORY_TOOLS=core` trims visibility to 8 essentials (`memory_save`, `memory_recall`, `memory_consolidate`, `memory_smart_search`, `memory_sessions`, `memory_diagnose`, `memory_lesson_save`, `memory_reflect`); the base set below is the registry's 14 foundational tools; the default (`AGENTMEMORY_TOOLS=all`) exposes all 54.
+Three tool surfaces, smallest to largest: `AGENTMEMORY_TOOLS=core` trims visibility to 8 essentials (`memory_save`, `memory_recall`, `memory_consolidate`, `memory_smart_search`, `memory_sessions`, `memory_diagnose`, `memory_lesson_save`, `memory_reflect`); the base set below is the registry's 14 foundational tools; the default (`AGENTMEMORY_TOOLS=all`) exposes all 54, minus the 6 `memory_slot_*` tools until `AGENTMEMORY_SLOTS=true`.
Base tools (14)
@@ -1056,17 +1052,17 @@ The viewer server binds to `127.0.0.1` by default and attaches the server secret
### LLM Providers
-agentmemory auto-detects providers from your environment. A provider makes LLM-backed operations available, but provider configuration alone does not enable LLM-written observation compression. That path requires both a provider and `AGENTMEMORY_AUTO_COMPRESS=true`.
+agentmemory sends session content to an LLM only after you select a provider with `AGENTMEMORY_LLM_PROVIDER`, or turn on the Claude Agent SDK fallback with `AGENTMEMORY_ALLOW_AGENT_SDK=true`. A key that exists in your environment for another tool is never enough. A selected provider makes LLM-backed operations available (session summaries, consolidation, reflection), but it does not enable LLM-written observation compression on its own. That path also requires `AGENTMEMORY_AUTO_COMPRESS=true`.
| Provider | Config | Notes |
|----------|--------|-------|
| **No-op (default)** | No config needed | LLM-backed compress/summarize is disabled. Synthetic compression and BM25 recall still work. See `AGENTMEMORY_ALLOW_AGENT_SDK` below if you used to rely on the Claude-subscription fallback. |
-| Anthropic API | `ANTHROPIC_API_KEY` | Per-token billing |
-| MiniMax | `MINIMAX_API_KEY` | Anthropic-compatible |
-| Gemini | `GEMINI_API_KEY` | Also enables embeddings |
-| OpenRouter | `OPENROUTER_API_KEY` | Any model |
-| OpenAI API | `OPENAI_API_KEY` | Default `gpt-5.6-luna`, override with `OPENAI_MODEL` |
-| **Local (Ollama / LM Studio / vLLM / llama.cpp)** | `OPENAI_API_KEY=local` + `OPENAI_BASE_URL=http://localhost:11434/v1` (Ollama) or `http://localhost:1234/v1` (LM Studio) + `OPENAI_MODEL=` | Anything OpenAI-API-compatible. Zero cost, runs on your hardware. See [Local models](#local-models-ollama--lm-studio--vllm) below. |
+| Anthropic API | `AGENTMEMORY_LLM_PROVIDER=anthropic` + `ANTHROPIC_API_KEY` | Per-token billing |
+| MiniMax | `AGENTMEMORY_LLM_PROVIDER=minimax` + `MINIMAX_API_KEY` | Anthropic-compatible |
+| Gemini | `AGENTMEMORY_LLM_PROVIDER=gemini` + `GEMINI_API_KEY` | Gemini embeddings need `EMBEDDING_PROVIDER=gemini` as well |
+| OpenRouter | `AGENTMEMORY_LLM_PROVIDER=openrouter` + `OPENROUTER_API_KEY` | Any model |
+| OpenAI API | `AGENTMEMORY_LLM_PROVIDER=openai` + `OPENAI_API_KEY` | Default `gpt-5.6-luna`, override with `OPENAI_MODEL` |
+| **Local (Ollama / LM Studio / vLLM / llama.cpp)** | `AGENTMEMORY_LLM_PROVIDER=openai` + `OPENAI_API_KEY=local` + `OPENAI_BASE_URL=http://localhost:11434/v1` (Ollama) or `http://localhost:1234/v1` (LM Studio) + `OPENAI_MODEL=` | Anything OpenAI-API-compatible. Zero cost, runs on your hardware. See [Local models](#local-models-ollama--lm-studio--vllm) below. |
| Claude subscription fallback | `AGENTMEMORY_ALLOW_AGENT_SDK=true` | Opt-in only. Spawns `@anthropic-ai/claude-agent-sdk` sessions; it used to cause unbounded Stop-hook recursion, so it is no longer the default. |
### Local models (Ollama / LM Studio / vLLM)
@@ -1082,6 +1078,7 @@ ollama serve
```env
# ~/.agentmemory/.env
+AGENTMEMORY_LLM_PROVIDER=openai
OPENAI_API_KEY=ollama # any non-empty string; Ollama ignores it
OPENAI_BASE_URL=http://localhost:11434/v1
OPENAI_MODEL=qwen3:8b
@@ -1093,6 +1090,7 @@ Open LM Studio → Local Server tab → Start Server. Pick any chat model from t
```env
# ~/.agentmemory/.env
+AGENTMEMORY_LLM_PROVIDER=openai
OPENAI_API_KEY=lmstudio # any non-empty string; LM Studio ignores it
OPENAI_BASE_URL=http://localhost:1234/v1
OPENAI_MODEL=qwen3-8b # match the model name from LM Studio
@@ -1142,6 +1140,8 @@ Two modes:
What gets tagged when `AGENT_ID` is set: `Session.agentId`, `RawObservation.agentId`, `CompressedObservation.agentId`, `Memory.agentId`. The role flows from `api::session::start` → `mem::observe` → `mem::compress` → KV.
+`GET /agentmemory/sessions` also filters by time with `startedAfter`, `startedBefore`, `endedAfter` and `endedBefore` (ISO 8601, for example `2026-10-09` or `2026-10-09T12:00:00Z`; a value without a zone is read as UTC, and a `+` in an offset must be URL-encoded as `%2B`; after is inclusive, before is exclusive). Sessions with no value for the filtered field are excluded, and an invalid timestamp returns 400.
+
What gets filtered in isolated mode: `mem::smart-search`, `/agentmemory/memories`, `/agentmemory/observations`, `/agentmemory/sessions`. Each endpoint accepts `?agentId=` to override per-request, and `?agentId=*` to opt out of the env scope entirely. `/memories` also accepts `?includeOrphans=true` to surface pre-AGENT_ID memories whose `agentId` is undefined.
Per-call override at the SDK / REST layer: every mutating endpoint (`/session/start`, `/remember`) accepts an `agentId` field in the request body that wins over the env. Useful for runtimes routing many roles through one server process. The MCP `memory_save` tool exposes the same `agentId` field, the standalone stdio server forwards both `agentId` and `project`, and saved memories carry `agentId` into the search index, so agent-scoped search covers memories as well as observations.
@@ -1165,7 +1165,7 @@ The default file store needs no separate database service. Redis is optional wit
### Config File
-Put agentmemory runtime configuration in `~/.agentmemory/.env` instead of exporting variables in every shell. If the viewer shows a setup hint like `export ANTHROPIC_API_KEY=...`, copy it into this file as `ANTHROPIC_API_KEY=...` without the `export` prefix, then restart agentmemory. Set `AGENTMEMORY_ENV_FILE` to use another env-file path.
+Put agentmemory runtime configuration in `~/.agentmemory/.env` instead of exporting variables in every shell. If the viewer shows a setup hint like `export ANTHROPIC_API_KEY=...`, copy it into this file as `ANTHROPIC_API_KEY=...` without the `export` prefix, add `AGENTMEMORY_LLM_PROVIDER=anthropic` to select it, then restart agentmemory. Set `AGENTMEMORY_ENV_FILE` to use another env-file path.
Process environment variables take precedence over values in the file. Restart the server after changing its configuration.
@@ -1185,7 +1185,7 @@ AGENTMEMORY_AUTO_COMPRESS=true
LLM-written observation compression requires both lines: access to an LLM provider (including this explicit subscription fallback) and `AGENTMEMORY_AUTO_COMPRESS=true`. A provider by itself leaves the default synthetic compression path in place.
-Consolidation (graph nodes, lessons, crystals) is on by default whenever an LLM provider is configured. Explicitly opt out with `CONSOLIDATION_ENABLED=false` if you want LLM-free operation. Graph extraction is a separate flag:
+Consolidation (graph nodes, lessons, crystals) is on by default whenever an LLM provider is selected with `AGENTMEMORY_LLM_PROVIDER`, or the Agent SDK fallback is on with `AGENTMEMORY_ALLOW_AGENT_SDK=true`. Explicitly opt out with `CONSOLIDATION_ENABLED=false` if you want LLM-free operation. Graph extraction is a separate flag:
```env
GRAPH_EXTRACTION_ENABLED=true
@@ -1202,8 +1202,14 @@ EMBEDDING_PROVIDER=local
# Optional automatic context injection through the shared hooks
# AGENTMEMORY_INJECT_CONTEXT=true
+# Set the PreToolUse timeout in the hook process environment, not this server file:
+# AGENTMEMORY_ENRICH_TIMEOUT_MS=2000 (default 2000 ms)
+
+# Optional outside LLM for summaries and consolidation. A key alone does nothing;
+# this line selects the provider whose key agentmemory may use.
+# AGENTMEMORY_LLM_PROVIDER=anthropic
-# Optional LLM-written compression; also requires a configured provider
+# Optional LLM-written compression; also requires AGENTMEMORY_LLM_PROVIDER
# AGENTMEMORY_AUTO_COMPRESS=true
# Show 8 essential MCP tools instead of the default 54
@@ -1221,7 +1227,7 @@ The complete reference is [`.env.example`](.env.example), including provider cre
-146 endpoints on port `3111`. The REST API binds to `127.0.0.1` by default. Protected endpoints require `Authorization: Bearer `, and mesh sync endpoints require an explicitly set `AGENTMEMORY_SECRET` on both peers.
+147 endpoints on port `3111`. The REST API binds to `127.0.0.1` by default. Protected endpoints require `Authorization: Bearer `, and mesh sync endpoints require an explicitly set `AGENTMEMORY_SECRET` on both peers.
**Authentication is on by default.** When `AGENTMEMORY_SECRET` is not set (in the shell or in `~/.agentmemory/.env`), the CLI generates a random secret on first start and stores it at `~/.agentmemory/secret`, mirrored to the selected data directory as `secret`, with mode `0600` (the platform-specific default data directory is described above). Bundled clients read the canonical secret first when they talk to a local server: the CLI, the viewer, the hooks under `plugin/scripts`, the MCP server and the `@agentmemory/mcp` shim, the configs written by `agentmemory connect`, and the bundled OpenCode, Pi, OpenClaw, Hermes and filesystem-watcher integrations. The stored secret is only sent to loopback URLs (`localhost`, `127.0.0.0/8`, `::1`). An explicit `AGENTMEMORY_SECRET` always wins, and remote clients need the secret set in their environment. Repository-based Docker self-host deployments and the `deploy/` entrypoints generate and export their own secret. To call the API by hand:
@@ -1307,7 +1313,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ar-SA.md b/READMEs/README.ar-SA.md
index 432c2446ec..de713f7766 100644
--- a/READMEs/README.ar-SA.md
+++ b/READMEs/README.ar-SA.md
@@ -52,7 +52,7 @@
-
+
@@ -71,7 +71,7 @@
-
+
@@ -448,7 +448,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code بدون تثبيت الإضافة (مسار MCP القائم بذاته)
-إذا ربطت خادم MCP الخاص بـ agentmemory عبر `~/.claude.json` مباشرة بدلًا من استخدام `/plugin install`، فإن Claude Code لن يحلّ `${CLAUDE_PLUGIN_ROOT}` مطلقًا، وستحتاج إلى توجيه نصوص الخطافات إلى مسارات مطلقة في `~/.claude/settings.json`. وتُضمِّن تلك المسارات عادة إصدار agentmemory (مثل `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)، فتنكسر جميع الخطافات بصمت عند الترقية التالية.
+إذا ربطت خادم MCP الخاص بـ agentmemory عبر `~/.claude.json` (المسار الافتراضي) مباشرة بدلًا من استخدام `/plugin install`، فإن Claude Code لن يحلّ `${CLAUDE_PLUGIN_ROOT}` مطلقًا، وستحتاج إلى توجيه نصوص الخطافات إلى مسارات مطلقة في `~/.claude/settings.json` (المسار الافتراضي). وتُضمِّن تلك المسارات عادة إصدار agentmemory (مثل `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)، فتنكسر جميع الخطافات بصمت عند الترقية التالية.
الحل البديل:
@@ -456,7 +456,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-يُدمج هذا الأمر نفس أوامر الخطافات في `~/.claude/settings.json` بمسارات مطلقة تُحلَّل إلى دليل `plugin/` المُضمَّن في حزمة `@agentmemory/agentmemory` المثبَّتة حاليًا. أعد تشغيل الأمر بعد ترقية agentmemory لتحديث المسارات. تُحفظ إدخالات المستخدم في نفس الملف؛ ويُستبدل إدخالات agentmemory السابقة فقط. يظل استخدام مسار `/plugin install` هو الأسلوب المُوصى به.
+يضبط هذا الأمر خادم MCP ويدمج الخطافات المضمّنة في إعدادات مستخدم Claude Code. عندما لا يكون `CLAUDE_CONFIG_DIR` مضبوطًا أو تكون قيمته فارغة أو مؤلفة من مسافات بيضاء فقط، يستخدم `~/.claude.json` لإعدادات MCP و`~/.claude/settings.json` للخطافات. تُستخدم قيم الأدلة الأخرى كما هي تمامًا، بما في ذلك المسافات البيضاء في البداية والنهاية. لاستخدام دليل مخصص، اضبط `CLAUDE_CONFIG_DIR` على القيمة غير الفارغة نفسها عند تشغيل هذا الأمر وClaude Code؛ وعندها يكون الملفان `$CLAUDE_CONFIG_DIR/.claude.json` و`$CLAUDE_CONFIG_DIR/settings.json`، على الترتيب. يجب أن يتلقى Claude Code هذه القيمة في بيئة تشغيله، حتى إذا قرأها الموصل من ملف `.env` الخاص بـ AgentMemory. أنشئ الدليل المخصص قبل تشغيل هذا الأمر؛ وإلا فسيتجاوز الموصل Claude Code باعتباره غير مكتشف. إذا كانت قيمة المتغير في بيئة shell مؤلفة من مسافات بيضاء فقط، فألغِ تعيين `CLAUDE_CONFIG_DIR` قبل تشغيل Claude Code ليستخدم الإعدادات الافتراضية أيضًا. استخدم مسارًا مطلقًا. تُحل المسارات النسبية انطلاقًا من دليل العمل، لذا يجب تشغيل الأمرين من الدليل نفسه.
+
+تستخدم أوامر الخطافات مسارات مطلقة إلى دليل `plugin/` المضمّن في الحزمة المثبّتة. أعد تشغيل الأمر بعد ترقية agentmemory لتحديث تلك المسارات. تُحفظ إدخالات المستخدم في ملفات الإعدادات؛ ولا تُستبدل إلا إدخالات agentmemory السابقة. يظل استخدام `/plugin install` هو النهج الموصى به.
بالنسبة للنشر عن بُعد أو المحمي، شغّل Claude Code مع ضبط `AGENTMEMORY_URL` و`AGENTMEMORY_SECRET`. تُمرّر الإضافة كلتا القيمتين إلى خادم MCP المُضمَّن بها؛ وعندما يكون `AGENTMEMORY_URL` فارغًا، يستخدم وسيط MCP (shim) عنوان `http://localhost:3111`.
### Codex CLI (منصة إضافات Codex)
@@ -567,7 +569,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
الدليل الكامل: [`integrations/hermes/`](../integrations/hermes/)
@@ -665,7 +667,7 @@ npm install && npm run build && npm start
### Windows
-يعمل agentmemory على Windows 10/11. يتبع WSL2 مسار Linux ويمكنه تثبيت المحرك المثبّت تلقائيًا. يتطلب Windows الأصلي تثبيت ملف iii-engine 0.25.0 المثبّت يدويًا؛ نزّل الأرشيف المطابق من [صفحة إصدار iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0)، وتحقق من بصمته، وضع `iii.exe` على `PATH` (مثل `%USERPROFILE%\.local\bin\iii.exe`). لا يستخرج CLI ملف ZIP الخاص بـ Windows تلقائيًا.
+يعمل agentmemory على Windows 10/11. يتبع WSL2 مسار Linux ويمكنه تثبيت المحرك المثبّت تلقائيًا. يتطلب Windows الأصلي تثبيت ملف iii-engine 0.25.1 المثبّت يدويًا؛ نزّل الأرشيف المطابق من [صفحة إصدار iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1)، وتحقق من بصمته، وضع `iii.exe` على `PATH` (مثل `%USERPROFILE%\.local\bin\iii.exe`). لا يستخرج CLI ملف ZIP الخاص بـ Windows تلقائيًا.
لا يدعم الربط الآلي لـ MCP على Windows الأصلي إلا `agentmemory connect copilot-cli`. أما وكلاء Windows الأصليون الآخرون، فاستخدم كتلة MCP اليدوية من [وكلاء آخرون](#other-agents). شغّل `connect` داخل WSL فقط عندما يكون الوكيل المستهدف مثبتًا في بيئة WSL نفسها.
@@ -1161,7 +1163,7 @@ EMBEDDING_PROVIDER=local
-146 نقطة نهاية على المنفذ `3111`. ترتبط REST API بـ `127.0.0.1` افتراضيًا. تتطلب نقاط النهاية المحمية ترويسة `Authorization: Bearer `، وتتطلب نقاط نهاية مزامنة mesh ضبط `AGENTMEMORY_SECRET` صريحًا على كلا الطرفين.
+147 نقطة نهاية على المنفذ `3111`. ترتبط REST API بـ `127.0.0.1` افتراضيًا. تتطلب نقاط النهاية المحمية ترويسة `Authorization: Bearer `، وتتطلب نقاط نهاية مزامنة mesh ضبط `AGENTMEMORY_SECRET` صريحًا على كلا الطرفين.
**المصادقة مُفعّلة افتراضيًا.** إذا لم يُضبط `AGENTMEMORY_SECRET`، ينشئ CLI عند التشغيل الأول سرًا عشوائيًا في `~/.agentmemory/secret` بصلاحيات `0600` وينسخه أيضًا إلى مجلد البيانات المحدد. يقرأ كل عميل مضمّن هذا السر عند الاتصال بخادم محلي: CLI والعارض والخطافات تحت `plugin/scripts` وخادم MCP ووسيط `@agentmemory/mcp` والإعدادات التي يكتبها `agentmemory connect` وتكاملات OpenCode وPi وOpenClaw وHermes ومراقب نظام الملفات المضمّنة. لا يُرسل السر المحفوظ إلا إلى عناوين loopback (`localhost` و`127.0.0.0/8` و`::1`). وتكون الأولوية دائمًا لقيمة `AGENTMEMORY_SECRET` الصريحة، كما يجب ضبط السر في بيئة العملاء البعيدين. تنشئ عمليات الاستضافة الذاتية عبر Docker من المستودع ونقاط دخول [`deploy/`](../deploy/) سرها وتصدّره. لاستدعاء API يدويًا:
@@ -1242,7 +1244,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.bn-BD.md b/READMEs/README.bn-BD.md
index 8a85ba1375..c878a5d8c8 100644
--- a/READMEs/README.bn-BD.md
+++ b/READMEs/README.bn-BD.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### প্লাগইন ইনস্টল ছাড়া Claude Code (MCP-স্ট্যান্ডঅ্যালোন পাথ)
-আপনি `/plugin install` ব্যবহার না করে সরাসরি `~/.claude.json`-এর মাধ্যমে agentmemory-র MCP সার্ভার ওয়্যার করলে, Claude Code কখনো `${CLAUDE_PLUGIN_ROOT}` রিজলভ করে না এবং আপনাকে `~/.claude/settings.json`-এ হুক স্ক্রিপ্টগুলো অ্যাবসোলিউট পাথে পয়েন্ট করতে হয়। সেই পাথগুলোতে সাধারণত agentmemory-র ভার্সন এমবেড থাকে (যেমন `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), তাই পরের আপগ্রেড নিঃশব্দে প্রতিটি হুক ভেঙে দেয়।
+আপনি `/plugin install` ব্যবহার না করে সরাসরি `~/.claude.json` (ডিফল্ট পথ)-এর মাধ্যমে agentmemory-র MCP সার্ভার ওয়্যার করলে, Claude Code কখনো `${CLAUDE_PLUGIN_ROOT}` রিজলভ করে না এবং আপনাকে `~/.claude/settings.json` (ডিফল্ট পথ)-এ হুক স্ক্রিপ্টগুলো অ্যাবসোলিউট পাথে পয়েন্ট করতে হয়। সেই পাথগুলোতে সাধারণত agentmemory-র ভার্সন এমবেড থাকে (যেমন `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), তাই পরের আপগ্রেড নিঃশব্দে প্রতিটি হুক ভেঙে দেয়।
ওয়ার্কঅ্যারাউন্ড:
@@ -452,7 +452,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-এটি একই হুক কমান্ডগুলো `~/.claude/settings.json`-এ মার্জ করে, বর্তমানে ইনস্টল করা `@agentmemory/agentmemory` প্যাকেজের বান্ডলড `plugin/` ডিরেক্টরির অ্যাবসোলিউট পাথ দিয়ে। পাথ রিফ্রেশ করতে agentmemory আপগ্রেড করার পর কমান্ডটি আবার চালান। একই ফাইলের ইউজার এন্ট্রিগুলো রক্ষিত থাকে; শুধু আগের agentmemory এন্ট্রিগুলো রিপ্লেস হয়। `/plugin install` পাথটি এখনও সুপারিশকৃত পদ্ধতি।
+এই কমান্ড MCP সার্ভার কনফিগার করে এবং সঙ্গে থাকা hook-গুলো Claude Code-এর ব্যবহারকারী কনফিগারেশনে যুক্ত করে। `CLAUDE_CONFIG_DIR` সেট করা না থাকলে, খালি থাকলে বা শুধু ফাঁকা অক্ষর থাকলে, এটি MCP-এর জন্য `~/.claude.json` এবং hook-এর জন্য `~/.claude/settings.json` ব্যবহার করে। অন্য ডিরেক্টরি মানগুলো শুরু ও শেষের ফাঁকা স্থানসহ হুবহু ব্যবহার করা হয়। কাস্টম ডিরেক্টরি ব্যবহার করতে এই কমান্ড এবং Claude Code উভয়ের জন্য `CLAUDE_CONFIG_DIR`-এ একই খালি নয় এমন মান সেট করুন; তখন ফাইল দুটি হবে যথাক্রমে `$CLAUDE_CONFIG_DIR/.claude.json` এবং `$CLAUDE_CONFIG_DIR/settings.json`। কানেক্টর AgentMemory-এর `.env` থেকে মানটি পড়লেও Claude Code চালু করার এনভায়রনমেন্টে এই মান থাকতে হবে। এই কমান্ড চালানোর আগে কাস্টম ডিরেক্টরি তৈরি করুন; না থাকলে কানেক্টর Claude Code-কে শনাক্ত করতে না পেরে এড়িয়ে যাবে। Shell-এর মানে শুধু ফাঁকা অক্ষর থাকলে, Claude Code চালুর আগে `CLAUDE_CONFIG_DIR` আনসেট করুন, যাতে সেটিও ডিফল্ট প্রোফাইল ব্যবহার করে। একটি পরম পথ ব্যবহার করুন। আপেক্ষিক পথ কর্মরত ডিরেক্টরির ভিত্তিতে নির্ধারিত হয়, তাই উভয় কমান্ড একই ডিরেক্টরি থেকে চালাতে হবে।
+
+Hook কমান্ডগুলো ইনস্টল করা প্যাকেজের সঙ্গে থাকা `plugin/` ডিরেক্টরির অ্যাবসোলিউট পথ ব্যবহার করে। agentmemory আপগ্রেড করার পরে পথগুলো হালনাগাদ করতে কমান্ডটি আবার চালান। কনফিগারেশন ফাইলে ব্যবহারকারীর এন্ট্রিগুলো সংরক্ষিত থাকে; শুধু আগের agentmemory এন্ট্রিগুলো প্রতিস্থাপিত হয়। `/plugin install` ব্যবহার করাই সুপারিশকৃত পদ্ধতি।
রিমোট বা প্রোটেক্টেড ডিপ্লয়মেন্টের জন্য, `AGENTMEMORY_URL` এবং `AGENTMEMORY_SECRET` সেট করে Claude Code লঞ্চ করুন। প্লাগইন দুটি ভ্যালুই তার বান্ডলড MCP সার্ভারে পাস করে; `AGENTMEMORY_URL` খালি থাকলে, MCP শিম `http://localhost:3111` ব্যবহার করে।
### Codex CLI (Codex প্লাগইন প্ল্যাটফর্ম)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
সম্পূর্ণ গাইড: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory Windows 10/11-এ চলে। WSL2 Linux-এর পথ অনুসরণ করে এবং পিন করা engine স্বয়ংক্রিয়ভাবে ইনস্টল করতে পারে। নেটিভ Windows-এর জন্য পিন করা iii-engine 0.25.0 বাইনারি ম্যানুয়ালি ইনস্টল করতে হবে; [iii 0.25.0 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) থেকে মিলে যাওয়া archive ডাউনলোড করে checksum যাচাই করুন, তারপর `iii.exe` `PATH`-এ রাখুন (যেমন `%USERPROFILE%\.local\bin\iii.exe`)। CLI Windows ZIP স্বয়ংক্রিয়ভাবে extract করে না।
+agentmemory Windows 10/11-এ চলে। WSL2 Linux-এর পথ অনুসরণ করে এবং পিন করা engine স্বয়ংক্রিয়ভাবে ইনস্টল করতে পারে। নেটিভ Windows-এর জন্য পিন করা iii-engine 0.25.1 বাইনারি ম্যানুয়ালি ইনস্টল করতে হবে; [iii 0.25.1 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) থেকে মিলে যাওয়া archive ডাউনলোড করে checksum যাচাই করুন, তারপর `iii.exe` `PATH`-এ রাখুন (যেমন `%USERPROFILE%\.local\bin\iii.exe`)। CLI Windows ZIP স্বয়ংক্রিয়ভাবে extract করে না।
নেটিভ Windows-এ স্বয়ংক্রিয় MCP wiring কেবল `agentmemory connect copilot-cli` সাপোর্ট করে। অন্য নেটিভ Windows এজেন্টের জন্য [Other agents](#other-agents) থেকে ম্যানুয়াল MCP block ব্যবহার করুন। লক্ষ্য এজেন্টটি একই WSL পরিবেশে ইনস্টল থাকলেই কেবল WSL-এর ভিতরে `connect` চালান।
@@ -1174,7 +1176,7 @@ EMBEDDING_PROVIDER=local
-`3111` পোর্টে 146 এন্ডপয়েন্ট। REST API ডিফল্টভাবে `127.0.0.1`-এ বাইন্ড করে। প্রোটেক্টেড এন্ডপয়েন্টে `Authorization: Bearer ` লাগে, এবং mesh sync এন্ডপয়েন্টে দুই পিয়ারেই স্পষ্টভাবে সেট করা `AGENTMEMORY_SECRET` লাগে।
+`3111` পোর্টে 147 এন্ডপয়েন্ট। REST API ডিফল্টভাবে `127.0.0.1`-এ বাইন্ড করে। প্রোটেক্টেড এন্ডপয়েন্টে `Authorization: Bearer ` লাগে, এবং mesh sync এন্ডপয়েন্টে দুই পিয়ারেই স্পষ্টভাবে সেট করা `AGENTMEMORY_SECRET` লাগে।
প্রমাণীকরণ ডিফল্টভাবে চালু। `AGENTMEMORY_SECRET` নির্ধারিত না থাকলে CLI প্রথমবার একটি random secret `~/.agentmemory/secret`-এ রাখে এবং নির্বাচিত ডেটা ডিরেক্টরির `secret`-এ কপি করে; অনুমতি `0600`। সঙ্গে থাকা ক্লায়েন্ট লোকাল সংযোগে মূল ফাইলটিকে অগ্রাধিকার দেয় এবং সংরক্ষিত secret শুধু loopback URL-এ পাঠায়। স্পষ্ট `AGENTMEMORY_SECRET` অগ্রাধিকার পায়; রিমোট ক্লায়েন্টকে environment-এ সেট করতে হয়। Docker নিজস্ব secret তৈরি করে।
@@ -1255,7 +1257,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.cs-CZ.md b/READMEs/README.cs-CZ.md
index 6733e9778b..05d3df1055 100644
--- a/READMEs/README.cs-CZ.md
+++ b/READMEs/README.cs-CZ.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code bez instalace pluginu (cesta MCP-standalone)
-Pokud zapojíte server MCP agentmemory přímo přes `~/.claude.json` místo použití `/plugin install`, Claude Code nikdy nevyřeší `${CLAUDE_PLUGIN_ROOT}` a musíte nasměrovat skripty hooks na absolutní cesty v `~/.claude/settings.json`. Tyto cesty typicky obsahují verzi agentmemory (např. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), takže další upgrade tiše rozbije všechny hooks.
+Pokud zapojíte server MCP agentmemory přímo přes `~/.claude.json` (výchozí cesta) místo použití `/plugin install`, Claude Code nikdy nevyřeší `${CLAUDE_PLUGIN_ROOT}` a musíte nasměrovat skripty hooks na absolutní cesty v `~/.claude/settings.json` (výchozí cesta). Tyto cesty typicky obsahují verzi agentmemory (např. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), takže další upgrade tiše rozbije všechny hooks.
Řešení:
@@ -454,7 +454,9 @@ Pokud zapojíte server MCP agentmemory přímo přes `~/.claude.json` místo pou
agentmemory connect claude-code --with-hooks
```
-Toto sloučí stejné příkazy hooks do `~/.claude/settings.json` s absolutními cestami vyřešenými na balíčený adresář `plugin/` aktuálně nainstalovaného balíčku `@agentmemory/agentmemory`. Po upgradu agentmemory příkaz spusťte znovu, aby se cesty obnovily. Uživatelské položky ve stejném souboru zůstanou zachovány; nahrazeny jsou pouze předchozí položky agentmemory. Doporučovaným přístupem zůstává cesta přes `/plugin install`.
+Tento příkaz nastaví server MCP a sloučí přibalené hooky do uživatelské konfigurace Claude Code. Pokud `CLAUDE_CONFIG_DIR` není nastavena, je prázdná nebo obsahuje pouze bílé znaky, použije pro MCP soubor `~/.claude.json` a pro hooky `~/.claude/settings.json`. Ostatní hodnoty adresáře se používají přesně tak, jak byly zadány, včetně úvodních a koncových bílých znaků. Chcete-li použít vlastní adresář, nastavte pro tento příkaz i Claude Code stejnou neprázdnou hodnotu `CLAUDE_CONFIG_DIR`; MCP pak použije `$CLAUDE_CONFIG_DIR/.claude.json` a hooky `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code musí tuto hodnotu obdržet ve svém spouštěcím prostředí, i když ji konektor načítá ze souboru `.env` AgentMemory. Vlastní adresář vytvořte před spuštěním tohoto příkazu; jinak konektor Claude Code nerozpozná a přeskočí jej. Pokud hodnota v shellu obsahuje pouze bílé znaky, před spuštěním Claude Code zrušte nastavení `CLAUDE_CONFIG_DIR`, aby také použil výchozí profil. Použijte absolutní cestu. Relativní cesty se vyhodnocují vůči pracovnímu adresáři, takže oba příkazy musí být spuštěny ze stejného adresáře.
+
+Příkazy hooků používají absolutní cesty do adresáře `plugin/` přibaleného v nainstalovaném balíčku. Po aktualizaci agentmemory spusťte příkaz znovu, aby se tyto cesty obnovily. Uživatelské položky v konfiguračních souborech zůstanou zachovány; nahradí se pouze předchozí položky agentmemory. Doporučeným postupem zůstává `/plugin install`.
Pro vzdálená nebo chráněná nasazení spusťte Claude Code s nastaveným `AGENTMEMORY_URL` a `AGENTMEMORY_SECRET`. Plugin obě hodnoty předá svému zabalenému serveru MCP; když je `AGENTMEMORY_URL` prázdné, shim MCP použije `http://localhost:3111`.
### Codex CLI (platforma pluginů Codex)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Úplný návod: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory běží na Windows 10/11. WSL2 používá cestu pro Linux a může pinned engine nainstalovat automaticky. Nativní Windows vyžaduje ručně nainstalovanou binárku iii-engine v0.25.0; stáhněte odpovídající archiv ze [stránky vydání iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), ověřte kontrolní součet a umístěte `iii.exe` do `PATH` (například `%USERPROFILE%\.local\bin\iii.exe`). CLI ZIP pro Windows automaticky nerozbaluje.
+agentmemory běží na Windows 10/11. WSL2 používá cestu pro Linux a může pinned engine nainstalovat automaticky. Nativní Windows vyžaduje ručně nainstalovanou binárku iii-engine v0.25.1; stáhněte odpovídající archiv ze [stránky vydání iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), ověřte kontrolní součet a umístěte `iii.exe` do `PATH` (například `%USERPROFILE%\.local\bin\iii.exe`). CLI ZIP pro Windows automaticky nerozbaluje.
Automatizované zapojení MCP na nativním Windows podporuje pouze `agentmemory connect copilot-cli`. U ostatních nativních agentů použijte manuální blok MCP ze sekce [Další agenti](#other-agents). `connect` ve WSL spouštějte pouze tehdy, pokud je cílový agent nainstalován ve stejném prostředí WSL.
@@ -1160,7 +1162,7 @@ EMBEDDING_PROVIDER=local
-146 endpointů na portu `3111`. REST API se ve výchozím stavu váže na `127.0.0.1`. Chráněné endpointy vyžadují `Authorization: Bearer `, a endpointy pro mesh sync vyžadují explicitně nastavené `AGENTMEMORY_SECRET` na obou stranách.
+147 endpointů na portu `3111`. REST API se ve výchozím stavu váže na `127.0.0.1`. Chráněné endpointy vyžadují `Authorization: Bearer `, a endpointy pro mesh sync vyžadují explicitně nastavené `AGENTMEMORY_SECRET` na obou stranách.
**Autentizace je ve výchozím stavu zapnutá.** Pokud `AGENTMEMORY_SECRET` není nastaveno, CLI při prvním spuštění vygeneruje náhodný secret v `~/.agentmemory/secret` s oprávněním `0600` a zkopíruje jej také do vybraného datového adresáře. Všichni zabalení klienti jej načítají odtud při komunikaci s lokálním serverem: CLI, viewer, hooks v `plugin/scripts`, server MCP a shim `@agentmemory/mcp`, konfigurace zapsané pomocí `agentmemory connect` a zabalené integrace OpenCode, Pi, OpenClaw, Hermes a filesystem-watcher. Uložený secret se odesílá pouze na loopback URL (`localhost`, `127.0.0.0/8`, `::1`). Výslovně nastavená `AGENTMEMORY_SECRET` má vždy přednost a vzdálení klienti ji musí mít ve svém prostředí. Self-host nasazení Dockeru z repozitáře a entrypointy `deploy/` generují a exportují vlastní secret. Pro ruční volání API:
@@ -1241,7 +1243,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.da-DK.md b/READMEs/README.da-DK.md
index 986f11e1c0..62c1373564 100644
--- a/READMEs/README.da-DK.md
+++ b/READMEs/README.da-DK.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code uden plugin-installation (MCP-standalone-vej)
-Hvis du forbinder agentmemorys MCP-server via `~/.claude.json` direkte i stedet for at bruge `/plugin install`, opløser Claude Code aldrig `${CLAUDE_PLUGIN_ROOT}`, og du skal pege hook-scripts på absolutte paths i `~/.claude/settings.json`. Disse paths indeholder typisk agentmemory-versionen (f.eks. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så den næste opgradering stille og roligt bryder hver hook.
+Hvis du forbinder agentmemorys MCP-server via `~/.claude.json` (standardsti) direkte i stedet for at bruge `/plugin install`, opløser Claude Code aldrig `${CLAUDE_PLUGIN_ROOT}`, og du skal pege hook-scripts på absolutte paths i `~/.claude/settings.json` (standardsti). Disse paths indeholder typisk agentmemory-versionen (f.eks. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så den næste opgradering stille og roligt bryder hver hook.
Løsning:
@@ -449,7 +449,9 @@ Løsning:
agentmemory connect claude-code --with-hooks
```
-Dette sammenføjer de samme hook-kommandoer i `~/.claude/settings.json` med absolutte paths, der peger på den medfølgende `plugin/`-mappe i den aktuelt installerede `@agentmemory/agentmemory`-pakke. Kør kommandoen igen efter opgradering af agentmemory for at opdatere paths. Brugerens egne indgange i samme fil bevares; kun tidligere agentmemory-indgange udskiftes. At bruge `/plugin install`-vejen er stadig den anbefalede metode.
+Denne kommando konfigurerer MCP-serveren og fletter de medfølgende hooks ind i Claude Codes brugerkonfiguration. Hvis `CLAUDE_CONFIG_DIR` ikke er sat, er tom eller kun indeholder blanktegn, bruges `~/.claude.json` til MCP og `~/.claude/settings.json` til hooks. Andre mappeværdier bruges præcis som angivet, inklusive indledende og afsluttende blanktegn. Hvis du vil bruge en brugerdefineret mappe, skal `CLAUDE_CONFIG_DIR` have den samme ikke-tomme værdi for både denne kommando og Claude Code; filerne bliver da henholdsvis `$CLAUDE_CONFIG_DIR/.claude.json` og `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code skal modtage værdien i sit startmiljø, selv hvis connectoren læser den fra AgentMemorys `.env`. Opret den brugerdefinerede mappe, før du kører kommandoen; ellers springer connectoren Claude Code over, fordi det ikke bliver fundet. Hvis værdien i shellen kun indeholder blanktegn, skal du fjerne `CLAUDE_CONFIG_DIR` fra miljøet, før du starter Claude Code, så det også bruger standardprofilen. Brug en absolut sti. Relative stier fortolkes ud fra arbejdsmappen, så begge kommandoer skal køres fra samme mappe.
+
+Hook-kommandoerne bruger absolutte stier til den installerede pakkes medfølgende `plugin/`-mappe. Kør kommandoen igen efter en opgradering af agentmemory for at opdatere stierne. Brugerens egne indgange i konfigurationsfilerne bevares; kun tidligere agentmemory-indgange erstattes. Det anbefales fortsat at bruge `/plugin install`.
Til eksterne eller beskyttede deployments, start Claude Code med `AGENTMEMORY_URL` og `AGENTMEMORY_SECRET` sat. Pluginet sender begge værdier videre til sin medfølgende MCP-server; når `AGENTMEMORY_URL` er tom, bruger MCP-shimmen `http://localhost:3111`.
### Codex CLI (Codex-plugin-platform)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Fuld guide: [`integrations/hermes/`](../integrations/hermes/)
@@ -655,7 +657,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory kører på Windows 10/11. WSL2 følger Linux-vejen og kan installere den fastlåste engine automatisk. Native Windows kræver, at den fastlåste iii-engine v0.25.0-binary installeres manuelt; download det tilsvarende arkiv fra [iii v0.25.0-udgivelsessiden](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verificér checksum, og placér `iii.exe` på `PATH` (for eksempel `%USERPROFILE%\.local\bin\iii.exe`). CLI’en pakker ikke Windows-ZIP’en ud automatisk.
+agentmemory kører på Windows 10/11. WSL2 følger Linux-vejen og kan installere den fastlåste engine automatisk. Native Windows kræver, at den fastlåste iii-engine v0.25.1-binary installeres manuelt; download det tilsvarende arkiv fra [iii v0.25.1-udgivelsessiden](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verificér checksum, og placér `iii.exe` på `PATH` (for eksempel `%USERPROFILE%\.local\bin\iii.exe`). CLI’en pakker ikke Windows-ZIP’en ud automatisk.
Automatisk MCP-opsætning på native Windows understøtter kun `agentmemory connect copilot-cli`. Brug den manuelle MCP-blok fra [Andre agenter](#other-agents) til andre native Windows-agenter. Kør kun `connect` i WSL, hvis målagenten er installeret i samme WSL-miljø.
@@ -1168,7 +1170,7 @@ Den fulde reference er [`.env.example`](../.env.example) med legitimationsoplysn
-146 endpoints på port `3111`. REST API'et binder til `127.0.0.1` som standard. Beskyttede endpoints kræver `Authorization: Bearer `, og mesh-sync-endpoints kræver en eksplicit sat `AGENTMEMORY_SECRET` på begge peers.
+147 endpoints på port `3111`. REST API'et binder til `127.0.0.1` som standard. Beskyttede endpoints kræver `Authorization: Bearer `, og mesh-sync-endpoints kræver en eksplicit sat `AGENTMEMORY_SECRET` på begge peers.
**Autentificering er slået til som standard.** Hvis `AGENTMEMORY_SECRET` hverken er sat i shellen eller i `~/.agentmemory/.env`, opretter CLI’en en tilfældig hemmelighed ved første start i `~/.agentmemory/secret` og en kopi med navnet `secret` i den valgte datamappe, med filtilstanden `0600`. Alle medfølgende klienter læser den derfra, når de taler med en lokal server: CLI’en, viewer, hooks under `plugin/scripts`, MCP-serveren og `@agentmemory/mcp`-shimmen, konfigurationerne skrevet af `agentmemory connect`, og de medfølgende OpenCode-, Pi-, OpenClaw-, Hermes- og filesystem-watcher-integrationer. Den lagrede secret sendes kun til loopback-URL’er (`localhost`, `127.0.0.0/8`, `::1`). En eksplicit `AGENTMEMORY_SECRET` vinder altid, og eksterne klienter skal have den i deres miljø. Docker-self-hosting fra repositoryet og `deploy/`-entrypoints genererer og eksporterer deres egen secret. Sådan kaldes API’et manuelt:
@@ -1249,7 +1251,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.de-DE.md b/READMEs/README.de-DE.md
index 7a7aee598b..60cbd1df16 100644
--- a/READMEs/README.de-DE.md
+++ b/READMEs/README.de-DE.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -439,7 +439,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code ohne Plugin-Installation (MCP-Standalone-Pfad)
-Wenn Sie den MCP-Server von agentmemory direkt über `~/.claude.json` verdrahten anstatt über `/plugin install`, löst Claude Code `${CLAUDE_PLUGIN_ROOT}` niemals auf, und Sie müssen Hook-Skripte in `~/.claude/settings.json` auf absolute Pfade zeigen lassen. Diese Pfade enthalten typischerweise die agentmemory-Version (z. B. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), sodass das nächste Upgrade jeden Hook stillschweigend bricht.
+Wenn Sie den MCP-Server von agentmemory direkt über `~/.claude.json` (Standardpfad) verdrahten anstatt über `/plugin install`, löst Claude Code `${CLAUDE_PLUGIN_ROOT}` niemals auf, und Sie müssen Hook-Skripte in `~/.claude/settings.json` (Standardpfad) auf absolute Pfade zeigen lassen. Diese Pfade enthalten typischerweise die agentmemory-Version (z. B. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), sodass das nächste Upgrade jeden Hook stillschweigend bricht.
Workaround:
@@ -447,7 +447,9 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-Das mischt dieselben Hook-Befehle in `~/.claude/settings.json` ein, mit absoluten Pfaden, die in das mitgelieferte `plugin/`-Verzeichnis des aktuell installierten `@agentmemory/agentmemory`-Pakets auflösen. Führen Sie den Befehl nach einem agentmemory-Upgrade erneut aus, um die Pfade zu aktualisieren. Eigene Einträge in derselben Datei bleiben erhalten; nur frühere agentmemory-Einträge werden ersetzt. Den `/plugin install`-Pfad zu nutzen, bleibt der empfohlene Ansatz.
+Dieser Befehl konfiguriert den MCP-Server und fügt die mitgelieferten Hooks zur Benutzerkonfiguration von Claude Code hinzu. Wenn `CLAUDE_CONFIG_DIR` nicht gesetzt oder leer ist oder nur Leerraum enthält, verwendet er `~/.claude.json` für MCP und `~/.claude/settings.json` für Hooks. Andere Verzeichniswerte werden unverändert verwendet, einschließlich Leerraum am Anfang und Ende. Für ein benutzerdefiniertes Verzeichnis muss `CLAUDE_CONFIG_DIR` für diesen Befehl und Claude Code denselben nicht leeren Wert haben; die Dateien sind dann `$CLAUDE_CONFIG_DIR/.claude.json` für MCP und `$CLAUDE_CONFIG_DIR/settings.json` für Hooks. Claude Code muss diesen Wert in seiner Startumgebung erhalten, auch wenn der Connector ihn aus der `.env` von AgentMemory liest. Erstellen Sie das benutzerdefinierte Verzeichnis vor dem Ausführen dieses Befehls; andernfalls wird Claude Code als nicht erkannt übersprungen. Wenn der Wert in der Shell nur Leerraum enthält, entfernen Sie `CLAUDE_CONFIG_DIR` vor dem Start von Claude Code aus der Umgebung, damit auch Claude Code das Standardprofil verwendet. Verwende einen absoluten Pfad. Relative Pfade werden vom Arbeitsverzeichnis aus aufgelöst, daher müssen beide Befehle im selben Verzeichnis ausgeführt werden.
+
+Die Hook-Befehle verwenden absolute Pfade zum mitgelieferten Verzeichnis `plugin/` des installierten Pakets. Führen Sie den Befehl nach einem Upgrade von agentmemory erneut aus, um diese Pfade zu aktualisieren. Benutzereinträge in den Konfigurationsdateien bleiben erhalten; nur bisherige agentmemory-Einträge werden ersetzt. Die Verwendung von `/plugin install` bleibt der empfohlene Weg.
Für entfernte oder geschützte Deployments starten Sie Claude Code mit gesetztem `AGENTMEMORY_URL` und `AGENTMEMORY_SECRET`. Das Plugin reicht beide Werte an seinen mitgelieferten MCP-Server weiter; ist `AGENTMEMORY_URL` leer, verwendet das MCP-Shim `http://localhost:3111`.
### Codex CLI (Codex-Plugin-Plattform)
@@ -556,7 +558,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Vollständiger Leitfaden: [`integrations/hermes/`](../integrations/hermes/)
@@ -653,7 +655,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory läuft unter Windows 10/11. WSL2 folgt dem Linux-Pfad und kann die gepinnte Engine automatisch installieren. Unter nativem Windows muss das gepinnte iii-engine-Binary v0.25.0 manuell installiert werden: Laden Sie das passende Archiv von der [iii-v0.25.0-Release-Seite](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) herunter, prüfen Sie die Prüfsumme und legen Sie `iii.exe` auf den `PATH` (zum Beispiel `%USERPROFILE%\.local\bin\iii.exe`). Die CLI entpackt das Windows-ZIP nicht automatisch.
+agentmemory läuft unter Windows 10/11. WSL2 folgt dem Linux-Pfad und kann die gepinnte Engine automatisch installieren. Unter nativem Windows muss das gepinnte iii-engine-Binary v0.25.1 manuell installiert werden: Laden Sie das passende Archiv von der [iii-v0.25.1-Release-Seite](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) herunter, prüfen Sie die Prüfsumme und legen Sie `iii.exe` auf den `PATH` (zum Beispiel `%USERPROFILE%\.local\bin\iii.exe`). Die CLI entpackt das Windows-ZIP nicht automatisch.
Die automatisierte MCP-Verdrahtung unter nativem Windows unterstützt nur `agentmemory connect copilot-cli`. Für andere native Windows-Agenten verwenden Sie den manuellen MCP-Block unter [Andere Agenten](#other-agents). Führen Sie `connect` in WSL nur aus, wenn der Ziel-Agent in derselben WSL-Umgebung installiert ist.
@@ -1166,7 +1168,7 @@ Die vollständige Referenz steht in [`.env.example`](../.env.example), einschlie
-146 Endpunkte auf Port `3111`. Die REST API bindet sich standardmäßig an `127.0.0.1`. Geschützte Endpunkte verlangen `Authorization: Bearer `, und Mesh-Sync-Endpunkte erfordern ein explizit gesetztes `AGENTMEMORY_SECRET` auf beiden Peers.
+147 Endpunkte auf Port `3111`. Die REST API bindet sich standardmäßig an `127.0.0.1`. Geschützte Endpunkte verlangen `Authorization: Bearer `, und Mesh-Sync-Endpunkte erfordern ein explizit gesetztes `AGENTMEMORY_SECRET` auf beiden Peers.
**Authentifizierung ist standardmäßig aktiv.** Wenn `AGENTMEMORY_SECRET` weder in der Shell noch in `~/.agentmemory/.env` gesetzt ist, erzeugt die CLI beim ersten Start ein zufälliges Secret unter `~/.agentmemory/secret` und spiegelt es als `secret` in das ausgewählte Datenverzeichnis, jeweils mit Dateimodus `0600`. Jeder mitgelieferte Client liest es von dort, wenn er mit einem lokalen Server spricht: die CLI, der Viewer, die Hooks unter `plugin/scripts`, der MCP-Server und das `@agentmemory/mcp`-Shim, die von `agentmemory connect` geschriebenen Konfigs sowie die mitgelieferten Integrationen für OpenCode, Pi, OpenClaw, Hermes und den Filesystem-Watcher. Das gespeicherte Secret wird nur an Loopback-URLs gesendet (`localhost`, `127.0.0.0/8`, `::1`). Ein explizites `AGENTMEMORY_SECRET` gewinnt immer, und Remote-Clients benötigen es trotzdem gesetzt. Docker und die `deploy/`-Entrypoints erzeugen und exportieren bereits ihr eigenes Secret. Um die API von Hand aufzurufen:
@@ -1247,7 +1249,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.el-GR.md b/READMEs/README.el-GR.md
index da436a98c1..4962170a4c 100644
--- a/READMEs/README.el-GR.md
+++ b/READMEs/README.el-GR.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code χωρίς εγκατάσταση plugin (αυτόνομη διαδρομή MCP)
-Αν συνδέσετε τον διακομιστή MCP του agentmemory μέσω του `~/.claude.json` απευθείας αντί να χρησιμοποιήσετε το `/plugin install`, το Claude Code δεν επιλύει ποτέ το `${CLAUDE_PLUGIN_ROOT}` και πρέπει να δείξετε τα scripts των hooks σε απόλυτες διαδρομές στο `~/.claude/settings.json`. Αυτές οι διαδρομές συνήθως ενσωματώνουν την έκδοση του agentmemory (π.χ. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), οπότε η επόμενη αναβάθμιση χαλάει σιωπηλά κάθε hook.
+Αν συνδέσετε τον διακομιστή MCP του agentmemory μέσω του `~/.claude.json` (προεπιλεγμένη διαδρομή) απευθείας αντί να χρησιμοποιήσετε το `/plugin install`, το Claude Code δεν επιλύει ποτέ το `${CLAUDE_PLUGIN_ROOT}` και πρέπει να δείξετε τα scripts των hooks σε απόλυτες διαδρομές στο `~/.claude/settings.json` (προεπιλεγμένη διαδρομή). Αυτές οι διαδρομές συνήθως ενσωματώνουν την έκδοση του agentmemory (π.χ. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), οπότε η επόμενη αναβάθμιση χαλάει σιωπηλά κάθε hook.
Λύση παράκαμψης:
@@ -454,7 +454,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-Αυτό συγχωνεύει τις ίδιες εντολές hook στο `~/.claude/settings.json` με απόλυτες διαδρομές που αναλύονται στον ενσωματωμένο κατάλογο `plugin/` του πακέτου `@agentmemory/agentmemory` που είναι τρέχουσα εγκατεστημένο. Εκτελέστε ξανά την εντολή μετά την αναβάθμιση του agentmemory για να ανανεωθούν οι διαδρομές. Οι καταχωρήσεις του χρήστη στο ίδιο αρχείο διατηρούνται· αντικαθίστανται μόνο οι προηγούμενες καταχωρήσεις του agentmemory. Η χρήση της διαδρομής `/plugin install` παραμένει η συνιστώμενη προσέγγιση.
+Αυτή η εντολή ρυθμίζει τον διακομιστή MCP και συγχωνεύει τα ενσωματωμένα hooks στη διαμόρφωση χρήστη του Claude Code. Αν το `CLAUDE_CONFIG_DIR` δεν έχει οριστεί, είναι κενό ή περιέχει μόνο κενούς χαρακτήρες, χρησιμοποιεί το `~/.claude.json` για το MCP και το `~/.claude/settings.json` για τα hooks. Οι υπόλοιπες τιμές καταλόγου χρησιμοποιούνται ακριβώς όπως δίνονται, μαζί με τυχόν κενούς χαρακτήρες στην αρχή και στο τέλος. Για προσαρμοσμένο κατάλογο, ορίστε την ίδια μη κενή τιμή του `CLAUDE_CONFIG_DIR` για αυτή την εντολή και το Claude Code, οπότε τα αρχεία θα είναι `$CLAUDE_CONFIG_DIR/.claude.json` και `$CLAUDE_CONFIG_DIR/settings.json`, αντίστοιχα. Το Claude Code πρέπει να λάβει αυτή την τιμή στο περιβάλλον εκκίνησής του, ακόμη και αν ο connector τη διαβάζει από το `.env` του AgentMemory. Δημιουργήστε τον προσαρμοσμένο κατάλογο πριν εκτελέσετε αυτή την εντολή, διαφορετικά ο connector παραλείπει το Claude Code επειδή δεν το εντοπίζει. Αν η τιμή στο shell περιέχει μόνο κενούς χαρακτήρες, καταργήστε το `CLAUDE_CONFIG_DIR` από το περιβάλλον πριν ξεκινήσετε το Claude Code, ώστε να χρησιμοποιήσει και αυτό το προεπιλεγμένο προφίλ. Χρησιμοποιήστε απόλυτη διαδρομή. Οι σχετικές διαδρομές επιλύονται ως προς τον κατάλογο εργασίας, οπότε και οι δύο εντολές πρέπει να εκτελούνται από τον ίδιο κατάλογο.
+
+Οι εντολές των hooks χρησιμοποιούν απόλυτες διαδρομές προς τον ενσωματωμένο κατάλογο `plugin/` του εγκατεστημένου πακέτου. Εκτελέστε ξανά την εντολή μετά την αναβάθμιση του agentmemory για να ενημερώσετε αυτές τις διαδρομές. Οι καταχωρίσεις χρήστη στα αρχεία διαμόρφωσης διατηρούνται και αντικαθίστανται μόνο οι προηγούμενες καταχωρίσεις του agentmemory. Η χρήση του `/plugin install` παραμένει η προτεινόμενη προσέγγιση.
Για απομακρυσμένες ή προστατευμένες αναπτύξεις, εκκινήστε το Claude Code με ρυθμισμένα τα `AGENTMEMORY_URL` και `AGENTMEMORY_SECRET`. Το plugin περνάει και τις δύο τιμές στον ενσωματωμένο διακομιστή MCP του· όταν το `AGENTMEMORY_URL` είναι άδειο, το MCP shim χρησιμοποιεί το `http://localhost:3111`.
### Codex CLI (πλατφόρμα plugin του Codex)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Πλήρης οδηγός: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-Το agentmemory εκτελείται σε Windows 10/11. Το WSL2 ακολουθεί τη διαδρομή Linux και μπορεί να εγκαταστήσει αυτόματα τον καρφιτσωμένο engine. Σε native Windows απαιτείται χειροκίνητη εγκατάσταση του καρφιτσωμένου binary iii-engine v0.25.0: κατεβάστε το αντίστοιχο archive από τη [σελίδα έκδοσης iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), επαληθεύστε το checksum και τοποθετήστε το `iii.exe` στο `PATH` (για παράδειγμα `%USERPROFILE%\.local\bin\iii.exe`). Το CLI δεν εξάγει αυτόματα το Windows ZIP.
+Το agentmemory εκτελείται σε Windows 10/11. Το WSL2 ακολουθεί τη διαδρομή Linux και μπορεί να εγκαταστήσει αυτόματα τον καρφιτσωμένο engine. Σε native Windows απαιτείται χειροκίνητη εγκατάσταση του καρφιτσωμένου binary iii-engine v0.25.1: κατεβάστε το αντίστοιχο archive από τη [σελίδα έκδοσης iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), επαληθεύστε το checksum και τοποθετήστε το `iii.exe` στο `PATH` (για παράδειγμα `%USERPROFILE%\.local\bin\iii.exe`). Το CLI δεν εξάγει αυτόματα το Windows ZIP.
Η αυτοματοποιημένη ρύθμιση MCP σε native Windows υποστηρίζει μόνο το `agentmemory connect copilot-cli`. Για άλλους native Windows agents, χρησιμοποιήστε το χειροκίνητο block MCP από τους [Άλλους agents](#other-agents). Εκτελέστε `connect` μέσα στο WSL μόνο αν ο agent-στόχος είναι εγκατεστημένος στο ίδιο περιβάλλον WSL.
@@ -1160,7 +1162,7 @@ EMBEDDING_PROVIDER=local
-146 endpoints στη θύρα `3111`. Το REST API συνδέεται στο `127.0.0.1` από προεπιλογή. Τα προστατευμένα endpoints απαιτούν `Authorization: Bearer `, και τα endpoints mesh sync απαιτούν ένα ρητά ρυθμισμένο `AGENTMEMORY_SECRET` και στους δύο peers.
+147 endpoints στη θύρα `3111`. Το REST API συνδέεται στο `127.0.0.1` από προεπιλογή. Τα προστατευμένα endpoints απαιτούν `Authorization: Bearer `, και τα endpoints mesh sync απαιτούν ένα ρητά ρυθμισμένο `AGENTMEMORY_SECRET` και στους δύο peers.
**Η πιστοποίηση είναι ενεργή από προεπιλογή.** Όταν δεν ορίζεται `AGENTMEMORY_SECRET`, στην πρώτη εκκίνηση το CLI δημιουργεί τυχαίο μυστικό στο `~/.agentmemory/secret` με δικαιώματα `0600` και το αντιγράφει και στον επιλεγμένο κατάλογο δεδομένων. Κάθε ενσωματωμένος client το διαβάζει από εκεί όταν μιλά με έναν τοπικό διακομιστή: το CLI, το viewer, τα hooks κάτω από το `plugin/scripts`, ο διακομιστής MCP και το shim `@agentmemory/mcp`, οι ρυθμίσεις που γράφει το `agentmemory connect`, και οι ενσωματωμένες ενσωματώσεις OpenCode, Pi, OpenClaw, Hermes, και filesystem-watcher. Το αποθηκευμένο secret αποστέλλεται μόνο σε loopback URLs (`localhost`, `127.0.0.0/8`, `::1`). Ένα ρητό `AGENTMEMORY_SECRET` υπερισχύει πάντα, και οι απομακρυσμένοι clients εξακολουθούν να το χρειάζονται ρυθμισμένο. Το Docker και τα entrypoints του `deploy/` δημιουργούν και εξάγουν ήδη το δικό τους secret. Για να καλέσετε το API χειροκίνητα:
@@ -1241,7 +1243,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.es-ES.md b/READMEs/README.es-ES.md
index 9a2add4427..71d33dbb10 100644
--- a/READMEs/README.es-ES.md
+++ b/READMEs/README.es-ES.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code sin instalar el plugin (ruta MCP standalone)
-Si conectas el servidor MCP de agentmemory directamente vía `~/.claude.json` en lugar de usar `/plugin install`, Claude Code nunca resuelve `${CLAUDE_PLUGIN_ROOT}` y tienes que apuntar los scripts de hook a rutas absolutas en `~/.claude/settings.json`. Esas rutas suelen incluir la versión de agentmemory (p. ej. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), por lo que la siguiente actualización rompe silenciosamente todos los hooks.
+Si conectas el servidor MCP de agentmemory directamente vía `~/.claude.json` (ruta predeterminada) en lugar de usar `/plugin install`, Claude Code nunca resuelve `${CLAUDE_PLUGIN_ROOT}` y tienes que apuntar los scripts de hook a rutas absolutas en `~/.claude/settings.json` (ruta predeterminada). Esas rutas suelen incluir la versión de agentmemory (p. ej. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), por lo que la siguiente actualización rompe silenciosamente todos los hooks.
Workaround:
@@ -449,7 +449,9 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-Esto fusiona los mismos comandos de hook en `~/.claude/settings.json` con rutas absolutas que apuntan al directorio `plugin/` empaquetado del paquete `@agentmemory/agentmemory` actualmente instalado. Vuelve a ejecutar el comando tras actualizar agentmemory para refrescar las rutas. Las entradas de usuario en el mismo fichero se preservan; solo se reemplazan las entradas previas de agentmemory. La ruta vía `/plugin install` sigue siendo la recomendada.
+Este comando configura el servidor MCP y fusiona los hooks incluidos en la configuración de usuario de Claude Code. Si `CLAUDE_CONFIG_DIR` no está definida, está vacía o contiene solo espacios en blanco, usa `~/.claude.json` para MCP y `~/.claude/settings.json` para los hooks. Los demás valores de directorio se usan tal como se proporcionan, incluidos los espacios en blanco iniciales y finales. Para usar un directorio personalizado, establece `CLAUDE_CONFIG_DIR` con el mismo valor no vacío para este comando y para Claude Code; los archivos serán entonces `$CLAUDE_CONFIG_DIR/.claude.json` y `$CLAUDE_CONFIG_DIR/settings.json`, respectivamente. Claude Code debe recibir este valor en su entorno de inicio, aunque el conector lo lea del archivo `.env` de AgentMemory. Crea el directorio personalizado antes de ejecutar este comando; de lo contrario, el conector omite Claude Code porque no lo detecta. Si el valor en el shell contiene solo espacios en blanco, elimina `CLAUDE_CONFIG_DIR` del entorno antes de iniciar Claude Code para que también use el perfil predeterminado. Usa una ruta absoluta. Las rutas relativas se resuelven desde el directorio de trabajo, por lo que ambos comandos deben ejecutarse desde el mismo directorio.
+
+Los comandos de los hooks usan rutas absolutas al directorio `plugin/` incluido en el paquete instalado. Vuelve a ejecutar el comando tras actualizar agentmemory para refrescar esas rutas. Las entradas de usuario en los archivos de configuración se conservan; solo se reemplazan las entradas previas de agentmemory. El uso de `/plugin install` sigue siendo la opción recomendada.
Para despliegues remotos o protegidos, lanza Claude Code con `AGENTMEMORY_URL` y `AGENTMEMORY_SECRET` definidos. El plugin pasa ambos valores a su servidor MCP empaquetado; cuando `AGENTMEMORY_URL` está vacío, el shim MCP usa `http://localhost:3111`.
### Codex CLI (plataforma de plugins Codex)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Guía completa: [`integrations/hermes/`](../integrations/hermes/)
@@ -655,7 +657,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory funciona en Windows 10/11. WSL2 sigue la ruta de Linux y puede instalar el motor fijado automáticamente. Windows nativo requiere instalar manualmente el binario fijado de iii-engine v0.25.0; descarga el archivo correspondiente desde la [página de la release iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verifica su checksum y coloca `iii.exe` en `PATH` (por ejemplo, `%USERPROFILE%\.local\bin\iii.exe`). La CLI no extrae automáticamente el ZIP de Windows.
+agentmemory funciona en Windows 10/11. WSL2 sigue la ruta de Linux y puede instalar el motor fijado automáticamente. Windows nativo requiere instalar manualmente el binario fijado de iii-engine v0.25.1; descarga el archivo correspondiente desde la [página de la release iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verifica su checksum y coloca `iii.exe` en `PATH` (por ejemplo, `%USERPROFILE%\.local\bin\iii.exe`). La CLI no extrae automáticamente el ZIP de Windows.
La conexión MCP automatizada en Windows nativo solo admite `agentmemory connect copilot-cli`. Para otros agentes nativos de Windows, usa el bloque MCP manual de [Otros agentes](#other-agents). Ejecuta `connect` dentro de WSL solo si el agente de destino está instalado en ese mismo entorno WSL.
@@ -1162,7 +1164,7 @@ La referencia completa está en [`.env.example`](../.env.example): credenciales,
-146 endpoints en el puerto `3111`. La REST API se enlaza a `127.0.0.1` por defecto. Los endpoints protegidos requieren `Authorization: Bearer `, y los endpoints de mesh sync requieren un `AGENTMEMORY_SECRET` definido explícitamente en ambos peers.
+147 endpoints en el puerto `3111`. La REST API se enlaza a `127.0.0.1` por defecto. Los endpoints protegidos requieren `Authorization: Bearer `, y los endpoints de mesh sync requieren un `AGENTMEMORY_SECRET` definido explícitamente en ambos peers.
**La autenticación está activada por defecto.** Si `AGENTMEMORY_SECRET` no está definida en la shell ni en `~/.agentmemory/.env`, la CLI genera un secreto aleatorio en el primer inicio en `~/.agentmemory/secret` y lo copia como `secret` en el directorio de datos seleccionado, con permisos `0600`. Todos los clientes incluidos lo leen desde allí al comunicarse con un servidor local: la CLI, el visor, los hooks de `plugin/scripts`, el servidor MCP y el shim `@agentmemory/mcp`, las configuraciones escritas por `agentmemory connect` y las integraciones incluidas de OpenCode, Pi, OpenClaw, Hermes y filesystem-watcher. El secreto guardado solo se envía a URL de loopback (`localhost`, `127.0.0.0/8`, `::1`). Un `AGENTMEMORY_SECRET` explícito siempre tiene prioridad, y los clientes remotos necesitan que el secreto esté definido en su entorno. Los despliegues Docker alojados por cuenta propia desde el repositorio y los entrypoints de `deploy/` generan y exportan su propio secreto. Para llamar a la API manualmente:
@@ -1243,7 +1245,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.fi-FI.md b/READMEs/README.fi-FI.md
index f0d7093a4f..175efd508c 100644
--- a/READMEs/README.fi-FI.md
+++ b/READMEs/README.fi-FI.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code ilman pluginin asennusta (itsenäinen MCP-reitti)
-Jos kytket agentmemoryn MCP-palvelimen tiedoston `~/.claude.json` kautta suoraan sen sijaan, että käyttäisit `/plugin install`-komentoa, Claude Code ei koskaan ratkaise muuttujaa `${CLAUDE_PLUGIN_ROOT}`, ja sinun on osoitettava hook-skriptit absoluuttisiin polkuihin tiedostossa `~/.claude/settings.json`. Nämä polut sisältävät tyypillisesti agentmemoryn versionumeron (esim. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), niin että seuraava päivitys hajottaa hiljaisesti kaikki hookit.
+Jos kytket agentmemoryn MCP-palvelimen tiedoston `~/.claude.json` (oletuspolku) kautta suoraan sen sijaan, että käyttäisit `/plugin install`-komentoa, Claude Code ei koskaan ratkaise muuttujaa `${CLAUDE_PLUGIN_ROOT}`, ja sinun on osoitettava hook-skriptit absoluuttisiin polkuihin tiedostossa `~/.claude/settings.json` (oletuspolku). Nämä polut sisältävät tyypillisesti agentmemoryn versionumeron (esim. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), niin että seuraava päivitys hajottaa hiljaisesti kaikki hookit.
Kiertotapa:
@@ -454,7 +454,9 @@ Kiertotapa:
agentmemory connect claude-code --with-hooks
```
-Tämä yhdistää samat hook-komennot tiedostoon `~/.claude/settings.json` absoluuttisilla poluilla, jotka osoittavat asennetun `@agentmemory/agentmemory`-paketin mukana tulevaan `plugin/`-hakemistoon. Aja komento uudelleen agentmemoryn päivityksen jälkeen päivittääksesi polut. Käyttäjän omat merkinnät samassa tiedostossa säilyvät; vain aiemmat agentmemory-merkinnät korvataan. `/plugin install`-reitti pysyy suositeltuna lähestymistapana.
+Tämä komento määrittää MCP-palvelimen ja yhdistää mukana tulevat hookit Claude Coden käyttäjäkohtaisiin asetuksiin. Jos `CLAUDE_CONFIG_DIR` on asettamatta, tyhjä tai sisältää vain tyhjiä merkkejä, se käyttää MCP:lle tiedostoa `~/.claude.json` ja hookeille tiedostoa `~/.claude/settings.json`. Muut hakemistopolut säilytetään täsmälleen annettuina, myös alun ja lopun tyhjät merkit mukaan lukien. Jos haluat käyttää omaa hakemistoa, aseta `CLAUDE_CONFIG_DIR` samaksi ei-tyhjäksi arvoksi sekä tälle komennolle että Claude Codelle; tiedostot ovat tällöin `$CLAUDE_CONFIG_DIR/.claude.json` MCP:lle ja `$CLAUDE_CONFIG_DIR/settings.json` hookeille. Claude Coden on saatava tämä arvo käynnistysympäristöstään, vaikka yhdistin lukisi sen AgentMemoryn `.env`-tiedostosta. Luo oma hakemisto ennen tämän komennon suorittamista; muuten yhdistin ohittaa Claude Coden, koska sitä ei tunnisteta. Jos shellin arvo sisältää vain tyhjiä merkkejä, poista `CLAUDE_CONFIG_DIR` ympäristöstä ennen Claude Coden käynnistämistä, jotta myös se käyttää oletusprofiilia. Käytä absoluuttista polkua. Suhteelliset polut tulkitaan työhakemiston perusteella, joten molemmat komennot on suoritettava samasta hakemistosta.
+
+Hook-komennot käyttävät absoluuttisia polkuja asennetun paketin mukana tulevaan `plugin/`-hakemistoon. Suorita komento uudelleen agentmemoryn päivityksen jälkeen, jotta polut päivittyvät. Käyttäjän omat merkinnät asetustiedostoissa säilytetään; vain aiemmat agentmemory-merkinnät korvataan. `/plugin install` on edelleen suositeltu tapa.
Etä- tai suojattuja käyttöönottoja varten käynnistä Claude Code `AGENTMEMORY_URL`- ja `AGENTMEMORY_SECRET`-muuttujat asetettuina. Plugin välittää molemmat arvot sen mukana tulevalle MCP-palvelimelle; kun `AGENTMEMORY_URL` on tyhjä, MCP-shim käyttää osoitetta `http://localhost:3111`.
### Codex CLI (Codexin plugin-alusta)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Vahvista toiminta komennolla `curl http://localhost:3111/agentmemory/health`. Avaa reaaliaikainen katseluohjelma osoitteessa http://localhost:3113. Syvempää kuuden hookin muistitarjoajaintegraatiota varten (kontekstin lisäys ennen LLM:ää, vuoron tallennus, MEMORY.md-peilaus ja järjestelmäkehotteen lohko) kopioi integrations/hermes agentmemory-repositoriosta polkuun ~/.hermes/plugins/agentmemory.
+Vahvista toiminta komennolla `curl http://localhost:3111/agentmemory/health`. Avaa reaaliaikainen katseluohjelma osoitteessa http://localhost:3113. Syvempää kuuden hookin muistitarjoajaintegraatiota varten (kontekstin lisäys ennen LLM:ää, vuoron tallennus, MEMORY.md-peilaus ja järjestelmäkehotteen lohko) kopioi integrations/hermes repositoriosta https://github.com/rohitg00/agentmemory polkuun ~/.hermes/plugins/agentmemory.
```
Täysi opas: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory toimii Windows 10/11:ssä. WSL2 noudattaa Linuxin polkua ja voi asentaa kiinnitetyn moottorin automaattisesti. Natiivi Windows vaatii iii-engine v0.25.0:n kiinnitetyn binäärin asentamisen käsin; lataa sopiva paketti [iii v0.25.0 -julkaisusivulta](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), tarkista sen tarkistussumma ja sijoita `iii.exe` `PATH`-polkuun (esimerkiksi `%USERPROFILE%\.local\bin\iii.exe`). CLI ei pura Windows-ZIP-pakettia automaattisesti.
+agentmemory toimii Windows 10/11:ssä. WSL2 noudattaa Linuxin polkua ja voi asentaa kiinnitetyn moottorin automaattisesti. Natiivi Windows vaatii iii-engine v0.25.1:n kiinnitetyn binäärin asentamisen käsin; lataa sopiva paketti [iii v0.25.1 -julkaisusivulta](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), tarkista sen tarkistussumma ja sijoita `iii.exe` `PATH`-polkuun (esimerkiksi `%USERPROFILE%\.local\bin\iii.exe`). CLI ei pura Windows-ZIP-pakettia automaattisesti.
Natiivin Windowsin automaattinen MCP-kytkentä tukee vain komentoa `agentmemory connect copilot-cli`. Muiden natiivien Windows-agenttien kanssa käytä manuaalista MCP-lohkoa kohdasta [Muut agentit](#other-agents). Suorita `connect` WSL:ssä vain, kun kohdeagentti on asennettu samaan WSL-ympäristöön.
@@ -1160,7 +1162,7 @@ Täydellinen [`.env.example`](../.env.example) kattaa palveluntarjoajat, tallenn
-146 endpointia portissa `3111`. REST-rajapinta sitoutuu oletuksena osoitteeseen `127.0.0.1`. Suojatut endpointit vaativat `Authorization: Bearer `, ja mesh-synkronointiendpointit vaativat nimenomaisesti asetetun `AGENTMEMORY_SECRET`-arvon molemmilla vertaisilla.
+147 endpointia portissa `3111`. REST-rajapinta sitoutuu oletuksena osoitteeseen `127.0.0.1`. Suojatut endpointit vaativat `Authorization: Bearer `, ja mesh-synkronointiendpointit vaativat nimenomaisesti asetetun `AGENTMEMORY_SECRET`-arvon molemmilla vertaisilla.
**Autentikointi on oletuksena päällä.** Jos `AGENTMEMORY_SECRET` puuttuu, CLI luo ensimmäisellä käynnistyksellä satunnaisen salaisuuden tiedostoon `~/.agentmemory/secret` oikeuksilla `0600` ja kopioi sen myös valittuun datahakemistoon. Kaikki mukana toimitetut asiakkaat lukevat salaisuuden sieltä käyttäessään paikallista palvelinta: CLI, katseluohjelma, `plugin/scripts`-hakemiston hookit, MCP-palvelin ja `@agentmemory/mcp`-shim, `agentmemory connect` -komennon luomat asetukset sekä mukana toimitetut OpenCode-, Pi-, OpenClaw-, Hermes- ja filesystem-watcher-integraatiot. Tallennettu salaisuus lähetetään vain loopback-osoitteisiin (`localhost`, `127.0.0.0/8`, `::1`). Nimenomainen `AGENTMEMORY_SECRET` voittaa aina, ja etäasiakkaiden on asetettava salaisuus ympäristöönsä. Repositorion Docker-itseylläpitokäyttöönotot ja `deploy/`-entrypointit luovat ja vievät oman salaisuutensa. Rajapinnan manuaalinen kutsu:
@@ -1241,7 +1243,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.fr-FR.md b/READMEs/README.fr-FR.md
index 60ed0f017a..c898e17a93 100644
--- a/READMEs/README.fr-FR.md
+++ b/READMEs/README.fr-FR.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code sans l'installation du plugin (chemin MCP-standalone)
-Si vous câblez le serveur MCP d'agentmemory via `~/.claude.json` directement plutôt qu'en utilisant `/plugin install`, Claude Code ne résout jamais `${CLAUDE_PLUGIN_ROOT}` et vous devez pointer les scripts de hooks vers des chemins absolus dans `~/.claude/settings.json`. Ces chemins embarquent typiquement la version d'agentmemory (par ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), donc la prochaine mise à niveau casse silencieusement chaque hook.
+Si vous câblez le serveur MCP d'agentmemory via `~/.claude.json` (chemin par défaut) directement plutôt qu'en utilisant `/plugin install`, Claude Code ne résout jamais `${CLAUDE_PLUGIN_ROOT}` et vous devez pointer les scripts de hooks vers des chemins absolus dans `~/.claude/settings.json` (chemin par défaut). Ces chemins embarquent typiquement la version d'agentmemory (par ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), donc la prochaine mise à niveau casse silencieusement chaque hook.
Solution de contournement :
@@ -449,7 +449,9 @@ Solution de contournement :
agentmemory connect claude-code --with-hooks
```
-Cela fusionne les mêmes commandes de hooks dans `~/.claude/settings.json` avec des chemins absolus résolus vers le répertoire `plugin/` embarqué dans le paquet `@agentmemory/agentmemory` actuellement installé. Relancez la commande après chaque mise à niveau d'agentmemory pour rafraîchir les chemins. Les entrées utilisateur dans le même fichier sont préservées ; seules les entrées agentmemory précédentes sont remplacées. Le chemin `/plugin install` reste l'approche recommandée.
+Cette commande configure le serveur MCP et fusionne les hooks inclus dans la configuration utilisateur de Claude Code. Si `CLAUDE_CONFIG_DIR` est absente, vide ou composée uniquement d’espaces, elle utilise `~/.claude.json` pour MCP et `~/.claude/settings.json` pour les hooks. Les autres valeurs de répertoire sont utilisées telles quelles, y compris les espaces en début et en fin de valeur. Pour utiliser un répertoire personnalisé, attribuez la même valeur non vide à `CLAUDE_CONFIG_DIR` pour cette commande et pour Claude Code ; les fichiers sont alors `$CLAUDE_CONFIG_DIR/.claude.json` et `$CLAUDE_CONFIG_DIR/settings.json`, respectivement. Claude Code doit recevoir cette valeur dans son environnement de lancement, même si le connecteur la lit dans le fichier `.env` d’AgentMemory. Créez le répertoire personnalisé avant d’exécuter cette commande ; sinon, Claude Code n’est pas détecté et le connecteur l’ignore. Si la valeur dans le shell ne contient que des espaces, supprimez `CLAUDE_CONFIG_DIR` de l’environnement avant de lancer Claude Code pour qu’il utilise aussi le profil par défaut. Utilisez un chemin absolu. Les chemins relatifs sont résolus à partir du répertoire de travail ; les deux commandes doivent donc être exécutées depuis le même répertoire.
+
+Les commandes des hooks utilisent des chemins absolus vers le répertoire `plugin/` inclus dans le paquet installé. Relancez la commande après la mise à niveau d’agentmemory pour actualiser ces chemins. Les entrées utilisateur dans les fichiers de configuration sont conservées ; seules les anciennes entrées d’agentmemory sont remplacées. L’utilisation de `/plugin install` reste l’approche recommandée.
Pour des déploiements distants ou protégés, lancez Claude Code avec `AGENTMEMORY_URL` et `AGENTMEMORY_SECRET` définis. Le plugin transmet les deux valeurs à son serveur MCP embarqué ; quand `AGENTMEMORY_URL` est vide, le shim MCP utilise `http://localhost:3111`.
### Codex CLI (plateforme de plugins Codex)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Guide complet : [`integrations/hermes/`](../integrations/hermes/)
@@ -655,7 +657,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory fonctionne sous Windows 10/11. WSL2 suit le parcours Linux et peut installer automatiquement le moteur épinglé. Sous Windows natif, installez manuellement le binaire iii-engine v0.25.0 épinglé : téléchargez l'archive correspondante depuis la [page de version iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), vérifiez son checksum et placez `iii.exe` dans `PATH` (par exemple `%USERPROFILE%\.local\bin\iii.exe`). La CLI n'extrait pas automatiquement le ZIP Windows.
+agentmemory fonctionne sous Windows 10/11. WSL2 suit le parcours Linux et peut installer automatiquement le moteur épinglé. Sous Windows natif, installez manuellement le binaire iii-engine v0.25.1 épinglé : téléchargez l'archive correspondante depuis la [page de version iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), vérifiez son checksum et placez `iii.exe` dans `PATH` (par exemple `%USERPROFILE%\.local\bin\iii.exe`). La CLI n'extrait pas automatiquement le ZIP Windows.
Sous Windows natif, le câblage MCP automatisé ne prend en charge que `agentmemory connect copilot-cli`. Pour les autres agents natifs Windows, utilisez le bloc MCP manuel de [Autres agents](#other-agents). Lancez `connect` dans WSL uniquement si l'agent cible est installé dans ce même environnement WSL.
@@ -1169,7 +1171,7 @@ La référence complète est [`.env.example`](../.env.example) : identifiants de
-146 endpoints sur le port `3111`. L'API REST se lie à `127.0.0.1` par défaut. Les endpoints protégés requièrent `Authorization: Bearer `, et les endpoints de mesh sync requièrent un `AGENTMEMORY_SECRET` explicitement défini sur les deux pairs.
+147 endpoints sur le port `3111`. L'API REST se lie à `127.0.0.1` par défaut. Les endpoints protégés requièrent `Authorization: Bearer `, et les endpoints de mesh sync requièrent un `AGENTMEMORY_SECRET` explicitement défini sur les deux pairs.
**L'authentification est activée par défaut.** Si `AGENTMEMORY_SECRET` n'est défini ni dans le shell ni dans `~/.agentmemory/.env`, la CLI génère un secret aléatoire au premier lancement dans `~/.agentmemory/secret` et en conserve une copie nommée `secret` dans le répertoire de données choisi, avec les permissions `0600`. Chaque client embarqué le lit depuis là quand il parle à un serveur local : la CLI, le visualiseur, les hooks sous `plugin/scripts`, le serveur MCP et le shim `@agentmemory/mcp`, les configs écrites par `agentmemory connect`, et les intégrations embarquées OpenCode, Pi, OpenClaw, Hermes et filesystem-watcher. Le secret stocké n'est envoyé qu'à des URLs loopback (`localhost`, `127.0.0.0/8`, `::1`). Un `AGENTMEMORY_SECRET` explicite prime toujours, et les clients distants en ont toujours besoin. Docker et les points d'entrée `deploy/` génèrent et exportent déjà leur propre secret. Pour appeler l'API à la main :
@@ -1250,7 +1252,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.he-IL.md b/READMEs/README.he-IL.md
index 580e9069b0..0586f40d7b 100644
--- a/READMEs/README.he-IL.md
+++ b/READMEs/README.he-IL.md
@@ -52,7 +52,7 @@
-
+
@@ -71,7 +71,7 @@
-
+
@@ -448,7 +448,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code בלי התקנת ה-plugin (נתיב MCP בלבד)
-אם אתם מחווטים את שרת ה-MCP של agentmemory ישירות דרך `~/.claude.json` במקום להשתמש ב-`/plugin install`, Claude Code לעולם לא פותר את `${CLAUDE_PLUGIN_ROOT}` ואתם חייבים להפנות את סקריפטי ה-hook ל-paths מוחלטים בתוך `~/.claude/settings.json`. ה-paths האלה בדרך כלל מטמיעים בתוכם את גרסת agentmemory (למשל `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), כך שהשדרוג הבא שובר בשקט כל hook.
+אם אתם מחווטים את שרת ה-MCP של agentmemory ישירות דרך `~/.claude.json` (נתיב ברירת המחדל) במקום להשתמש ב-`/plugin install`, Claude Code לעולם לא פותר את `${CLAUDE_PLUGIN_ROOT}` ואתם חייבים להפנות את סקריפטי ה-hook ל-paths מוחלטים בתוך `~/.claude/settings.json` (נתיב ברירת המחדל). ה-paths האלה בדרך כלל מטמיעים בתוכם את גרסת agentmemory (למשל `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), כך שהשדרוג הבא שובר בשקט כל hook.
פתרון עוקף:
@@ -456,7 +456,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-זה ממזג את אותן פקודות hook לתוך `~/.claude/settings.json` עם paths מוחלטים שנפתרים לתיקיית `plugin/` המצורפת של חבילת `@agentmemory/agentmemory` המותקנת כעת. יש להריץ את הפקודה מחדש אחרי שדרוג agentmemory כדי לרפרש את ה-paths. רשומות משתמש בקובץ עצמו נשמרות; רק רשומות agentmemory קודמות מוחלפות. השימוש בנתיב `/plugin install` נשאר הגישה המומלצת.
+הפקודה מגדירה את שרת ה-MCP וממזגת את ה-hooks המצורפים לתצורת המשתמש של Claude Code. אם `CLAUDE_CONFIG_DIR` אינו מוגדר, ריק או מכיל רק תווי רווח, היא משתמשת ב-`~/.claude.json` עבור MCP וב-`~/.claude/settings.json` עבור hooks. ערכי תיקייה אחרים משמשים בדיוק כפי שהוזנו, כולל תווי רווח בתחילת הערך ובסופו. כדי להשתמש בתיקייה מותאמת אישית, הגדירו את `CLAUDE_CONFIG_DIR` לאותו ערך שאינו ריק גם עבור הפקודה הזו וגם עבור Claude Code; הקבצים יהיו אז `$CLAUDE_CONFIG_DIR/.claude.json` ו-`$CLAUDE_CONFIG_DIR/settings.json`, בהתאמה. Claude Code חייב לקבל את הערך בסביבת ההפעלה שלו, גם אם המחבר קורא אותו מקובץ `.env` של AgentMemory. צרו את התיקייה המותאמת אישית לפני הפעלת הפקודה; אחרת המחבר מדלג על Claude Code כי הוא לא זוהה. אם הערך ב-shell מכיל רק תווי רווח, הסירו את `CLAUDE_CONFIG_DIR` מהסביבה לפני הפעלת Claude Code כדי שגם הוא ישתמש בפרופיל ברירת המחדל. השתמשו בנתיב מוחלט. נתיבים יחסיים מפוענחים ביחס לתיקיית העבודה, ולכן יש להריץ את שתי הפקודות מאותה תיקייה.
+
+פקודות ה-hook משתמשות בנתיבים מוחלטים לתיקיית `plugin/` המצורפת לחבילה המותקנת. הפעילו שוב את הפקודה לאחר שדרוג agentmemory כדי לרענן את הנתיבים. רשומות המשתמש בקובצי התצורה נשמרות; רק רשומות קודמות של agentmemory מוחלפות. השימוש ב-`/plugin install` נותר הדרך המומלצת.
ל-deployments מרוחקים או מוגנים, הפעילו את Claude Code עם `AGENTMEMORY_URL` ו-`AGENTMEMORY_SECRET` מוגדרים. ה-plugin מעביר את שני הערכים לשרת ה-MCP המצורף שלו; כש-`AGENTMEMORY_URL` ריק, ה-shim של MCP משתמש ב-`http://localhost:3111`.
### Codex CLI (פלטפורמת plugin של Codex)
@@ -567,7 +569,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
מדריך מלא: [`integrations/hermes/`](../integrations/hermes/)
@@ -665,7 +667,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory פועל ב-Windows 10/11. WSL2 פועל במסלול Linux ויכול להתקין את המנוע הנעוץ אוטומטית. ב-Windows מקורי יש להתקין ידנית את הבינארי הנעוץ iii-engine v0.25.0: הורידו את הארכיון המתאים מ-[דף ההפצה של iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), אמתו את ה-checksum והוסיפו את `iii.exe` ל-`PATH` (למשל `%USERPROFILE%\.local\bin\iii.exe`). ה-CLI אינו מחלץ אוטומטית את ZIP של Windows.
+agentmemory פועל ב-Windows 10/11. WSL2 פועל במסלול Linux ויכול להתקין את המנוע הנעוץ אוטומטית. ב-Windows מקורי יש להתקין ידנית את הבינארי הנעוץ iii-engine v0.25.1: הורידו את הארכיון המתאים מ-[דף ההפצה של iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), אמתו את ה-checksum והוסיפו את `iii.exe` ל-`PATH` (למשל `%USERPROFILE%\.local\bin\iii.exe`). ה-CLI אינו מחלץ אוטומטית את ZIP של Windows.
חיבור MCP אוטומטי ב-Windows מקורי נתמך רק עבור `agentmemory connect copilot-cli`. עבור סוכנים מקומיים אחרים ב-Windows, השתמשו בבלוק MCP הידני מתוך [סוכנים אחרים](#other-agents). הפעילו `connect` בתוך WSL רק אם סוכן היעד מותקן באותה סביבת WSL.
@@ -1161,7 +1163,7 @@ EMBEDDING_PROVIDER=local
-146 endpoints בפורט `3111`. ה-REST API נקשר ל-`127.0.0.1` כברירת מחדל. endpoints מוגנים דורשים `Authorization: Bearer `, ו-endpoints של mesh sync דורשים `AGENTMEMORY_SECRET` מוגדר באופן מפורש בשני ה-peers.
+147 endpoints בפורט `3111`. ה-REST API נקשר ל-`127.0.0.1` כברירת מחדל. endpoints מוגנים דורשים `Authorization: Bearer `, ו-endpoints של mesh sync דורשים `AGENTMEMORY_SECRET` מוגדר באופן מפורש בשני ה-peers.
**אימות (Authentication) פעיל כברירת מחדל.** אם `AGENTMEMORY_SECRET` לא מוגדר, בהפעלה הראשונה ה-CLI יוצר סוד אקראי ב-`~/.agentmemory/secret` עם הרשאות `0600`, ומעתיק אותו גם לתיקיית הנתונים שנבחרה. כל לקוח מצורף קורא אותו משם כשהוא מדבר עם שרת מקומי: ה-CLI, המציג, ה-hooks תחת `plugin/scripts`, שרת ה-MCP וה-shim `@agentmemory/mcp`, התצורות שנכתבות על ידי `agentmemory connect`, והאינטגרציות המצורפות של OpenCode, Pi, OpenClaw, Hermes וה-filesystem-watcher. ה-secret המאוחסן נשלח רק ל-URLs של loopback (`localhost`, `127.0.0.0/8`, `::1`). `AGENTMEMORY_SECRET` מפורש גובר תמיד, ולקוחות מרוחקים עדיין צריכים אותו מוגדר. Docker וה-entrypoints של `deploy/` כבר מייצרים ומייצאים את ה-secret שלהם. כדי לקרוא ל-API ביד:
@@ -1242,7 +1244,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.hi-IN.md b/READMEs/README.hi-IN.md
index 04eb563111..9185983cda 100644
--- a/READMEs/README.hi-IN.md
+++ b/READMEs/README.hi-IN.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Plugin install के बिना Claude Code (MCP-standalone path)
-अगर आप `/plugin install` का उपयोग करने के बजाय `~/.claude.json` के माध्यम से सीधे agentmemory का MCP server connect करते हैं, तो Claude Code कभी भी `${CLAUDE_PLUGIN_ROOT}` resolve नहीं करता और आपको hook scripts को `~/.claude/settings.json` में absolute paths पर point करना पड़ता है। ये paths आमतौर पर agentmemory version को embed करते हैं (जैसे `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), इसलिए अगला upgrade चुपचाप हर hook को तोड़ देता है।
+अगर आप `/plugin install` का उपयोग करने के बजाय `~/.claude.json` (डिफ़ॉल्ट पथ) के माध्यम से सीधे agentmemory का MCP server connect करते हैं, तो Claude Code कभी भी `${CLAUDE_PLUGIN_ROOT}` resolve नहीं करता और आपको hook scripts को `~/.claude/settings.json` (डिफ़ॉल्ट पथ) में absolute paths पर point करना पड़ता है। ये paths आमतौर पर agentmemory version को embed करते हैं (जैसे `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), इसलिए अगला upgrade चुपचाप हर hook को तोड़ देता है।
Workaround:
@@ -452,7 +452,9 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-यह वही hook commands को `~/.claude/settings.json` में merge करता है, current installed `@agentmemory/agentmemory` package की bundled `plugin/` directory पर resolve किए गए absolute paths के साथ। agentmemory upgrade करने के बाद paths refresh करने के लिए command फिर से चलाएँ। उसी file में user entries preserved रहती हैं; केवल पिछली agentmemory entries replace होती हैं। `/plugin install` path अनुशंसित approach बनी रहती है।
+यह कमांड MCP सर्वर को कॉन्फ़िगर करता है और साथ आए hooks को Claude Code के उपयोगकर्ता कॉन्फ़िगरेशन में मिलाता है। यदि `CLAUDE_CONFIG_DIR` सेट नहीं है, खाली है या उसमें केवल व्हाइटस्पेस हैं, तो यह MCP के लिए `~/.claude.json` और hooks के लिए `~/.claude/settings.json` का उपयोग करता है। डायरेक्टरी के अन्य मान आगे-पीछे के व्हाइटस्पेस सहित ठीक वैसे ही इस्तेमाल होते हैं जैसे दिए गए हैं। कस्टम डायरेक्टरी के लिए इस कमांड और Claude Code दोनों में `CLAUDE_CONFIG_DIR` का एक ही गैर-खाली मान सेट करें; तब फ़ाइलें क्रमशः `$CLAUDE_CONFIG_DIR/.claude.json` और `$CLAUDE_CONFIG_DIR/settings.json` होंगी। Claude Code के लॉन्च वातावरण में यह मान होना चाहिए, भले ही कनेक्टर इसे AgentMemory की `.env` से पढ़ता हो। इस कमांड को चलाने से पहले कस्टम डायरेक्टरी बनाएँ; अन्यथा कनेक्टर Claude Code को नहीं पहचान पाता और उसे छोड़ देता है। यदि shell के मान में केवल व्हाइटस्पेस हैं, तो Claude Code लॉन्च करने से पहले `CLAUDE_CONFIG_DIR` अनसेट करें, ताकि वह भी डिफ़ॉल्ट प्रोफ़ाइल का उपयोग करे। निरपेक्ष पथ का उपयोग करें। सापेक्ष पथ कार्यशील डायरेक्टरी के आधार पर तय होते हैं, इसलिए दोनों कमांड एक ही डायरेक्टरी से चलाएँ।
+
+Hook कमांड इंस्टॉल किए गए पैकेज की साथ आई `plugin/` डायरेक्टरी के ऐब्सोल्यूट पथ इस्तेमाल करते हैं। agentmemory अपग्रेड करने के बाद इन पथों को रीफ़्रेश करने के लिए कमांड फिर से चलाएँ। कॉन्फ़िगरेशन फ़ाइलों में उपयोगकर्ता की प्रविष्टियाँ बनी रहती हैं; केवल पिछली agentmemory प्रविष्टियाँ बदली जाती हैं। `/plugin install` का उपयोग करना अब भी अनुशंसित तरीका है।
Remote या protected deployments के लिए, Claude Code को `AGENTMEMORY_URL` और `AGENTMEMORY_SECRET` set के साथ launch करें। Plugin दोनों values को अपने bundled MCP server के माध्यम से pass करता है; जब `AGENTMEMORY_URL` खाली होता है, तो MCP shim `http://localhost:3111` का उपयोग करता है।
### Codex CLI (Codex plugin platform)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
पूर्ण गाइड: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory Windows 10/11 पर चलता है। WSL2 Linux path अपनाता है और pinned engine को automatically install कर सकता है। Native Windows पर pinned iii-engine v0.25.0 binary manually install करें: [iii v0.25.0 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) से सही archive download करें, checksum verify करें और `iii.exe` को `PATH` में रखें (उदाहरण: `%USERPROFILE%\.local\bin\iii.exe`)। CLI Windows ZIP को automatically extract नहीं करता।
+agentmemory Windows 10/11 पर चलता है। WSL2 Linux path अपनाता है और pinned engine को automatically install कर सकता है। Native Windows पर pinned iii-engine v0.25.1 binary manually install करें: [iii v0.25.1 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) से सही archive download करें, checksum verify करें और `iii.exe` को `PATH` में रखें (उदाहरण: `%USERPROFILE%\.local\bin\iii.exe`)। CLI Windows ZIP को automatically extract नहीं करता।
Native Windows में automated MCP wiring केवल `agentmemory connect copilot-cli` को support करती है। अन्य native Windows agents के लिए [Other agents](#other-agents) वाला manual MCP block इस्तेमाल करें। `connect` को WSL में तभी चलाएँ जब target agent भी उसी WSL environment में installed हो।
@@ -1175,7 +1177,7 @@ EMBEDDING_PROVIDER=local
-Port `3111` पर 146 endpoints। REST API default रूप से `127.0.0.1` से bind होता है। Protected endpoints `Authorization: Bearer ` की आवश्यकता रखते हैं, और mesh sync endpoints दोनों peers पर एक explicitly set `AGENTMEMORY_SECRET` की आवश्यकता रखते हैं।
+Port `3111` पर 147 endpoints। REST API default रूप से `127.0.0.1` से bind होता है। Protected endpoints `Authorization: Bearer ` की आवश्यकता रखते हैं, और mesh sync endpoints दोनों peers पर एक explicitly set `AGENTMEMORY_SECRET` की आवश्यकता रखते हैं।
प्रमाणीकरण डिफ़ॉल्ट रूप से चालू है। `AGENTMEMORY_SECRET` सेट न होने पर CLI पहली बार एक random secret `~/.agentmemory/secret` में रखता है और चुनी हुई डेटा डायरेक्टरी के `secret` में उसकी प्रति बनाता है; permissions `0600` होती हैं। साथ आए क्लाइंट लोकल कनेक्शन में इस मूल फ़ाइल को प्राथमिकता देते हैं और सेव किया secret सिर्फ loopback URL को भेजते हैं। स्पष्ट `AGENTMEMORY_SECRET` प्राथमिकता रखता है; रिमोट क्लाइंट को इसे environment में सेट करना होता है। Docker अपना secret बनाता है।
@@ -1256,7 +1258,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.hu-HU.md b/READMEs/README.hu-HU.md
index 2951739da5..b1fcd2e91e 100644
--- a/READMEs/README.hu-HU.md
+++ b/READMEs/README.hu-HU.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code a plugin telepítése nélkül (önálló MCP útvonal)
-Ha az agentmemory MCP szerverét közvetlenül a `~/.claude.json`-ban kötöd be, a `/plugin install` használata helyett, a Claude Code soha nem oldja fel a `${CLAUDE_PLUGIN_ROOT}`-ot, és a hook-szkripteket abszolút elérési utakra kell mutatnod a `~/.claude/settings.json`-ban. Ezek az útvonalak jellemzően beágyazzák az agentmemory verziószámát (pl. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), így a következő frissítés némán elront minden hookot.
+Ha az agentmemory MCP szerverét közvetlenül a `~/.claude.json` (alapértelmezett útvonal)-ban kötöd be, a `/plugin install` használata helyett, a Claude Code soha nem oldja fel a `${CLAUDE_PLUGIN_ROOT}`-ot, és a hook-szkripteket abszolút elérési utakra kell mutatnod a `~/.claude/settings.json` (alapértelmezett útvonal)-ban. Ezek az útvonalak jellemzően beágyazzák az agentmemory verziószámát (pl. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), így a következő frissítés némán elront minden hookot.
Megoldás:
@@ -452,7 +452,9 @@ Megoldás:
agentmemory connect claude-code --with-hooks
```
-Ez ugyanazokat a hook-parancsokat olvasztja be a `~/.claude/settings.json`-ba, abszolút elérési utakkal, amelyek a jelenleg telepített `@agentmemory/agentmemory` csomag becsomagolt `plugin/` mappájára mutatnak. Futtasd újra a parancsot az agentmemory frissítése után, hogy felfrissítsd az útvonalakat. A felhasználó saját bejegyzései ugyanabban a fájlban megmaradnak; csak a korábbi agentmemory-bejegyzések kerülnek lecserélésre. A `/plugin install` útvonal marad az ajánlott megközelítés.
+Ez a parancs beállítja az MCP-kiszolgálót, és beolvasztja a mellékelt hookokat a Claude Code felhasználói konfigurációjába. Ha a `CLAUDE_CONFIG_DIR` nincs beállítva, üres, vagy csak üres karaktereket tartalmaz, az MCP-hez a `~/.claude.json`, a hookokhoz pedig a `~/.claude/settings.json` fájlt használja. A többi könyvtárérték változatlanul kerül felhasználásra, az elején és végén lévő üres karakterekkel együtt. Egyéni könyvtár használatához állítsd a `CLAUDE_CONFIG_DIR` változót ugyanarra a nem üres értékre ennél a parancsnál és a Claude Code-nál is; ekkor az MCP fájlja `$CLAUDE_CONFIG_DIR/.claude.json`, a hookoké pedig `$CLAUDE_CONFIG_DIR/settings.json` lesz. A Claude Code-nak az indítási környezetében meg kell kapnia ezt az értéket akkor is, ha a csatlakozó az AgentMemory `.env` fájljából olvassa be. A parancs futtatása előtt hozd létre az egyéni könyvtárat; különben a csatlakozó nem észleli a Claude Code-ot, és kihagyja. Ha a shellben az érték csak üres karaktereket tartalmaz, a Claude Code indítása előtt töröld a `CLAUDE_CONFIG_DIR` változót a környezetből, hogy az is az alapértelmezett profilt használja. Használj abszolút elérési utat. A relatív utak a munkakönyvtárhoz képest értendők, ezért mindkét parancsot ugyanabból a könyvtárból kell futtatni.
+
+A hook-parancsok a telepített csomaghoz mellékelt `plugin/` könyvtárra mutató abszolút útvonalakat használnak. Az agentmemory frissítése után futtasd újra a parancsot az útvonalak frissítéséhez. A konfigurációs fájlok felhasználói bejegyzései megmaradnak; csak a korábbi agentmemory-bejegyzések cserélődnek le. Továbbra is a `/plugin install` használata az ajánlott megoldás.
Távoli vagy védett telepítésekhez indítsd el a Claude Code-ot az `AGENTMEMORY_URL` és az `AGENTMEMORY_SECRET` beállításával. A plugin mindkét értéket továbbadja a becsomagolt MCP szerverének; amikor az `AGENTMEMORY_URL` üres, az MCP shim a `http://localhost:3111`-et használja.
### Codex CLI (Codex plugin platform)
@@ -563,7 +565,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Teljes útmutató: [`integrations/hermes/`](../integrations/hermes/)
@@ -661,7 +663,7 @@ Az `npm start` ugyanazt a helyi szervert indítja, mint a telepített CLI. A kö
### Windows
-Az agentmemory Windows 10/11 rendszeren fut. A WSL2 a Linux útvonalat követi, és automatikusan telepítheti a rögzített motort. Natív Windowson kézzel telepítse a rögzített iii-engine v0.25.0 binárist: töltse le a megfelelő archívumot az [iii v0.25.0 kiadási oldaláról](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), ellenőrizze az ellenőrzőösszeget, majd helyezze az `iii.exe` fájlt a `PATH`-ra (például `%USERPROFILE%\.local\bin\iii.exe`). A CLI nem bontja ki automatikusan a Windows ZIP-et.
+Az agentmemory Windows 10/11 rendszeren fut. A WSL2 a Linux útvonalat követi, és automatikusan telepítheti a rögzített motort. Natív Windowson kézzel telepítse a rögzített iii-engine v0.25.1 binárist: töltse le a megfelelő archívumot az [iii v0.25.1 kiadási oldaláról](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), ellenőrizze az ellenőrzőösszeget, majd helyezze az `iii.exe` fájlt a `PATH`-ra (például `%USERPROFILE%\.local\bin\iii.exe`). A CLI nem bontja ki automatikusan a Windows ZIP-et.
A natív Windows automatizált MCP-kapcsolat csak az `agentmemory connect copilot-cli` parancsot támogatja. Más natív Windows-ügynökökhöz használja az [Egyéb ügynökök](#other-agents) kézi MCP-blokkját. A `connect` parancsot csak akkor futtassa WSL-ben, ha a célügynök is ugyanabban a WSL-környezetben van telepítve.
@@ -1158,7 +1160,7 @@ A teljes [`.env.example`](../.env.example) leírja a szolgáltatókat, rögzít
-146 endpoint a `3111`-es porton. A REST API alapértelmezetten a `127.0.0.1`-hez kötődik. A védett végpontok `Authorization: Bearer `-et igényelnek, és a mesh-sync végpontok mindkét oldalon explicit módon beállított `AGENTMEMORY_SECRET`-et igényelnek.
+147 endpoint a `3111`-es porton. A REST API alapértelmezetten a `127.0.0.1`-hez kötődik. A védett végpontok `Authorization: Bearer `-et igényelnek, és a mesh-sync végpontok mindkét oldalon explicit módon beállított `AGENTMEMORY_SECRET`-et igényelnek.
**A hitelesítés alapértelmezetten be van kapcsolva.** Ha az `AGENTMEMORY_SECRET` nincs beállítva, a CLI első indításkor véletlen titkot hoz létre a `~/.agentmemory/secret` fájlban `0600` jogosultsággal, és a kiválasztott adatkönyvtárba is átmásolja. Minden becsomagolt kliens onnan olvassa, amikor egy lokális szerverrel beszél: a CLI, a megjelenítő, a `plugin/scripts` alatti hookok, az MCP szerver és a `@agentmemory/mcp` shim, az `agentmemory connect` által írt konfigurációk, és a becsomagolt OpenCode, Pi, OpenClaw, Hermes és fájlrendszer-figyelő integrációk. A tárolt secret csak loopback URL-eknek kerül elküldésre (`localhost`, `127.0.0.0/8`, `::1`). Egy explicit `AGENTMEMORY_SECRET` mindig elsőbbséget kap, és a távoli klienseknek továbbra is be kell állítaniuk. A Docker és a `deploy/` entrypointok már generálnak és exportálnak egy saját secretet. Az API kézi hívásához:
@@ -1239,7 +1241,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.id-ID.md b/READMEs/README.id-ID.md
index b9b300ebfc..6be8f90a25 100644
--- a/READMEs/README.id-ID.md
+++ b/READMEs/README.id-ID.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code tanpa instalasi plugin (jalur MCP-standalone)
-Jika Anda menyambungkan server MCP agentmemory lewat `~/.claude.json` secara langsung tanpa memakai `/plugin install`, Claude Code tidak pernah meresolusi `${CLAUDE_PLUGIN_ROOT}` dan Anda harus mengarahkan script hook ke path absolut di `~/.claude/settings.json`. Path tersebut biasanya menyertakan versi agentmemory (misalnya `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), sehingga upgrade berikutnya diam-diam merusak setiap hook.
+Jika Anda menyambungkan server MCP agentmemory lewat `~/.claude.json` (jalur default) secara langsung tanpa memakai `/plugin install`, Claude Code tidak pernah meresolusi `${CLAUDE_PLUGIN_ROOT}` dan Anda harus mengarahkan script hook ke path absolut di `~/.claude/settings.json` (jalur default). Path tersebut biasanya menyertakan versi agentmemory (misalnya `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), sehingga upgrade berikutnya diam-diam merusak setiap hook.
Solusinya:
@@ -452,7 +452,9 @@ Solusinya:
agentmemory connect claude-code --with-hooks
```
-Ini menggabungkan perintah hook yang sama ke `~/.claude/settings.json` dengan path absolut yang diresolusi ke direktori `plugin/` bundel dari paket `@agentmemory/agentmemory` yang sedang terpasang. Jalankan ulang perintah ini setelah upgrade agentmemory untuk menyegarkan path-nya. Entri pengguna di file yang sama tetap dipertahankan; hanya entri agentmemory sebelumnya yang diganti. Jalur `/plugin install` tetap menjadi pendekatan yang direkomendasikan.
+Perintah ini mengonfigurasi server MCP dan menggabungkan hook bawaan ke konfigurasi pengguna Claude Code. Jika `CLAUDE_CONFIG_DIR` tidak diatur, kosong, atau hanya berisi whitespace, perintah ini menggunakan `~/.claude.json` untuk MCP dan `~/.claude/settings.json` untuk hook. Nilai direktori lainnya digunakan persis seperti yang diberikan, termasuk whitespace di awal dan akhir. Untuk direktori khusus, atur `CLAUDE_CONFIG_DIR` ke nilai tidak kosong yang sama untuk perintah ini dan Claude Code; file yang digunakan menjadi `$CLAUDE_CONFIG_DIR/.claude.json` dan `$CLAUDE_CONFIG_DIR/settings.json`, masing-masing. Claude Code harus menerima nilai ini di lingkungan saat dijalankan, meskipun konektor membacanya dari `.env` milik AgentMemory. Buat direktori khusus sebelum menjalankan perintah ini; jika tidak, konektor melewati Claude Code karena tidak terdeteksi. Jika nilai di shell hanya berisi whitespace, hapus `CLAUDE_CONFIG_DIR` dari lingkungan sebelum menjalankan Claude Code agar juga menggunakan profil default. Gunakan jalur absolut. Jalur relatif ditentukan berdasarkan direktori kerja, jadi kedua perintah harus dijalankan dari direktori yang sama.
+
+Perintah hook menggunakan jalur absolut ke direktori `plugin/` bawaan paket yang terpasang. Jalankan ulang perintah ini setelah memperbarui agentmemory untuk menyegarkan jalur tersebut. Entri pengguna dalam file konfigurasi tetap dipertahankan; hanya entri agentmemory sebelumnya yang diganti. Penggunaan `/plugin install` tetap menjadi pendekatan yang disarankan.
Untuk deployment remote atau terlindungi, jalankan Claude Code dengan `AGENTMEMORY_URL` dan `AGENTMEMORY_SECRET` yang sudah diset. Plugin ini meneruskan kedua nilai itu ke server MCP bundelnya; ketika `AGENTMEMORY_URL` kosong, shim MCP memakai `http://localhost:3111`.
### Codex CLI (platform plugin Codex)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Panduan lengkap: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory berjalan di Windows 10/11. WSL2 mengikuti jalur Linux dan dapat memasang engine yang dipatok secara otomatis. Pada Windows native, pasang biner iii-engine v0.25.0 yang dipatok secara manual: unduh arsip yang sesuai dari [halaman rilis iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verifikasi checksum, lalu letakkan `iii.exe` di `PATH` (misalnya `%USERPROFILE%\.local\bin\iii.exe`). CLI tidak mengekstrak ZIP Windows secara otomatis.
+agentmemory berjalan di Windows 10/11. WSL2 mengikuti jalur Linux dan dapat memasang engine yang dipatok secara otomatis. Pada Windows native, pasang biner iii-engine v0.25.1 yang dipatok secara manual: unduh arsip yang sesuai dari [halaman rilis iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verifikasi checksum, lalu letakkan `iii.exe` di `PATH` (misalnya `%USERPROFILE%\.local\bin\iii.exe`). CLI tidak mengekstrak ZIP Windows secara otomatis.
Wiring MCP otomatis di Windows native hanya mendukung `agentmemory connect copilot-cli`. Untuk agen Windows native lainnya, gunakan blok MCP manual dari [Agen lainnya](#other-agents). Jalankan `connect` di WSL hanya jika agen target juga dipasang di lingkungan WSL yang sama.
@@ -1175,7 +1177,7 @@ Referensi lengkap ada di [`.env.example`](../.env.example), termasuk penyedia, f
-146 endpoint di port `3111`. REST API terbind ke `127.0.0.1` secara default. Endpoint yang terlindungi membutuhkan `Authorization: Bearer `, dan endpoint mesh sync membutuhkan `AGENTMEMORY_SECRET` yang diset secara eksplisit di kedua peer.
+147 endpoint di port `3111`. REST API terbind ke `127.0.0.1` secara default. Endpoint yang terlindungi membutuhkan `Authorization: Bearer `, dan endpoint mesh sync membutuhkan `AGENTMEMORY_SECRET` yang diset secara eksplisit di kedua peer.
Autentikasi aktif secara default. Jika `AGENTMEMORY_SECRET` tidak disetel, CLI membuat rahasia acak saat pertama dijalankan di `~/.agentmemory/secret` dan menyalinnya ke `secret` dalam direktori data terpilih, dengan mode `0600`. Klien bawaan mengutamakan file kanonis ini untuk koneksi lokal dan hanya mengirim rahasia tersimpan ke URL loopback. `AGENTMEMORY_SECRET` eksplisit selalu diutamakan; klien remote harus mengaturnya melalui environment. Deployment Docker membuat rahasianya sendiri.
@@ -1256,7 +1258,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.it-IT.md b/READMEs/README.it-IT.md
index 76c4267bd3..341799588d 100644
--- a/READMEs/README.it-IT.md
+++ b/READMEs/README.it-IT.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code senza l'installazione del plugin (percorso MCP standalone)
-Se collegi il server MCP di agentmemory tramite `~/.claude.json` direttamente invece di usare `/plugin install`, Claude Code non risolve mai `${CLAUDE_PLUGIN_ROOT}` e devi puntare gli script degli hook a percorsi assoluti in `~/.claude/settings.json`. Questi percorsi di solito incorporano la versione di agentmemory (ad es. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), quindi il prossimo aggiornamento rompe silenziosamente ogni hook.
+Se collegi il server MCP di agentmemory tramite `~/.claude.json` (percorso predefinito) direttamente invece di usare `/plugin install`, Claude Code non risolve mai `${CLAUDE_PLUGIN_ROOT}` e devi puntare gli script degli hook a percorsi assoluti in `~/.claude/settings.json` (percorso predefinito). Questi percorsi di solito incorporano la versione di agentmemory (ad es. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), quindi il prossimo aggiornamento rompe silenziosamente ogni hook.
Soluzione alternativa:
@@ -449,7 +449,9 @@ Soluzione alternativa:
agentmemory connect claude-code --with-hooks
```
-Questo unisce gli stessi comandi degli hook in `~/.claude/settings.json` con percorsi assoluti risolti verso la directory `plugin/` incorporata nel pacchetto `@agentmemory/agentmemory` attualmente installato. Riesegui il comando dopo aver aggiornato agentmemory per aggiornare i percorsi. Le voci dell'utente nello stesso file vengono preservate; vengono sostituite solo le voci precedenti di agentmemory. Usare il percorso `/plugin install` resta l'approccio consigliato.
+Questo comando configura il server MCP e unisce gli hook inclusi alla configurazione utente di Claude Code. Se `CLAUDE_CONFIG_DIR` non è impostata, è vuota o contiene solo spazi, usa `~/.claude.json` per MCP e `~/.claude/settings.json` per gli hook. Gli altri valori di directory vengono usati esattamente come forniti, inclusi gli spazi iniziali e finali. Per una directory personalizzata, imposta `CLAUDE_CONFIG_DIR` sullo stesso valore non vuoto sia per questo comando sia per Claude Code; i file saranno quindi rispettivamente `$CLAUDE_CONFIG_DIR/.claude.json` e `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code deve ricevere questo valore nel proprio ambiente di avvio, anche se il connettore lo legge dal file `.env` di AgentMemory. Crea la directory personalizzata prima di eseguire questo comando; altrimenti il connettore ignora Claude Code perché non viene rilevato. Se il valore nella shell contiene solo spazi, rimuovi `CLAUDE_CONFIG_DIR` dall’ambiente prima di avviare Claude Code, in modo che usi anch’esso il profilo predefinito. Usa un percorso assoluto. I percorsi relativi vengono risolti dalla directory di lavoro, quindi entrambi i comandi devono essere eseguiti dalla stessa directory.
+
+I comandi degli hook usano percorsi assoluti verso la directory `plugin/` inclusa nel pacchetto installato. Riesegui il comando dopo aver aggiornato agentmemory per aggiornare questi percorsi. Le voci utente nei file di configurazione vengono preservate; vengono sostituite solo le precedenti voci di agentmemory. L’uso di `/plugin install` rimane l’approccio consigliato.
Per deployment remoti o protetti, avvia Claude Code con `AGENTMEMORY_URL` e `AGENTMEMORY_SECRET` impostati. Il plugin passa entrambi i valori al suo server MCP incorporato; quando `AGENTMEMORY_URL` è vuoto, lo shim MCP usa `http://localhost:3111`.
### Codex CLI (piattaforma plugin di Codex)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Guida completa: [`integrations/hermes/`](../integrations/hermes/)
@@ -655,7 +657,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory funziona su Windows 10/11. WSL2 segue il percorso Linux e può installare automaticamente l'engine fissato. Su Windows nativo, installare manualmente il binario iii-engine v0.25.0 fissato: scaricare l'archivio corrispondente dalla [pagina della release iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verificarne il checksum e mettere `iii.exe` nel `PATH` (ad esempio `%USERPROFILE%\.local\bin\iii.exe`). La CLI non estrae automaticamente lo ZIP Windows.
+agentmemory funziona su Windows 10/11. WSL2 segue il percorso Linux e può installare automaticamente l'engine fissato. Su Windows nativo, installare manualmente il binario iii-engine v0.25.1 fissato: scaricare l'archivio corrispondente dalla [pagina della release iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verificarne il checksum e mettere `iii.exe` nel `PATH` (ad esempio `%USERPROFILE%\.local\bin\iii.exe`). La CLI non estrae automaticamente lo ZIP Windows.
La configurazione MCP automatica su Windows nativo supporta solo `agentmemory connect copilot-cli`. Per gli altri agenti Windows nativi, usare il blocco MCP manuale da [Altri agenti](#other-agents). Eseguire `connect` in WSL solo se l'agente di destinazione è installato nello stesso ambiente WSL.
@@ -1168,7 +1170,7 @@ La documentazione completa è in [`.env.example`](../.env.example): credenziali,
-146 endpoint sulla porta `3111`. L'API REST si collega a `127.0.0.1` per impostazione predefinita. Gli endpoint protetti richiedono `Authorization: Bearer `, e gli endpoint di sincronizzazione mesh richiedono un `AGENTMEMORY_SECRET` impostato esplicitamente su entrambi i peer.
+147 endpoint sulla porta `3111`. L'API REST si collega a `127.0.0.1` per impostazione predefinita. Gli endpoint protetti richiedono `Authorization: Bearer `, e gli endpoint di sincronizzazione mesh richiedono un `AGENTMEMORY_SECRET` impostato esplicitamente su entrambi i peer.
**L'autenticazione è attiva per default.** Se `AGENTMEMORY_SECRET` non è impostato nella shell o in `~/.agentmemory/.env`, al primo avvio la CLI genera un segreto casuale in `~/.agentmemory/secret` e ne conserva una copia chiamata `secret` nella directory dati selezionata, con permessi `0600`. Ogni client incluso lo legge da lì quando parla con un server locale: la CLI, il viewer, gli hook sotto `plugin/scripts`, il server MCP e lo shim `@agentmemory/mcp`, le configurazioni scritte da `agentmemory connect`, e le integrazioni incluse OpenCode, Pi, OpenClaw, Hermes e filesystem-watcher. Il secret memorizzato viene inviato solo a URL loopback (`localhost`, `127.0.0.0/8`, `::1`). Un `AGENTMEMORY_SECRET` esplicito vince sempre, e i client remoti devono comunque averlo impostato. Docker e gli entrypoint di `deploy/` generano ed esportano già il proprio secret. Per chiamare l'API a mano:
@@ -1249,7 +1251,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ja-JP.md b/READMEs/README.ja-JP.md
index 5f3bd8dd2d..43913c0fd7 100644
--- a/READMEs/README.ja-JP.md
+++ b/READMEs/README.ja-JP.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### プラグインをインストールしない Claude Code(MCP スタンドアロン経路)
-`/plugin install` を使わず `~/.claude.json` から直接 agentmemory の MCP サーバーを配線する場合、Claude Code は `${CLAUDE_PLUGIN_ROOT}` を一切解決しないため、hook スクリプトを `~/.claude/settings.json` 内の絶対パスに向ける必要があります。これらのパスには通常 agentmemory のバージョンが埋め込まれる(例: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)ため、次のアップグレードで全 hook が静かに壊れます。
+`/plugin install` を使わず `~/.claude.json`(既定のパス) から直接 agentmemory の MCP サーバーを配線する場合、Claude Code は `${CLAUDE_PLUGIN_ROOT}` を一切解決しないため、hook スクリプトを `~/.claude/settings.json`(既定のパス) 内の絶対パスに向ける必要があります。これらのパスには通常 agentmemory のバージョンが埋め込まれる(例: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)ため、次のアップグレードで全 hook が静かに壊れます。
回避策:
@@ -452,7 +452,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-同じ hook コマンドを `~/.claude/settings.json` にマージし、現在インストールされている `@agentmemory/agentmemory` パッケージの同梱 `plugin/` ディレクトリに解決された絶対パスを書き込みます。agentmemory をアップグレードしたら、このコマンドを再実行してパスを更新してください。同じファイル内のユーザーエントリは保持され、以前の agentmemory エントリだけが置き換えられます。`/plugin install` の経路が推奨アプローチであることに変わりはありません。
+このコマンドは MCP サーバーを設定し、同梱の hook を Claude Code のユーザー設定にマージします。`CLAUDE_CONFIG_DIR` が未設定、空、または空白のみの場合、MCP には `~/.claude.json`、hook には `~/.claude/settings.json` を使います。それ以外のディレクトリ値は、前後の空白を含めて指定どおりに使われます。カスタムディレクトリを使う場合は、このコマンドと Claude Code の両方に同じ空でない `CLAUDE_CONFIG_DIR` の値を設定してください。その場合、ファイルはそれぞれ `$CLAUDE_CONFIG_DIR/.claude.json` と `$CLAUDE_CONFIG_DIR/settings.json` になります。コネクターが AgentMemory の `.env` から値を読み込む場合でも、Claude Code 自身の起動環境にこの値を設定する必要があります。このコマンドを実行する前にカスタムディレクトリを作成してください。存在しない場合、Claude Code は未検出としてスキップされます。shell の値が空白のみの場合は、Claude Code の起動前に `CLAUDE_CONFIG_DIR` を解除し、Claude Code 側でも既定のプロファイルが使われるようにしてください。絶対パスを使ってください。相対パスは作業ディレクトリを基準に解決されるため、両方のコマンドを同じディレクトリから実行する必要があります。
+
+Hook コマンドは、インストール済みパッケージに同梱された `plugin/` ディレクトリへの絶対パスを使います。agentmemory のアップグレード後にコマンドを再実行して、これらのパスを更新してください。設定ファイル内のユーザーのエントリは保持され、以前の agentmemory のエントリだけが置き換えられます。引き続き `/plugin install` の利用を推奨します。
リモートや保護されたデプロイでは、`AGENTMEMORY_URL` と `AGENTMEMORY_SECRET` を設定して Claude Code を起動してください。プラグインはこの両方の値を同梱の MCP サーバーに渡します。`AGENTMEMORY_URL` が空の場合、MCP shim は `http://localhost:3111` にフォールバックします。
### Codex CLI(Codex プラグインプラットフォーム)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
完全ガイド: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory は Windows 10/11 で動作します。WSL2 は Linux の経路に従い、ピン留めされたエンジンを自動インストールできます。ネイティブ Windows では、ピン留めされた iii-engine v0.25.0 バイナリを手動でインストールしてください。[iii v0.25.0 リリースページ](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0)から該当アーカイブをダウンロードして checksum を確認し、`iii.exe` を `PATH` に配置します(例: `%USERPROFILE%\.local\bin\iii.exe`)。CLI は Windows ZIP を自動展開しません。
+agentmemory は Windows 10/11 で動作します。WSL2 は Linux の経路に従い、ピン留めされたエンジンを自動インストールできます。ネイティブ Windows では、ピン留めされた iii-engine v0.25.1 バイナリを手動でインストールしてください。[iii v0.25.1 リリースページ](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1)から該当アーカイブをダウンロードして checksum を確認し、`iii.exe` を `PATH` に配置します(例: `%USERPROFILE%\.local\bin\iii.exe`)。CLI は Windows ZIP を自動展開しません。
ネイティブ Windows の自動 MCP 接続は `agentmemory connect copilot-cli` のみをサポートします。それ以外のネイティブ Windows エージェントには[その他のエージェント](#other-agents)の手動 MCP ブロックを使用してください。`connect` を WSL 内で実行するのは、対象エージェントも同じ WSL 環境にインストールされている場合に限ります。
@@ -1174,7 +1176,7 @@ EMBEDDING_PROVIDER=local
-ポート `3111` 上の 146 エンドポイント。REST API はデフォルトで `127.0.0.1` にバインドします。保護されたエンドポイントは `Authorization: Bearer ` を要求し、mesh sync エンドポイントは両ピアで明示的に設定された `AGENTMEMORY_SECRET` を要求します。
+ポート `3111` 上の 147 エンドポイント。REST API はデフォルトで `127.0.0.1` にバインドします。保護されたエンドポイントは `Authorization: Bearer ` を要求し、mesh sync エンドポイントは両ピアで明示的に設定された `AGENTMEMORY_SECRET` を要求します。
認証はデフォルトで有効です。`AGENTMEMORY_SECRET` が未設定なら、CLI は初回起動時にランダムなシークレットを `~/.agentmemory/secret` に保存し、選択したデータディレクトリの `secret` にも複製します。権限は `0600` です。同梱クライアントはローカル接続時にこの共通ファイルを優先し、保存されたシークレットを送るのはループバック URL だけです。明示的な `AGENTMEMORY_SECRET` が優先され、リモート接続には環境変数で指定します。Docker デプロイは独自のシークレットを生成します。
@@ -1255,7 +1257,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ko-KR.md b/READMEs/README.ko-KR.md
index 75ea0ac701..a70c02477a 100644
--- a/READMEs/README.ko-KR.md
+++ b/READMEs/README.ko-KR.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -442,7 +442,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### 플러그인 설치 없이 Claude Code 사용 (MCP 독립형 경로)
-`/plugin install`을 사용하는 대신 `~/.claude.json`을 통해 agentmemory의 MCP 서버를 직접 연결하면, Claude Code는 `${CLAUDE_PLUGIN_ROOT}`를 해석하지 못하므로 `~/.claude/settings.json`의 hook 스크립트를 절대 경로로 지정해야 합니다. 이런 경로는 보통 agentmemory 버전을 포함하기 때문에(예: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), 다음 업그레이드에서 모든 hook이 조용히 깨질 수 있습니다.
+`/plugin install`을 사용하는 대신 `~/.claude.json` (기본 경로)을 통해 agentmemory의 MCP 서버를 직접 연결하면, Claude Code는 `${CLAUDE_PLUGIN_ROOT}`를 해석하지 못하므로 `~/.claude/settings.json` (기본 경로)의 hook 스크립트를 절대 경로로 지정해야 합니다. 이런 경로는 보통 agentmemory 버전을 포함하기 때문에(예: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), 다음 업그레이드에서 모든 hook이 조용히 깨질 수 있습니다.
해결책:
@@ -450,7 +450,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-이 명령은 현재 설치된 `@agentmemory/agentmemory` 패키지의 번들된 `plugin/` 디렉터리로 해석된 절대 경로를 사용해, 동일한 hook 명령을 `~/.claude/settings.json`에 병합합니다. agentmemory를 업그레이드한 뒤에는 동일한 명령을 다시 실행해서 경로를 갱신하십시오. 같은 파일의 사용자 항목은 보존되며, 이전 agentmemory 항목만 교체됩니다. `/plugin install` 경로를 사용하는 것이 여전히 권장되는 방식입니다.
+이 명령은 MCP 서버를 구성하고 번들 hook을 Claude Code의 사용자 설정에 병합합니다. `CLAUDE_CONFIG_DIR`가 설정되지 않았거나 비어 있거나 공백만 포함하면 MCP에는 `~/.claude.json`을, hook에는 `~/.claude/settings.json`을 사용합니다. 그 밖의 디렉터리 값은 앞뒤 공백을 포함해 입력한 그대로 사용합니다. 사용자 지정 디렉터리를 사용하려면 이 명령과 Claude Code 양쪽에 `CLAUDE_CONFIG_DIR`를 동일한 비어 있지 않은 값으로 설정하세요. 그러면 각각 `$CLAUDE_CONFIG_DIR/.claude.json`과 `$CLAUDE_CONFIG_DIR/settings.json`을 사용합니다. 커넥터가 AgentMemory의 `.env`에서 값을 읽더라도 Claude Code 자체의 실행 환경에 이 값이 전달되어야 합니다. 이 명령을 실행하기 전에 사용자 지정 디렉터리를 만드세요. 디렉터리가 없으면 커넥터는 Claude Code를 감지하지 못한 것으로 처리하고 건너뜁니다. shell 값이 공백만 포함하면 Claude Code를 시작하기 전에 `CLAUDE_CONFIG_DIR`를 해제하여 Claude Code도 기본 프로필을 사용하도록 하세요. 절대 경로를 사용하세요. 상대 경로는 작업 디렉터리를 기준으로 해석되므로 두 명령을 같은 디렉터리에서 실행해야 합니다.
+
+Hook 명령은 설치된 패키지에 포함된 `plugin/` 디렉터리의 절대 경로를 사용합니다. agentmemory를 업그레이드한 후 명령을 다시 실행하여 경로를 갱신하세요. 설정 파일에 있는 사용자 항목은 유지되며, 이전 agentmemory 항목만 교체됩니다. `/plugin install` 사용을 계속 권장합니다.
원격 또는 보호된 배포의 경우, `AGENTMEMORY_URL`과 `AGENTMEMORY_SECRET`을 설정한 채로 Claude Code를 실행하십시오. 플러그인은 두 값을 모두 번들된 MCP 서버로 전달합니다. `AGENTMEMORY_URL`이 비어 있으면 MCP shim은 `http://localhost:3111`을 사용합니다.
### Codex CLI (Codex 플러그인 플랫폼)
@@ -557,7 +559,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
전체 가이드: [`integrations/hermes/`](../integrations/hermes/)
@@ -654,7 +656,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory는 Windows 10/11에서 실행됩니다. WSL2는 Linux 경로를 따르며 고정 엔진을 자동 설치할 수 있습니다. 네이티브 Windows에서는 고정된 iii-engine v0.25.0 바이너리를 수동 설치하십시오: [iii v0.25.0 릴리스 페이지](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0)에서 맞는 아카이브를 다운로드하고 checksum을 확인한 뒤 `iii.exe`를 `PATH`에 두십시오(예: `%USERPROFILE%\.local\bin\iii.exe`). CLI는 Windows ZIP을 자동으로 압축 해제하지 않습니다.
+agentmemory는 Windows 10/11에서 실행됩니다. WSL2는 Linux 경로를 따르며 고정 엔진을 자동 설치할 수 있습니다. 네이티브 Windows에서는 고정된 iii-engine v0.25.1 바이너리를 수동 설치하십시오: [iii v0.25.1 릴리스 페이지](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1)에서 맞는 아카이브를 다운로드하고 checksum을 확인한 뒤 `iii.exe`를 `PATH`에 두십시오(예: `%USERPROFILE%\.local\bin\iii.exe`). CLI는 Windows ZIP을 자동으로 압축 해제하지 않습니다.
네이티브 Windows 자동 MCP 연결은 `agentmemory connect copilot-cli`만 지원합니다. 다른 네이티브 Windows 에이전트는 [다른 에이전트](#other-agents)의 수동 MCP 블록을 사용하십시오. 대상 에이전트도 같은 WSL 환경에 설치된 경우에만 WSL에서 `connect`를 실행하십시오.
@@ -1173,7 +1175,7 @@ EMBEDDING_PROVIDER=local
-포트 `3111`의 엔드포인트 146개. REST API는 기본적으로 `127.0.0.1`에 바인딩됩니다. 보호된 엔드포인트는 `Authorization: Bearer `을 요구하며, mesh sync 엔드포인트는 양쪽 피어 모두에 `AGENTMEMORY_SECRET`이 명시적으로 설정되어 있어야 합니다.
+포트 `3111`의 엔드포인트 147개. REST API는 기본적으로 `127.0.0.1`에 바인딩됩니다. 보호된 엔드포인트는 `Authorization: Bearer `을 요구하며, mesh sync 엔드포인트는 양쪽 피어 모두에 `AGENTMEMORY_SECRET`이 명시적으로 설정되어 있어야 합니다.
인증은 기본적으로 활성화됩니다. `AGENTMEMORY_SECRET`이 없으면 CLI가 처음 시작할 때 임의의 비밀값을 `~/.agentmemory/secret`에 저장하고 선택한 데이터 디렉터리의 `secret`에도 복사합니다. 권한은 `0600`입니다. 번들 클라이언트는 로컬 연결 시 이 공통 파일을 우선하며 저장된 비밀값은 루프백 URL에만 보냅니다. 명시적인 `AGENTMEMORY_SECRET`이 우선하고 원격 클라이언트는 환경 변수로 설정해야 합니다. Docker 배포는 자체 비밀값을 생성합니다.
@@ -1254,7 +1256,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.nb-NO.md b/READMEs/README.nb-NO.md
index 59f55f0809..9cce02dcf8 100644
--- a/READMEs/README.nb-NO.md
+++ b/READMEs/README.nb-NO.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -439,7 +439,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code uten plugin-installasjon (MCP-frittstående vei)
-Hvis du kobler agentmemorys MCP-server direkte gjennom `~/.claude.json` i stedet for å bruke `/plugin install`, løser Claude Code aldri opp `${CLAUDE_PLUGIN_ROOT}`, og du må peke hook-skriptene til absolutte stier i `~/.claude/settings.json`. Disse stiene bygger typisk inn agentmemory-versjonen (f.eks. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så neste oppgradering knekker stille hver hook.
+Hvis du kobler agentmemorys MCP-server direkte gjennom `~/.claude.json` (standardsti) i stedet for å bruke `/plugin install`, løser Claude Code aldri opp `${CLAUDE_PLUGIN_ROOT}`, og du må peke hook-skriptene til absolutte stier i `~/.claude/settings.json` (standardsti). Disse stiene bygger typisk inn agentmemory-versjonen (f.eks. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så neste oppgradering knekker stille hver hook.
Løsning:
@@ -447,7 +447,9 @@ Løsning:
agentmemory connect claude-code --with-hooks
```
-Dette slår sammen de samme hook-kommandoene inn i `~/.claude/settings.json` med absolutte stier løst opp mot den medfølgende `plugin/`-katalogen til den installerte `@agentmemory/agentmemory`-pakken. Kjør kommandoen på nytt etter at du har oppgradert agentmemory for å oppdatere stiene. Brukeroppføringer i samme fil bevares; kun tidligere agentmemory-oppføringer byttes ut. Å bruke `/plugin install`-veien er fortsatt den anbefalte metoden.
+Denne kommandoen konfigurerer MCP-serveren og fletter de medfølgende hookene inn i Claude Codes brukerkonfigurasjon. Hvis `CLAUDE_CONFIG_DIR` ikke er satt, er tom eller bare inneholder blanktegn, brukes `~/.claude.json` for MCP og `~/.claude/settings.json` for hooks. Andre mappeverdier brukes nøyaktig som angitt, inkludert innledende og avsluttende blanktegn. For en egendefinert mappe setter du `CLAUDE_CONFIG_DIR` til den samme ikke-tomme verdien for både denne kommandoen og Claude Code; filene blir da henholdsvis `$CLAUDE_CONFIG_DIR/.claude.json` og `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code må motta verdien i oppstartsmiljøet sitt, selv om koblingen leser den fra AgentMemorys `.env`. Opprett den egendefinerte mappen før du kjører kommandoen; ellers hopper koblingen over Claude Code fordi det ikke blir oppdaget. Hvis verdien i skallet bare inneholder blanktegn, fjern `CLAUDE_CONFIG_DIR` fra miljøet før du starter Claude Code, slik at det også bruker standardprofilen. Bruk en absolutt sti. Relative stier tolkes fra arbeidsmappen, så begge kommandoene må kjøres fra samme mappe.
+
+Hook-kommandoene bruker absolutte stier til den installerte pakkens medfølgende `plugin/`-mappe. Kjør kommandoen på nytt etter en oppgradering av agentmemory for å oppdatere stiene. Brukerens egne oppføringer i konfigurasjonsfilene beholdes; bare tidligere agentmemory-oppføringer erstattes. Det anbefales fortsatt å bruke `/plugin install`.
For eksterne eller beskyttede distribusjoner, start Claude Code med `AGENTMEMORY_URL` og `AGENTMEMORY_SECRET` satt. Pluginen sender begge verdiene videre til sin medfølgende MCP-server; når `AGENTMEMORY_URL` er tom, bruker MCP-shimmen `http://localhost:3111`.
### Codex CLI (Codex-plugin-plattformen)
@@ -556,7 +558,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Full veiledning: [`integrations/hermes/`](../integrations/hermes/)
@@ -653,7 +655,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory kjører på Windows 10/11. WSL2 følger Linux-stien og kan installere den fastlåste engine-en automatisk. Native Windows krever at den fastlåste iii-engine v0.25.0-binærfilen installeres manuelt; last ned det tilsvarende arkivet fra [iii v0.25.0-utgivelsessiden](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), kontroller kontrollsummen og legg `iii.exe` på `PATH` (for eksempel `%USERPROFILE%\.local\bin\iii.exe`). CLI-en pakker ikke ut Windows-ZIP-filen automatisk.
+agentmemory kjører på Windows 10/11. WSL2 følger Linux-stien og kan installere den fastlåste engine-en automatisk. Native Windows krever at den fastlåste iii-engine v0.25.1-binærfilen installeres manuelt; last ned det tilsvarende arkivet fra [iii v0.25.1-utgivelsessiden](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), kontroller kontrollsummen og legg `iii.exe` på `PATH` (for eksempel `%USERPROFILE%\.local\bin\iii.exe`). CLI-en pakker ikke ut Windows-ZIP-filen automatisk.
Automatisert native Windows-MCP-tilkobling støtter bare `agentmemory connect copilot-cli`. For andre native Windows-agenter bruker du den manuelle MCP-blokken fra [Andre agenter](#other-agents). Kjør `connect` i WSL bare når målagenten er installert i det samme WSL-miljøet.
@@ -1166,7 +1168,7 @@ Den fullstendige referansen er [`.env.example`](../.env.example), med legitimasj
-146 endepunkter på port `3111`. REST-API-en bindes til `127.0.0.1` som standard. Beskyttede endepunkter krever `Authorization: Bearer `, og mesh-synkroniseringsendepunkter krever en uttrykkelig satt `AGENTMEMORY_SECRET` på begge sider.
+147 endepunkter på port `3111`. REST-API-en bindes til `127.0.0.1` som standard. Beskyttede endepunkter krever `Authorization: Bearer `, og mesh-synkroniseringsendepunkter krever en uttrykkelig satt `AGENTMEMORY_SECRET` på begge sider.
**Autentisering er på som standard.** Hvis `AGENTMEMORY_SECRET` verken er satt i skallet eller i `~/.agentmemory/.env`, oppretter CLI-en en tilfeldig hemmelighet ved første start i `~/.agentmemory/secret` og en kopi kalt `secret` i den valgte datamappen, med filmodus `0600`. Alle medfølgende klienter leser den derfra når de snakker med en lokal server: CLI-en, viewer, hookene under `plugin/scripts`, MCP-serveren og `@agentmemory/mcp`-shimmen, konfigurasjonene skrevet av `agentmemory connect` og de medfølgende OpenCode-, Pi-, OpenClaw-, Hermes- og filsystemovervåker-integrasjonene. Den lagrede hemmeligheten sendes bare til loopback-URL-er (`localhost`, `127.0.0.0/8`, `::1`). En uttrykkelig `AGENTMEMORY_SECRET` vinner alltid, og eksterne klienter trenger hemmeligheten i miljøet sitt. Docker-basert selvhosting fra repoet og `deploy/`-entrypointene genererer og eksporterer sin egen hemmelighet. Slik kaller du API-et manuelt:
@@ -1247,7 +1249,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.nl-NL.md b/READMEs/README.nl-NL.md
index d5f8c62a3d..6af924de0f 100644
--- a/READMEs/README.nl-NL.md
+++ b/READMEs/README.nl-NL.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -439,7 +439,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code zonder de plugin-installatie (MCP-standalone pad)
-Als je de MCP-server van agentmemory rechtstreeks via `~/.claude.json` koppelt in plaats van `/plugin install` te gebruiken, lost Claude Code `${CLAUDE_PLUGIN_ROOT}` nooit op en moet je hook-scripts naar absolute paden in `~/.claude/settings.json` laten verwijzen. Die paden bevatten doorgaans de agentmemory-versie (bijv. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), waardoor de volgende upgrade stilletjes elke hook stuk maakt.
+Als je de MCP-server van agentmemory rechtstreeks via `~/.claude.json` (standaardpad) koppelt in plaats van `/plugin install` te gebruiken, lost Claude Code `${CLAUDE_PLUGIN_ROOT}` nooit op en moet je hook-scripts naar absolute paden in `~/.claude/settings.json` (standaardpad) laten verwijzen. Die paden bevatten doorgaans de agentmemory-versie (bijv. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), waardoor de volgende upgrade stilletjes elke hook stuk maakt.
Workaround:
@@ -447,7 +447,9 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-Dit voegt dezelfde hook-commando's samen in `~/.claude/settings.json`, met absolute paden die verwijzen naar de gebundelde `plugin/`-map van het momenteel geïnstalleerde `@agentmemory/agentmemory`-package. Voer het commando opnieuw uit na het upgraden van agentmemory om de paden te verversen. Gebruikersinvoer in hetzelfde bestand blijft behouden; alleen eerdere agentmemory-invoer wordt vervangen. Het `/plugin install`-pad blijft de aanbevolen aanpak.
+Dit commando configureert de MCP-server en voegt de meegeleverde hooks samen met de gebruikersconfiguratie van Claude Code. Als `CLAUDE_CONFIG_DIR` niet is ingesteld, leeg is of alleen witruimte bevat, gebruikt het `~/.claude.json` voor MCP en `~/.claude/settings.json` voor hooks. Andere mapwaarden worden precies gebruikt zoals opgegeven, inclusief witruimte aan het begin en einde. Voor een aangepaste map stel je `CLAUDE_CONFIG_DIR` voor zowel dit commando als Claude Code in op dezelfde niet-lege waarde; de bestanden zijn dan respectievelijk `$CLAUDE_CONFIG_DIR/.claude.json` en `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code moet deze waarde ontvangen in zijn opstartomgeving, ook als de connector die uit het `.env`-bestand van AgentMemory leest. Maak de aangepaste map aan voordat je dit commando uitvoert; anders slaat de connector Claude Code over omdat het niet wordt gedetecteerd. Als de waarde in de shell alleen witruimte bevat, verwijder dan `CLAUDE_CONFIG_DIR` uit de omgeving voordat je Claude Code start, zodat het ook het standaardprofiel gebruikt. Gebruik een absoluut pad. Relatieve paden worden vanuit de werkmap bepaald, dus beide opdrachten moeten vanuit dezelfde map worden uitgevoerd.
+
+Hook-commando’s gebruiken absolute paden naar de meegeleverde map `plugin/` van het geïnstalleerde pakket. Voer het commando na het upgraden van agentmemory opnieuw uit om deze paden te vernieuwen. Gebruikersinvoer in de configuratiebestanden blijft behouden; alleen eerdere agentmemory-invoer wordt vervangen. Het gebruik van `/plugin install` blijft de aanbevolen aanpak.
Voor remote of beveiligde deployments start je Claude Code met `AGENTMEMORY_URL` en `AGENTMEMORY_SECRET` ingesteld. De plugin geeft beide waarden door aan zijn gebundelde MCP-server; wanneer `AGENTMEMORY_URL` leeg is, gebruikt de MCP-shim `http://localhost:3111`.
### Codex CLI (Codex-pluginplatform)
@@ -556,7 +558,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Volledige handleiding: [`integrations/hermes/`](../integrations/hermes/)
@@ -651,7 +653,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory draait op Windows 10/11. WSL2 volgt het Linux-pad en kan de vastgezette engine automatisch installeren. Native Windows vereist handmatige installatie van de vastgezette iii-engine v0.25.0-binary; download het passende archief van de [iii v0.25.0-releasepagina](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), controleer de checksum en plaats `iii.exe` op `PATH` (bijvoorbeeld `%USERPROFILE%\.local\bin\iii.exe`). De CLI pakt de Windows ZIP niet automatisch uit.
+agentmemory draait op Windows 10/11. WSL2 volgt het Linux-pad en kan de vastgezette engine automatisch installeren. Native Windows vereist handmatige installatie van de vastgezette iii-engine v0.25.1-binary; download het passende archief van de [iii v0.25.1-releasepagina](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), controleer de checksum en plaats `iii.exe` op `PATH` (bijvoorbeeld `%USERPROFILE%\.local\bin\iii.exe`). De CLI pakt de Windows ZIP niet automatisch uit.
Geautomatiseerde MCP-koppeling op native Windows ondersteunt alleen `agentmemory connect copilot-cli`. Gebruik voor andere native Windows-agents het handmatige MCP-blok uit [Other agents](#other-agents). Voer `connect` binnen WSL alleen uit wanneer de doelagent in dezelfde WSL-omgeving is geïnstalleerd.
@@ -1162,7 +1164,7 @@ De volledige referentie staat in [`.env.example`](../.env.example), met provider
-146 endpoints op poort `3111`. De REST API bindt standaard aan `127.0.0.1`. Beschermde endpoints vereisen `Authorization: Bearer `, en mesh-sync-endpoints vereisen een expliciet ingestelde `AGENTMEMORY_SECRET` op beide peers.
+147 endpoints op poort `3111`. De REST API bindt standaard aan `127.0.0.1`. Beschermde endpoints vereisen `Authorization: Bearer `, en mesh-sync-endpoints vereisen een expliciet ingestelde `AGENTMEMORY_SECRET` op beide peers.
**Authenticatie staat standaard aan.** Als `AGENTMEMORY_SECRET` niet in de shell of in `~/.agentmemory/.env` staat, maakt de CLI bij de eerste start een willekeurig secret in `~/.agentmemory/secret` en een kopie met de naam `secret` in de geselecteerde gegevensmap, met bestandsmodus `0600`. Elke gebundelde client leest het daar wanneer die met een lokale server communiceert: de CLI, viewer, hooks onder `plugin/scripts`, MCP-server en `@agentmemory/mcp`-shim, configs geschreven door `agentmemory connect`, en de gebundelde OpenCode-, Pi-, OpenClaw-, Hermes- en filesystem-watcher-integraties. Het opgeslagen secret wordt alleen verstuurd naar loopback-URL's (`localhost`, `127.0.0.0/8`, `::1`). Een expliciete `AGENTMEMORY_SECRET` wint altijd, en externe clients hebben het secret in hun omgeving nodig. Docker self-host deployments vanuit de repository en de `deploy/`-entrypoints genereren en exporteren hun eigen secret. Zo roep je de API handmatig aan:
@@ -1243,7 +1245,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.pl-PL.md b/READMEs/README.pl-PL.md
index d20aa558c1..098d6dbdd2 100644
--- a/READMEs/README.pl-PL.md
+++ b/READMEs/README.pl-PL.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code bez instalacji pluginu (ścieżka samodzielnego MCP)
-Jeśli podłączasz serwer MCP agentmemory bezpośrednio przez `~/.claude.json` zamiast używać `/plugin install`, Claude Code nigdy nie rozwiąże `${CLAUDE_PLUGIN_ROOT}` i musisz wskazać skryptom hooków bezwzględne ścieżki w `~/.claude/settings.json`. Te ścieżki zwykle zawierają w sobie wersję agentmemory (np. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), więc kolejna aktualizacja po cichu psuje każdy hook.
+Jeśli podłączasz serwer MCP agentmemory bezpośrednio przez `~/.claude.json` (domyślna ścieżka) zamiast używać `/plugin install`, Claude Code nigdy nie rozwiąże `${CLAUDE_PLUGIN_ROOT}` i musisz wskazać skryptom hooków bezwzględne ścieżki w `~/.claude/settings.json` (domyślna ścieżka). Te ścieżki zwykle zawierają w sobie wersję agentmemory (np. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), więc kolejna aktualizacja po cichu psuje każdy hook.
Rozwiązanie zastępcze:
@@ -452,7 +452,9 @@ Rozwiązanie zastępcze:
agentmemory connect claude-code --with-hooks
```
-To scala te same komendy hooków do `~/.claude/settings.json`, z bezwzględnymi ścieżkami rozwiązanymi do dołączonego katalogu `plugin/` aktualnie zainstalowanego pakietu `@agentmemory/agentmemory`. Uruchom tę komendę ponownie po aktualizacji agentmemory, aby odświeżyć ścieżki. Wpisy użytkownika w tym samym pliku są zachowywane; zastępowane są tylko wcześniejsze wpisy agentmemory. Zalecanym podejściem pozostaje ścieżka `/plugin install`.
+Ta komenda konfiguruje serwer MCP i scala dołączone hooki z konfiguracją użytkownika Claude Code. Jeśli `CLAUDE_CONFIG_DIR` nie jest ustawiona, jest pusta lub zawiera tylko białe znaki, używa `~/.claude.json` dla MCP i `~/.claude/settings.json` dla hooków. Pozostałe wartości katalogu są używane dokładnie w podanej postaci, łącznie z białymi znakami na początku i końcu. Aby użyć własnego katalogu, ustaw `CLAUDE_CONFIG_DIR` na tę samą niepustą wartość dla tej komendy i Claude Code; pliki będą wtedy miały ścieżki odpowiednio `$CLAUDE_CONFIG_DIR/.claude.json` i `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code musi otrzymać tę wartość w swoim środowisku uruchomieniowym, nawet jeśli konektor odczytuje ją z pliku `.env` AgentMemory. Utwórz własny katalog przed uruchomieniem tej komendy; w przeciwnym razie konektor pominie Claude Code jako niewykryty. Jeśli wartość w powłoce zawiera tylko białe znaki, usuń `CLAUDE_CONFIG_DIR` ze środowiska przed uruchomieniem Claude Code, aby również używał profilu domyślnego. Użyj ścieżki bezwzględnej. Ścieżki względne są rozwiązywane względem katalogu roboczego, więc oba polecenia muszą być uruchamiane z tego samego katalogu.
+
+Komendy hooków używają bezwzględnych ścieżek do katalogu `plugin/` dołączonego do zainstalowanego pakietu. Po aktualizacji agentmemory uruchom komendę ponownie, aby odświeżyć te ścieżki. Wpisy użytkownika w plikach konfiguracyjnych są zachowywane; zastępowane są tylko poprzednie wpisy agentmemory. Zalecanym sposobem pozostaje użycie `/plugin install`.
Dla zdalnych lub chronionych wdrożeń uruchom Claude Code z ustawionymi `AGENTMEMORY_URL` i `AGENTMEMORY_SECRET`. Plugin przekazuje obie wartości dalej do swojego dołączonego serwera MCP; gdy `AGENTMEMORY_URL` jest puste, shim MCP używa `http://localhost:3111`.
### Codex CLI (platforma pluginów Codex)
@@ -563,7 +565,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Pełny przewodnik: [`integrations/hermes/`](../integrations/hermes/)
@@ -661,7 +663,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory działa w Windows 10/11. WSL2 korzysta ze ścieżki linuksowej i może automatycznie zainstalować przypięty silnik. Natywny Windows wymaga ręcznie zainstalowanego przypiętego pliku binarnego iii-engine v0.25.0; pobierz pasujące archiwum ze [strony wydania iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), zweryfikuj sumę kontrolną i umieść `iii.exe` w `PATH` (na przykład `%USERPROFILE%\.local\bin\iii.exe`). CLI nie wypakowuje automatycznie archiwum ZIP dla Windows.
+agentmemory działa w Windows 10/11. WSL2 korzysta ze ścieżki linuksowej i może automatycznie zainstalować przypięty silnik. Natywny Windows wymaga ręcznie zainstalowanego przypiętego pliku binarnego iii-engine v0.25.1; pobierz pasujące archiwum ze [strony wydania iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), zweryfikuj sumę kontrolną i umieść `iii.exe` w `PATH` (na przykład `%USERPROFILE%\.local\bin\iii.exe`). CLI nie wypakowuje automatycznie archiwum ZIP dla Windows.
Zautomatyzowane podłączanie MCP w natywnym Windows obsługuje tylko `agentmemory connect copilot-cli`. Dla pozostałych natywnych agentów Windows użyj ręcznego bloku MCP z sekcji [Inni agenci](#other-agents). Uruchamiaj `connect` w WSL tylko wtedy, gdy docelowy agent jest zainstalowany w tym samym środowisku WSL.
@@ -1158,7 +1160,7 @@ Pełny opis w [`.env.example`](../.env.example) obejmuje dostawców, filtry prze
-146 endpointów na porcie `3111`. REST API domyślnie wiąże się z `127.0.0.1`. Chronione endpointy wymagają `Authorization: Bearer `, a endpointy synchronizacji mesh wymagają wyraźnie ustawionego `AGENTMEMORY_SECRET` na obu peerach.
+147 endpointów na porcie `3111`. REST API domyślnie wiąże się z `127.0.0.1`. Chronione endpointy wymagają `Authorization: Bearer `, a endpointy synchronizacji mesh wymagają wyraźnie ustawionego `AGENTMEMORY_SECRET` na obu peerach.
**Autoryzacja jest domyślnie włączona.** Gdy `AGENTMEMORY_SECRET` nie jest ustawiony, CLI przy pierwszym uruchomieniu generuje losowy sekret w `~/.agentmemory/secret` z uprawnieniami `0600` i kopiuje go także do wybranego katalogu danych. Wszystkie dołączone klienty odczytują go stamtąd, gdy łączą się z lokalnym serwerem: CLI, podgląd, hooki w `plugin/scripts`, serwer MCP i shim `@agentmemory/mcp`, konfiguracje tworzone przez `agentmemory connect` oraz dołączone integracje OpenCode, Pi, OpenClaw, Hermes i obserwator systemu plików. Zapisany sekret jest wysyłany tylko na adresy loopback (`localhost`, `127.0.0.0/8`, `::1`). Jawnie ustawione `AGENTMEMORY_SECRET` ma zawsze pierwszeństwo, a zdalni klienci muszą mieć sekret w swoim środowisku. Wdrożenia self-hosted Docker oparte na repozytorium i punkty wejścia `deploy/` generują i eksportują własny sekret. Aby ręcznie wywołać API:
@@ -1239,7 +1241,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.pt-BR.md b/READMEs/README.pt-BR.md
index c6c37e69f3..fee630c5cd 100644
--- a/READMEs/README.pt-BR.md
+++ b/READMEs/README.pt-BR.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -439,7 +439,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code sem instalar o plugin (caminho MCP standalone)
-Se você cabear o servidor MCP do agentmemory via `~/.claude.json` diretamente em vez de usar `/plugin install`, o Claude Code nunca resolve `${CLAUDE_PLUGIN_ROOT}` e você tem que apontar os scripts de hook para caminhos absolutos em `~/.claude/settings.json`. Esses caminhos tipicamente embutem a versão do agentmemory (ex.: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), então a próxima atualização quebra silenciosamente todos os hooks.
+Se você cabear o servidor MCP do agentmemory via `~/.claude.json` (caminho padrão) diretamente em vez de usar `/plugin install`, o Claude Code nunca resolve `${CLAUDE_PLUGIN_ROOT}` e você tem que apontar os scripts de hook para caminhos absolutos em `~/.claude/settings.json` (caminho padrão). Esses caminhos tipicamente embutem a versão do agentmemory (ex.: `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), então a próxima atualização quebra silenciosamente todos os hooks.
Contorno:
@@ -447,7 +447,9 @@ Contorno:
agentmemory connect claude-code --with-hooks
```
-Isso mescla os mesmos comandos de hook em `~/.claude/settings.json` com caminhos absolutos resolvidos para o diretório `plugin/` empacotado do pacote `@agentmemory/agentmemory` atualmente instalado. Rode o comando novamente após atualizar o agentmemory para atualizar os caminhos. Entradas de usuário no mesmo arquivo são preservadas; apenas entradas anteriores do agentmemory são substituídas. Usar o caminho `/plugin install` continua sendo a abordagem recomendada.
+Este comando configura o servidor MCP e mescla os hooks incluídos à configuração de usuário do Claude Code. Se `CLAUDE_CONFIG_DIR` não estiver definida, estiver vazia ou contiver apenas espaços em branco, ele usa `~/.claude.json` para MCP e `~/.claude/settings.json` para hooks. Os demais valores de diretório são usados exatamente como fornecidos, incluindo espaços em branco no início e no fim. Para usar um diretório personalizado, defina `CLAUDE_CONFIG_DIR` com o mesmo valor não vazio para este comando e para o Claude Code; os arquivos serão então `$CLAUDE_CONFIG_DIR/.claude.json` e `$CLAUDE_CONFIG_DIR/settings.json`, respectivamente. O Claude Code deve receber esse valor no ambiente em que é iniciado, mesmo que o conector o leia do arquivo `.env` do AgentMemory. Crie o diretório personalizado antes de executar este comando; caso contrário, o conector ignora o Claude Code por não detectá-lo. Se o valor no shell contiver apenas espaços em branco, remova `CLAUDE_CONFIG_DIR` do ambiente antes de iniciar o Claude Code para que ele também use o perfil padrão. Use um caminho absoluto. Caminhos relativos são resolvidos a partir do diretório de trabalho, portanto os dois comandos devem ser executados no mesmo diretório.
+
+Os comandos dos hooks usam caminhos absolutos para o diretório `plugin/` incluído no pacote instalado. Execute o comando novamente após atualizar o agentmemory para atualizar esses caminhos. As entradas de usuário nos arquivos de configuração são preservadas; apenas as entradas anteriores do agentmemory são substituídas. O uso de `/plugin install` continua sendo a abordagem recomendada.
Para deploys remotos ou protegidos, inicie o Claude Code com `AGENTMEMORY_URL` e `AGENTMEMORY_SECRET` definidos. O plugin repassa ambos os valores para seu servidor MCP empacotado; quando `AGENTMEMORY_URL` está vazio, o shim MCP usa `http://localhost:3111`.
### Codex CLI (plataforma de plugins do Codex)
@@ -556,7 +558,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Guia completo: [`integrations/hermes/`](../integrations/hermes/)
@@ -653,7 +655,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory roda no Windows 10/11. O WSL2 segue o caminho Linux e pode instalar o engine fixado automaticamente. O Windows nativo exige a instalação manual do binário iii-engine v0.25.0 fixado; baixe o arquivo correspondente na [página de releases do iii 0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), confira o checksum e coloque `iii.exe` no `PATH` (por exemplo, `%USERPROFILE%\.local\bin\iii.exe`). O CLI não extrai o ZIP do Windows automaticamente.
+agentmemory roda no Windows 10/11. O WSL2 segue o caminho Linux e pode instalar o engine fixado automaticamente. O Windows nativo exige a instalação manual do binário iii-engine v0.25.1 fixado; baixe o arquivo correspondente na [página de releases do iii 0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), confira o checksum e coloque `iii.exe` no `PATH` (por exemplo, `%USERPROFILE%\.local\bin\iii.exe`). O CLI não extrai o ZIP do Windows automaticamente.
A configuração MCP automatizada no Windows nativo dá suporte apenas a `agentmemory connect copilot-cli`. Para os outros agentes nativos do Windows, use o bloco MCP manual em [Outros agentes](#other-agents). Rode `connect` no WSL somente quando o agente de destino estiver instalado no mesmo ambiente WSL.
@@ -1166,7 +1168,7 @@ A referência completa está em [`.env.example`](../.env.example): credenciais,
-146 endpoints na porta `3111`. A REST API faz bind em `127.0.0.1` por padrão. Endpoints protegidos exigem `Authorization: Bearer `, e endpoints de mesh sync exigem um `AGENTMEMORY_SECRET` explicitamente definido em ambos os peers.
+147 endpoints na porta `3111`. A REST API faz bind em `127.0.0.1` por padrão. Endpoints protegidos exigem `Authorization: Bearer `, e endpoints de mesh sync exigem um `AGENTMEMORY_SECRET` explicitamente definido em ambos os peers.
**A autenticação vem ativada por padrão.** Quando `AGENTMEMORY_SECRET` não está definida na shell nem em `~/.agentmemory/.env`, a CLI gera um segredo aleatório na primeira execução em `~/.agentmemory/secret` e grava uma cópia chamada `secret` no diretório de dados selecionado, com permissões `0600`. Todos os clientes empacotados o leem de lá ao falar com um servidor local: CLI, viewer, hooks em `plugin/scripts`, servidor MCP e shim `@agentmemory/mcp`, configurações escritas por `agentmemory connect` e integrações empacotadas de OpenCode, Pi, OpenClaw, Hermes e filesystem-watcher. O secret armazenado só é enviado para URLs de loopback (`localhost`, `127.0.0.0/8`, `::1`). Um `AGENTMEMORY_SECRET` explícito sempre prevalece, e clientes remotos precisam ter o secret definido em seu ambiente. Deploys self-hosted com Docker baseados no repositório e os entrypoints de `deploy/` geram e exportam seu próprio secret. Para chamar a API manualmente:
@@ -1247,7 +1249,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.pt-PT.md b/READMEs/README.pt-PT.md
index 0b57b1b8db..91747393a5 100644
--- a/READMEs/README.pt-PT.md
+++ b/READMEs/README.pt-PT.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code sem instalar o plugin (caminho MCP standalone)
-Se ligar o servidor MCP do agentmemory através de `~/.claude.json` diretamente, em vez de usar `/plugin install`, o Claude Code nunca resolve `${CLAUDE_PLUGIN_ROOT}` e tem de apontar os scripts de hook para caminhos absolutos em `~/.claude/settings.json`. Esses caminhos normalmente incorporam a versão do agentmemory (por exemplo, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), por isso a atualização seguinte quebra silenciosamente todos os hooks.
+Se ligar o servidor MCP do agentmemory através de `~/.claude.json` (caminho predefinido) diretamente, em vez de usar `/plugin install`, o Claude Code nunca resolve `${CLAUDE_PLUGIN_ROOT}` e tem de apontar os scripts de hook para caminhos absolutos em `~/.claude/settings.json` (caminho predefinido). Esses caminhos normalmente incorporam a versão do agentmemory (por exemplo, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), por isso a atualização seguinte quebra silenciosamente todos os hooks.
Solução alternativa:
@@ -449,7 +449,9 @@ Solução alternativa:
agentmemory connect claude-code --with-hooks
```
-Isto combina os mesmos comandos de hook em `~/.claude/settings.json` com caminhos absolutos resolvidos para o diretório `plugin/` empacotado do pacote `@agentmemory/agentmemory` atualmente instalado. Volte a executar o comando depois de atualizar o agentmemory para atualizar os caminhos. As entradas do utilizador no mesmo ficheiro são preservadas; só as entradas anteriores do agentmemory são substituídas. Usar o caminho `/plugin install` continua a ser a abordagem recomendada.
+Este comando configura o servidor MCP e funde os hooks incluídos com a configuração de utilizador do Claude Code. Se `CLAUDE_CONFIG_DIR` não estiver definida, estiver vazia ou contiver apenas espaços em branco, usa `~/.claude.json` para MCP e `~/.claude/settings.json` para os hooks. Os restantes valores de diretório são usados exatamente como fornecidos, incluindo espaços em branco no início e no fim. Para usar um diretório personalizado, defina `CLAUDE_CONFIG_DIR` com o mesmo valor não vazio para este comando e para o Claude Code; os ficheiros serão então `$CLAUDE_CONFIG_DIR/.claude.json` e `$CLAUDE_CONFIG_DIR/settings.json`, respetivamente. O Claude Code tem de receber este valor no seu ambiente de arranque, mesmo que o conector o leia do ficheiro `.env` do AgentMemory. Crie o diretório personalizado antes de executar este comando; caso contrário, o conector ignora o Claude Code por não o detetar. Se o valor na shell contiver apenas espaços em branco, remova `CLAUDE_CONFIG_DIR` do ambiente antes de iniciar o Claude Code para que também use o perfil predefinido. Utilize um caminho absoluto. Os caminhos relativos são resolvidos a partir do diretório de trabalho, pelo que ambos os comandos têm de ser executados no mesmo diretório.
+
+Os comandos dos hooks usam caminhos absolutos para o diretório `plugin/` incluído no pacote instalado. Volte a executar o comando depois de atualizar o agentmemory para atualizar esses caminhos. As entradas do utilizador nos ficheiros de configuração são preservadas; só as entradas anteriores do agentmemory são substituídas. O uso de `/plugin install` continua a ser a abordagem recomendada.
Para implementações remotas ou protegidas, inicie o Claude Code com `AGENTMEMORY_URL` e `AGENTMEMORY_SECRET` definidas. O plugin passa ambos os valores ao seu servidor MCP empacotado; quando `AGENTMEMORY_URL` está vazia, o shim MCP usa `http://localhost:3111`.
### Codex CLI (plataforma de plugins do Codex)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Guia completo: [`integrations/hermes/`](../integrations/hermes/)
@@ -655,7 +657,7 @@ npm install && npm run build && npm start
### Windows
-O agentmemory funciona no Windows 10/11. O WSL2 segue o caminho Linux e pode instalar automaticamente o engine fixado. O Windows nativo exige que o binário iii-engine v0.25.0 fixado seja instalado manualmente; descarregue o ficheiro correspondente na [página de lançamento iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verifique o checksum e coloque `iii.exe` no `PATH` (por exemplo, `%USERPROFILE%\.local\bin\iii.exe`). O CLI não extrai automaticamente o ZIP do Windows.
+O agentmemory funciona no Windows 10/11. O WSL2 segue o caminho Linux e pode instalar automaticamente o engine fixado. O Windows nativo exige que o binário iii-engine v0.25.1 fixado seja instalado manualmente; descarregue o ficheiro correspondente na [página de lançamento iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verifique o checksum e coloque `iii.exe` no `PATH` (por exemplo, `%USERPROFILE%\.local\bin\iii.exe`). O CLI não extrai automaticamente o ZIP do Windows.
A ligação MCP automatizada no Windows nativo só suporta `agentmemory connect copilot-cli`. Para os restantes agentes nativos do Windows, use o bloco MCP manual de [Outros agentes](#other-agents). Execute `connect` no WSL apenas quando o agente de destino também estiver instalado nesse mesmo ambiente WSL.
@@ -1162,7 +1164,7 @@ A referência completa está em [`.env.example`](../.env.example): credenciais,
-146 endpoints na porta `3111`. A REST API faz bind em `127.0.0.1` por predefinição. Os endpoints protegidos exigem `Authorization: Bearer `, e os endpoints de sincronização mesh exigem uma `AGENTMEMORY_SECRET` explicitamente definida em ambos os pares.
+147 endpoints na porta `3111`. A REST API faz bind em `127.0.0.1` por predefinição. Os endpoints protegidos exigem `Authorization: Bearer `, e os endpoints de sincronização mesh exigem uma `AGENTMEMORY_SECRET` explicitamente definida em ambos os pares.
**A autenticação está ativa por predefinição.** Quando `AGENTMEMORY_SECRET` não está definida na shell nem em `~/.agentmemory/.env`, o CLI gera um segredo aleatório no primeiro arranque em `~/.agentmemory/secret` e guarda uma cópia chamada `secret` no diretório de dados selecionado, com permissões `0600`. Todos os clientes incluídos o leem daí quando comunicam com um servidor local: o CLI, o visualizador, os hooks em `plugin/scripts`, o servidor MCP e o shim `@agentmemory/mcp`, as configurações escritas por `agentmemory connect`, e as integrações incluídas de OpenCode, Pi, OpenClaw, Hermes e filesystem-watcher. O segredo guardado só é enviado para URLs de loopback (`localhost`, `127.0.0.0/8`, `::1`). Uma `AGENTMEMORY_SECRET` explícita prevalece sempre, e os clientes remotos precisam de ter o segredo definido no seu ambiente. As implementações Docker self-host a partir do repositório e os entrypoints de `deploy/` geram e exportam o seu próprio segredo. Para chamar a API manualmente:
@@ -1243,7 +1245,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ro-RO.md b/READMEs/README.ro-RO.md
index 3e1f4c5870..d6173acd64 100644
--- a/READMEs/README.ro-RO.md
+++ b/READMEs/README.ro-RO.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code fără instalarea plugin-ului (cale MCP independentă)
-Dacă conectezi serverul MCP al agentmemory direct prin `~/.claude.json`, în loc să folosești `/plugin install`, Claude Code nu rezolvă niciodată `${CLAUDE_PLUGIN_ROOT}` și trebuie să indici scripturile de hook prin căi absolute în `~/.claude/settings.json`. Aceste căi includ de obicei versiunea agentmemory (de ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), astfel încât următoarea actualizare rupe silențios fiecare hook.
+Dacă conectezi serverul MCP al agentmemory direct prin `~/.claude.json` (cale implicită), în loc să folosești `/plugin install`, Claude Code nu rezolvă niciodată `${CLAUDE_PLUGIN_ROOT}` și trebuie să indici scripturile de hook prin căi absolute în `~/.claude/settings.json` (cale implicită). Aceste căi includ de obicei versiunea agentmemory (de ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), astfel încât următoarea actualizare rupe silențios fiecare hook.
Soluție alternativă:
@@ -454,7 +454,9 @@ Soluție alternativă:
agentmemory connect claude-code --with-hooks
```
-Aceasta îmbină aceleași comenzi de hook în `~/.claude/settings.json`, cu căi absolute rezolvate către directorul `plugin/` inclus în pachetul `@agentmemory/agentmemory` instalat curent. Rulează din nou comanda după actualizarea agentmemory, pentru a reîmprospăta căile. Intrările proprii ale utilizatorului din același fișier sunt păstrate; sunt înlocuite doar intrările anterioare ale agentmemory. Folosirea căii `/plugin install` rămâne abordarea recomandată.
+Această comandă configurează serverul MCP și îmbină hook-urile incluse cu configurația de utilizator a Claude Code. Dacă `CLAUDE_CONFIG_DIR` nu este setată, este goală sau conține doar spații albe, folosește `~/.claude.json` pentru MCP și `~/.claude/settings.json` pentru hook-uri. Celelalte valori de director sunt folosite exact așa cum sunt furnizate, inclusiv spațiile albe de la început și de la sfârșit. Pentru un director personalizat, setați `CLAUDE_CONFIG_DIR` la aceeași valoare nevidă atât pentru această comandă, cât și pentru Claude Code; fișierele vor fi atunci `$CLAUDE_CONFIG_DIR/.claude.json` și, respectiv, `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code trebuie să primească această valoare în mediul său de pornire, chiar dacă conectorul o citește din fișierul `.env` al AgentMemory. Creați directorul personalizat înainte de a rula această comandă; altfel, conectorul omite Claude Code deoarece nu îl detectează. Dacă valoarea din shell conține doar spații albe, eliminați `CLAUDE_CONFIG_DIR` din mediu înainte de a porni Claude Code, pentru ca și acesta să folosească profilul implicit. Folosește o cale absolută. Căile relative sunt interpretate pornind de la directorul de lucru, deci ambele comenzi trebuie executate din același director.
+
+Comenzile hook-urilor folosesc căi absolute către directorul `plugin/` inclus în pachetul instalat. Rulați din nou comanda după actualizarea agentmemory pentru a reîmprospăta aceste căi. Intrările utilizatorului din fișierele de configurare sunt păstrate; sunt înlocuite doar intrările anterioare ale agentmemory. Utilizarea `/plugin install` rămâne abordarea recomandată.
Pentru deployment-uri la distanță sau protejate, pornește Claude Code cu `AGENTMEMORY_URL` și `AGENTMEMORY_SECRET` setate. Plugin-ul transmite ambele valori către serverul MCP inclus; când `AGENTMEMORY_URL` este gol, shim-ul MCP folosește `http://localhost:3111`.
### Codex CLI (platforma de plugin-uri Codex)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Ghid complet: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory rulează pe Windows 10/11. WSL2 urmează calea Linux și poate instala automat engine-ul fixat. Windows nativ necesită instalarea manuală a binarului iii-engine v0.25.0 fixat; descarcă arhiva potrivită de pe [pagina de release iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verifică checksum-ul și pune `iii.exe` în `PATH` (de exemplu `%USERPROFILE%\.local\bin\iii.exe`). CLI-ul nu extrage automat arhiva ZIP pentru Windows.
+agentmemory rulează pe Windows 10/11. WSL2 urmează calea Linux și poate instala automat engine-ul fixat. Windows nativ necesită instalarea manuală a binarului iii-engine v0.25.1 fixat; descarcă arhiva potrivită de pe [pagina de release iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verifică checksum-ul și pune `iii.exe` în `PATH` (de exemplu `%USERPROFILE%\.local\bin\iii.exe`). CLI-ul nu extrage automat arhiva ZIP pentru Windows.
Conectarea MCP automatizată pe Windows nativ acceptă doar `agentmemory connect copilot-cli`. Pentru ceilalți agenți nativi Windows, folosește blocul MCP manual din [Alți agenți](#other-agents). Rulează `connect` în WSL doar când agentul țintă este instalat în același mediu WSL.
@@ -1154,7 +1156,7 @@ Referința completă [`.env.example`](../.env.example) include furnizori, filtre
-146 de endpoint-uri pe portul `3111`. API-ul REST se leagă implicit la `127.0.0.1`. Endpoint-urile protejate necesită `Authorization: Bearer `, iar endpoint-urile de sincronizare mesh necesită un `AGENTMEMORY_SECRET` setat explicit pe ambii parteneri (peers).
+147 de endpoint-uri pe portul `3111`. API-ul REST se leagă implicit la `127.0.0.1`. Endpoint-urile protejate necesită `Authorization: Bearer `, iar endpoint-urile de sincronizare mesh necesită un `AGENTMEMORY_SECRET` setat explicit pe ambii parteneri (peers).
**Autentificarea este activată implicit.** Dacă `AGENTMEMORY_SECRET` nu este setat, CLI-ul generează la prima pornire un secret aleatoriu în `~/.agentmemory/secret`, cu permisiuni `0600`, și îl copiază și în directorul de date selectat. Toți clienții incluși îl citesc de acolo când comunică cu un server local: CLI-ul, vizualizatorul, hook-urile din `plugin/scripts`, serverul MCP și shim-ul `@agentmemory/mcp`, configurațiile scrise de `agentmemory connect` și integrările incluse OpenCode, Pi, OpenClaw, Hermes și filesystem-watcher. Secretul stocat este trimis doar către URL-uri loopback (`localhost`, `127.0.0.0/8`, `::1`). Un `AGENTMEMORY_SECRET` explicit are întotdeauna prioritate, iar clienții la distanță trebuie să seteze secretul în mediul lor. Implementările Docker self-host pornite din repository și entrypoint-urile `deploy/` își generează și exportă propriul secret. Pentru a apela API-ul manual:
@@ -1235,7 +1237,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ru-RU.md b/READMEs/README.ru-RU.md
index 3ea4e5de29..be1e91e4e4 100644
--- a/READMEs/README.ru-RU.md
+++ b/READMEs/README.ru-RU.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code без установки плагина (путь MCP-standalone)
-Если подключать MCP-сервер agentmemory через `~/.claude.json` напрямую, минуя `/plugin install`, Claude Code никогда не разрешит `${CLAUDE_PLUGIN_ROOT}`, и в `~/.claude/settings.json` придётся прописывать абсолютные пути к скриптам хуков. Эти пути обычно включают версию agentmemory (например, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), так что следующее обновление тихо ломает каждый хук.
+Если подключать MCP-сервер agentmemory через `~/.claude.json` (путь по умолчанию) напрямую, минуя `/plugin install`, Claude Code никогда не разрешит `${CLAUDE_PLUGIN_ROOT}`, и в `~/.claude/settings.json` (путь по умолчанию) придётся прописывать абсолютные пути к скриптам хуков. Эти пути обычно включают версию agentmemory (например, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), так что следующее обновление тихо ломает каждый хук.
Обходное решение:
@@ -454,7 +454,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-Это вливает те же команды хуков в `~/.claude/settings.json` с абсолютными путями, разрешёнными в каталог `plugin/` текущего установленного пакета `@agentmemory/agentmemory`. После обновления agentmemory запустите команду ещё раз, чтобы освежить пути. Записи пользователя в этом файле сохраняются; заменяются только предыдущие записи agentmemory. Рекомендуемым способом остаётся путь через `/plugin install`.
+Эта команда настраивает MCP-сервер и добавляет поставляемые с пакетом хуки в пользовательскую конфигурацию Claude Code. Если `CLAUDE_CONFIG_DIR` не задана, пуста или содержит только пробельные символы, для MCP используется `~/.claude.json`, а для хуков — `~/.claude/settings.json`. Остальные значения каталога используются без изменений, включая пробельные символы в начале и конце. Чтобы использовать свой каталог, задайте одинаковое непустое значение `CLAUDE_CONFIG_DIR` для этой команды и Claude Code; тогда файлы будут находиться в `$CLAUDE_CONFIG_DIR/.claude.json` и `$CLAUDE_CONFIG_DIR/settings.json` соответственно. Claude Code должен получить это значение в своём окружении при запуске, даже если коннектор читает его из файла `.env` AgentMemory. Создайте свой каталог перед выполнением этой команды; иначе коннектор пропустит Claude Code как не обнаруженный. Если значение в оболочке содержит только пробельные символы, удалите `CLAUDE_CONFIG_DIR` из окружения перед запуском Claude Code, чтобы он также использовал профиль по умолчанию. Используйте абсолютный путь. Относительные пути разрешаются от рабочего каталога, поэтому обе команды нужно запускать из одного каталога.
+
+Команды хуков используют абсолютные пути к каталогу `plugin/` из установленного пакета. После обновления agentmemory запустите команду ещё раз, чтобы обновить эти пути. Пользовательские записи в файлах конфигурации сохраняются; заменяются только предыдущие записи agentmemory. Использование `/plugin install` остаётся рекомендуемым способом.
Для удалённых или защищённых развёртываний запускайте Claude Code с заданными `AGENTMEMORY_URL` и `AGENTMEMORY_SECRET`. Плагин пробрасывает оба значения во встроенный MCP-сервер; если `AGENTMEMORY_URL` пуст, MCP-shim использует `http://localhost:3111`.
### Codex CLI (платформа плагинов Codex)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Полное руководство: [`integrations/hermes/`](../integrations/hermes/)
@@ -664,7 +666,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory работает на Windows 10/11. В WSL2 используется путь Linux, и закреплённый движок устанавливается автоматически. Для нативной работы в Windows требуется вручную установить закреплённый бинарь iii-engine v0.25.0: скачайте подходящий архив со [страницы релиза iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), проверьте контрольную сумму и поместите `iii.exe` в `PATH` (например, `%USERPROFILE%\.local\bin\iii.exe`). CLI не распаковывает Windows ZIP автоматически.
+agentmemory работает на Windows 10/11. В WSL2 используется путь Linux, и закреплённый движок устанавливается автоматически. Для нативной работы в Windows требуется вручную установить закреплённый бинарь iii-engine v0.25.1: скачайте подходящий архив со [страницы релиза iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), проверьте контрольную сумму и поместите `iii.exe` в `PATH` (например, `%USERPROFILE%\.local\bin\iii.exe`). CLI не распаковывает Windows ZIP автоматически.
Автоматизированное подключение MCP в нативной Windows поддерживает только `agentmemory connect copilot-cli`. Для других нативных Windows-агентов используйте ручной блок MCP из раздела [Другие агенты](#other-agents). Запускайте `connect` внутри WSL только если целевой агент установлен в той же среде WSL.
@@ -1160,7 +1162,7 @@ EMBEDDING_PROVIDER=local
-146 эндпоинтов на порту `3111`. REST API по умолчанию слушает на `127.0.0.1`. Защищённые эндпоинты требуют `Authorization: Bearer `, а эндпоинты mesh-синхронизации требуют явно заданного `AGENTMEMORY_SECRET` на обоих узлах.
+147 эндпоинтов на порту `3111`. REST API по умолчанию слушает на `127.0.0.1`. Защищённые эндпоинты требуют `Authorization: Bearer `, а эндпоинты mesh-синхронизации требуют явно заданного `AGENTMEMORY_SECRET` на обоих узлах.
**Аутентификация включена по умолчанию.** Если `AGENTMEMORY_SECRET` не задан, при первом запуске CLI создаёт случайный секрет в `~/.agentmemory/secret` с правами `0600` и копирует его также в выбранный каталог данных. Каждый встроенный клиент читает его оттуда, когда говорит с локальным сервером: CLI, просмотрщик, хуки из `plugin/scripts`, MCP-сервер и shim `@agentmemory/mcp`, конфиги, записанные `agentmemory connect`, и встроенные интеграции OpenCode, Pi, OpenClaw, Hermes и filesystem-watcher. Сохранённый секрет отправляется только на loopback-адреса (`localhost`, `127.0.0.0/8`, `::1`). Явно заданный `AGENTMEMORY_SECRET` всегда выигрывает, и удалённым клиентам он всё равно нужен. Docker и entrypoint'ы `deploy/` уже генерируют и экспортируют собственный секрет. Чтобы вызвать API вручную:
@@ -1241,7 +1243,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.sv-SE.md b/READMEs/README.sv-SE.md
index 3c3e72e866..82f04762eb 100644
--- a/READMEs/README.sv-SE.md
+++ b/READMEs/README.sv-SE.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -441,7 +441,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code utan plugin-installationen (fristående MCP-väg)
-Om du kopplar in agentmemorys MCP-server via `~/.claude.json` direkt istället för att använda `/plugin install`, löser Claude Code aldrig upp `${CLAUDE_PLUGIN_ROOT}`, och du måste peka hook-skripten mot absoluta sökvägar i `~/.claude/settings.json`. Dessa sökvägar innehåller vanligtvis agentmemory-versionen (t.ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så nästa uppgradering bryter varje hook i det tysta.
+Om du kopplar in agentmemorys MCP-server via `~/.claude.json` (standardsökväg) direkt istället för att använda `/plugin install`, löser Claude Code aldrig upp `${CLAUDE_PLUGIN_ROOT}`, och du måste peka hook-skripten mot absoluta sökvägar i `~/.claude/settings.json` (standardsökväg). Dessa sökvägar innehåller vanligtvis agentmemory-versionen (t.ex. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), så nästa uppgradering bryter varje hook i det tysta.
Lösning:
@@ -449,7 +449,9 @@ Lösning:
agentmemory connect claude-code --with-hooks
```
-Detta slår samman samma hook-kommandon i `~/.claude/settings.json` med absoluta sökvägar som löses upp till den medföljande `plugin/`-katalogen i det för tillfället installerade paketet `@agentmemory/agentmemory`. Kör kommandot igen efter att du har uppgraderat agentmemory för att uppdatera sökvägarna. Användarens egna poster i samma fil bevaras; endast tidigare agentmemory-poster ersätts. Att använda vägen `/plugin install` är fortfarande den rekommenderade metoden.
+Det här kommandot konfigurerar MCP-servern och slår samman de medföljande hookarna med Claude Codes användarkonfiguration. Om `CLAUDE_CONFIG_DIR` inte är satt, är tom eller bara innehåller blanktecken används `~/.claude.json` för MCP och `~/.claude/settings.json` för hooks. Övriga katalogvärden används exakt som de anges, inklusive inledande och avslutande blanktecken. För en egen katalog ställer du in `CLAUDE_CONFIG_DIR` till samma icke-tomma värde för både det här kommandot och Claude Code; filerna blir då `$CLAUDE_CONFIG_DIR/.claude.json` respektive `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code måste få värdet i sin startmiljö, även om anslutningsmodulen läser det från AgentMemorys `.env`. Skapa den egna katalogen innan du kör kommandot; annars hoppar anslutningsmodulen över Claude Code eftersom det inte upptäcks. Om värdet i skalet bara innehåller blanktecken tar du bort `CLAUDE_CONFIG_DIR` från miljön innan du startar Claude Code, så att det också använder standardprofilen. Använd en absolut sökväg. Relativa sökvägar utgår från arbetskatalogen, så båda kommandona måste köras från samma katalog.
+
+Hook-kommandona använder absoluta sökvägar till det installerade paketets medföljande katalog `plugin/`. Kör kommandot igen efter en uppgradering av agentmemory för att uppdatera sökvägarna. Användarens egna poster i konfigurationsfilerna bevaras; bara tidigare agentmemory-poster ersätts. Att använda `/plugin install` är fortfarande det rekommenderade sättet.
För fjärr- eller skyddade driftsättningar, starta Claude Code med `AGENTMEMORY_URL` och `AGENTMEMORY_SECRET` satta. Plugin-programmet skickar båda värdena vidare till sin medföljande MCP-server; när `AGENTMEMORY_URL` är tomt använder MCP-shimmen `http://localhost:3111`.
### Codex CLI (Codex-plugin-plattformen)
@@ -558,7 +560,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Fullständig guide: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory körs på Windows 10/11. WSL2 följer Linux-vägen och kan installera den fastlåsta enginen automatiskt. Native Windows kräver att den fastlåsta iii-engine v0.25.0-binären installeras manuellt: ladda ner rätt arkiv från [iii v0.25.0-utgåvan](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), verifiera kontrollsumman och placera `iii.exe` på `PATH` (till exempel `%USERPROFILE%\.local\bin\iii.exe`). CLI:n packar inte upp Windows-ZIP-filen automatiskt.
+agentmemory körs på Windows 10/11. WSL2 följer Linux-vägen och kan installera den fastlåsta enginen automatiskt. Native Windows kräver att den fastlåsta iii-engine v0.25.1-binären installeras manuellt: ladda ner rätt arkiv från [iii v0.25.1-utgåvan](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), verifiera kontrollsumman och placera `iii.exe` på `PATH` (till exempel `%USERPROFILE%\.local\bin\iii.exe`). CLI:n packar inte upp Windows-ZIP-filen automatiskt.
Automatiserad MCP-inkoppling på native Windows stöder bara `agentmemory connect copilot-cli`. För andra native Windows-agenter använder du det manuella MCP-blocket från [Andra agenter](#other-agents). Kör `connect` i WSL endast om målagenten är installerad i samma WSL-miljö.
@@ -1168,7 +1170,7 @@ Den fullständiga referensen finns i [`.env.example`](../.env.example): autentis
-146 endpoints på port `3111`. REST API:et binder till `127.0.0.1` som standard. Skyddade endpoints kräver `Authorization: Bearer `, och mesh-synk-endpoints kräver en explicit satt `AGENTMEMORY_SECRET` på båda parterna.
+147 endpoints på port `3111`. REST API:et binder till `127.0.0.1` som standard. Skyddade endpoints kräver `Authorization: Bearer `, och mesh-synk-endpoints kräver en explicit satt `AGENTMEMORY_SECRET` på båda parterna.
**Autentisering är aktiverad som standard.** Om `AGENTMEMORY_SECRET` inte är angiven i skalet eller i `~/.agentmemory/.env` skapar CLI:n en slumpmässig hemlighet vid första starten i `~/.agentmemory/secret` och en kopia med namnet `secret` i den valda datamappen, med filbehörigheten `0600`. Alla medföljande klienter läser den därifrån när de ansluter till en lokal server: CLI:n, viewern, hookarna under `plugin/scripts`, MCP-servern och `@agentmemory/mcp`-shimmen, konfigurationerna skrivna av `agentmemory connect` samt de medföljande integrationerna för OpenCode, Pi, OpenClaw, Hermes och filsystemsbevakaren. Den lagrade hemligheten skickas bara till loopback-URL:er (`localhost`, `127.0.0.0/8`, `::1`). En explicit `AGENTMEMORY_SECRET` har alltid företräde; fjärrklienter behöver hemligheten i sin miljö. Docker-baserad self-hosting från repot och startpunkterna i `deploy/` genererar och exporterar en egen hemlighet. För att anropa API:et för hand:
@@ -1249,7 +1251,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.th-TH.md b/READMEs/README.th-TH.md
index 76671822b6..c93db2f895 100644
--- a/READMEs/README.th-TH.md
+++ b/READMEs/README.th-TH.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -438,7 +438,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code without the plugin install (MCP-standalone path)
-ถ้าคุณเชื่อมต่อ MCP server ของ agentmemory ผ่าน `~/.claude.json` โดยตรงแทนการใช้ `/plugin install`, Claude Code จะไม่ resolve `${CLAUDE_PLUGIN_ROOT}` เลย และคุณต้องชี้ hook script ไปที่ absolute path ใน `~/.claude/settings.json` path เหล่านั้นมักจะฝังเวอร์ชันของ agentmemory ไว้ด้วย (เช่น `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`) ดังนั้นการ upgrade ครั้งต่อไปจะทำให้ hook ทุกตัวพังแบบไม่มีเสียงเตือน
+ถ้าคุณเชื่อมต่อ MCP server ของ agentmemory ผ่าน `~/.claude.json` (เส้นทางเริ่มต้น) โดยตรงแทนการใช้ `/plugin install`, Claude Code จะไม่ resolve `${CLAUDE_PLUGIN_ROOT}` เลย และคุณต้องชี้ hook script ไปที่ absolute path ใน `~/.claude/settings.json` (เส้นทางเริ่มต้น) path เหล่านั้นมักจะฝังเวอร์ชันของ agentmemory ไว้ด้วย (เช่น `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`) ดังนั้นการ upgrade ครั้งต่อไปจะทำให้ hook ทุกตัวพังแบบไม่มีเสียงเตือน
วิธีแก้:
@@ -446,7 +446,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-คำสั่งนี้จะ merge คำสั่ง hook เดียวกันเข้าไปใน `~/.claude/settings.json` โดยใช้ absolute path ที่ resolve ไปยัง directory `plugin/` ที่แพ็กเกจ `@agentmemory/agentmemory` เวอร์ชันที่ติดตั้งอยู่ในปัจจุบัน ให้รันคำสั่งนี้ซ้ำอีกครั้งหลัง upgrade agentmemory เพื่อ refresh path รายการของผู้ใช้ในไฟล์เดียวกันจะยังคงอยู่ มีเพียงรายการของ agentmemory เดิมที่จะถูกแทนที่ การใช้เส้นทาง `/plugin install` ยังคงเป็นวิธีที่แนะนำ
+คำสั่งนี้กำหนดค่าเซิร์ฟเวอร์ MCP และรวม hook ที่ให้มากับแพ็กเกจเข้ากับการกำหนดค่าผู้ใช้ของ Claude Code หากไม่ได้ตั้งค่า `CLAUDE_CONFIG_DIR` มีค่าว่าง หรือมีแต่ช่องว่าง จะใช้ `~/.claude.json` สำหรับ MCP และ `~/.claude/settings.json` สำหรับ hook ค่าไดเรกทอรีอื่นจะถูกใช้ตามที่ระบุทุกตัวอักษร รวมถึงช่องว่างที่ต้นและท้ายค่า หากต้องการใช้ไดเรกทอรีที่กำหนดเอง ให้ตั้งค่า `CLAUDE_CONFIG_DIR` เป็นค่าเดียวกันที่ไม่ว่างทั้งสำหรับคำสั่งนี้และ Claude Code โดยไฟล์ที่ใช้จะเป็น `$CLAUDE_CONFIG_DIR/.claude.json` และ `$CLAUDE_CONFIG_DIR/settings.json` ตามลำดับ Claude Code ต้องได้รับค่านี้ในสภาพแวดล้อมที่ใช้เริ่มโปรแกรม แม้ว่าตัวเชื่อมต่อจะอ่านค่าจากไฟล์ `.env` ของ AgentMemory ก็ตาม สร้างไดเรกทอรีที่กำหนดเองก่อนรันคำสั่งนี้ มิฉะนั้นตัวเชื่อมต่อจะข้าม Claude Code เนื่องจากตรวจไม่พบ หากค่าใน shell มีแต่ช่องว่าง ให้ยกเลิกการตั้งค่า `CLAUDE_CONFIG_DIR` ก่อนเริ่ม Claude Code เพื่อให้ใช้โปรไฟล์เริ่มต้นเช่นกัน ใช้พาธแบบสัมบูรณ์ พาธแบบสัมพัทธ์จะอ้างอิงจากไดเรกทอรีทำงาน ดังนั้นต้องเรียกใช้ทั้งสองคำสั่งจากไดเรกทอรีเดียวกัน
+
+คำสั่ง hook ใช้เส้นทางแบบสัมบูรณ์ไปยังไดเรกทอรี `plugin/` ที่ให้มากับแพ็กเกจที่ติดตั้ง หลังอัปเกรด agentmemory ให้รันคำสั่งนี้อีกครั้งเพื่ออัปเดตเส้นทาง รายการของผู้ใช้ในไฟล์กำหนดค่าจะยังคงอยู่ โดยจะแทนที่เฉพาะรายการเดิมของ agentmemory เท่านั้น การใช้ `/plugin install` ยังคงเป็นแนวทางที่แนะนำ
สำหรับการ deploy แบบ remote หรือแบบที่มีการป้องกัน ให้เปิด Claude Code โดยตั้งค่า `AGENTMEMORY_URL` และ `AGENTMEMORY_SECRET` ไว้ plugin จะส่งค่าทั้งสองนี้ต่อไปยัง MCP server ที่ bundle มาด้วย เมื่อ `AGENTMEMORY_URL` เป็นค่าว่าง MCP shim จะใช้ `http://localhost:3111`
### Codex CLI (Codex plugin platform)
@@ -553,7 +555,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
คู่มือฉบับเต็ม: [`integrations/hermes/`](../integrations/hermes/)
@@ -648,7 +650,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory รองรับ Windows 10/11; WSL2 ใช้ขั้นตอน Linux และติดตั้ง engine อัตโนมัติได้ Windows แบบ native ต้องติดตั้งไบนารี iii-engine v0.25.0 ด้วยตนเอง ดาวน์โหลด archive จาก [หน้า release iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), ตรวจ checksum และวาง `iii.exe` บน `PATH` (เช่น `%USERPROFILE%\.local\bin\iii.exe`) CLI ไม่แตก Windows ZIP ให้อัตโนมัติ
+agentmemory รองรับ Windows 10/11; WSL2 ใช้ขั้นตอน Linux และติดตั้ง engine อัตโนมัติได้ Windows แบบ native ต้องติดตั้งไบนารี iii-engine v0.25.1 ด้วยตนเอง ดาวน์โหลด archive จาก [หน้า release iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), ตรวจ checksum และวาง `iii.exe` บน `PATH` (เช่น `%USERPROFILE%\.local\bin\iii.exe`) CLI ไม่แตก Windows ZIP ให้อัตโนมัติ
การตั้งค่า MCP อัตโนมัติบน Windows รองรับเฉพาะ `agentmemory connect copilot-cli`; สำหรับ agent อื่นให้ใช้ MCP block ใน [Other agents](#other-agents) เรียก `connect` ใน WSL เมื่อ agent เป้าหมายติดตั้งใน WSL เดียวกันเท่านั้น
@@ -1161,7 +1163,7 @@ EMBEDDING_PROVIDER=local
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code nang walang plugin install (MCP-standalone path)
-Kung i-wire mo ang MCP server ng agentmemory gamit ang `~/.claude.json` nang direkta sa halip na gamitin ang `/plugin install`, hindi kailanman nireresolba ng Claude Code ang `${CLAUDE_PLUGIN_ROOT}` at kailangan mong ituro ang hook scripts sa absolute paths sa `~/.claude/settings.json`. Karaniwang naka-embed sa mga path na ito ang bersyon ng agentmemory (hal. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), kaya tahimik na masisira ng susunod na upgrade ang bawat hook.
+Kung i-wire mo ang MCP server ng agentmemory gamit ang `~/.claude.json` (default na path) nang direkta sa halip na gamitin ang `/plugin install`, hindi kailanman nireresolba ng Claude Code ang `${CLAUDE_PLUGIN_ROOT}` at kailangan mong ituro ang hook scripts sa absolute paths sa `~/.claude/settings.json` (default na path). Karaniwang naka-embed sa mga path na ito ang bersyon ng agentmemory (hal. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), kaya tahimik na masisira ng susunod na upgrade ang bawat hook.
Workaround:
@@ -452,7 +452,9 @@ Workaround:
agentmemory connect claude-code --with-hooks
```
-Pinagsasama nito ang parehong hook commands sa `~/.claude/settings.json` gamit ang absolute paths na nireresolba sa bundled `plugin/` directory ng kasalukuyang naka-install na `@agentmemory/agentmemory` package. Patakbuhin ulit ang command pagkatapos i-upgrade ang agentmemory para i-refresh ang mga path. Napapanatili ang mga entry ng user sa parehong file; ang mga nakaraang entry ng agentmemory lamang ang napapalitan. Ang paggamit ng `/plugin install` path ay nananatiling inirerekomendang paraan.
+Kino-configure ng command na ito ang MCP server at pinagsasama ang mga bundled hook sa user configuration ng Claude Code. Kung hindi naka-set ang `CLAUDE_CONFIG_DIR`, blangko ito, o puro whitespace ang laman, ginagamit nito ang `~/.claude.json` para sa MCP at `~/.claude/settings.json` para sa mga hook. Ginagamit ang iba pang directory value nang eksakto sa ibinigay, kasama ang whitespace sa simula at dulo. Para sa custom na directory, itakda ang `CLAUDE_CONFIG_DIR` sa parehong hindi blangkong value para sa command na ito at sa Claude Code; ang mga file ay magiging `$CLAUDE_CONFIG_DIR/.claude.json` at `$CLAUDE_CONFIG_DIR/settings.json`, ayon sa pagkakasunod. Kailangang matanggap ng Claude Code ang value na ito sa environment na ginagamit sa paglulunsad nito, kahit binabasa ito ng connector mula sa `.env` ng AgentMemory. Gawin ang custom na directory bago patakbuhin ang command na ito; kung wala ito, lalaktawan ng connector ang Claude Code dahil hindi ito ma-detect. Kung puro whitespace ang value sa shell, alisin ang `CLAUDE_CONFIG_DIR` sa environment bago ilunsad ang Claude Code para gamitin din nito ang default na profile. Gumamit ng absolute path. Ang mga relative path ay nakabatay sa working directory, kaya dapat patakbuhin ang parehong command mula sa iisang directory.
+
+Gumagamit ang mga hook command ng absolute paths patungo sa bundled na `plugin/` directory ng naka-install na package. Patakbuhin muli ang command pagkatapos i-upgrade ang agentmemory upang i-refresh ang mga path. Pinananatili ang mga entry ng user sa mga configuration file; ang mga dating entry ng agentmemory lamang ang pinapalitan. Ang paggamit ng `/plugin install` pa rin ang inirerekomendang paraan.
Para sa remote o protected deployment, patakbuhin ang Claude Code na naka-set ang `AGENTMEMORY_URL` at `AGENTMEMORY_SECRET`. Ipinapasa ng plugin ang dalawang value papunta sa bundled MCP server nito; kapag walang laman ang `AGENTMEMORY_URL`, gumagamit ang MCP shim ng `http://localhost:3111`.
### Codex CLI (Codex plugin platform)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Kumpletong gabay: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ Pinapatakbo ng `npm start` ang kaparehong local server ng naka-install na CLI. N
### Windows
-Tumatakbo ang agentmemory sa Windows 10/11. Awtomatikong nag-i-install ng engine ang WSL2 gamit ang Linux path. Sa native Windows, manu-manong i-install ang pinned na iii-engine v0.25.0: i-download ang archive mula sa [iii v0.25.0 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), tiyakin ang checksum, at ilagay ang `iii.exe` sa `PATH`. Hindi awtomatikong nag-e-extract ng ZIP ang CLI
+Tumatakbo ang agentmemory sa Windows 10/11. Awtomatikong nag-i-install ng engine ang WSL2 gamit ang Linux path. Sa native Windows, manu-manong i-install ang pinned na iii-engine v0.25.1: i-download ang archive mula sa [iii v0.25.1 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), tiyakin ang checksum, at ilagay ang `iii.exe` sa `PATH`. Hindi awtomatikong nag-e-extract ng ZIP ang CLI
Native Windows MCP automation ay para lamang sa `agentmemory connect copilot-cli`; gamitin ang manual MCP block sa [Other agents](#other-agents) para sa iba. Sa WSL, patakbuhin ang `connect` lamang kung naroon din ang target agent
@@ -1170,7 +1172,7 @@ Nasa [`.env.example`](../.env.example) ang buong reference, kasama ang provider,
-146 na endpoint sa port `3111`. Nagbibind ang REST API sa `127.0.0.1` bilang default. Kinakailangan ng mga protected endpoint ang `Authorization: Bearer `, at kinakailangan ng mga mesh sync endpoint ang tahasang naka-set na `AGENTMEMORY_SECRET` sa dalawang peer.
+147 na endpoint sa port `3111`. Nagbibind ang REST API sa `127.0.0.1` bilang default. Kinakailangan ng mga protected endpoint ang `Authorization: Bearer `, at kinakailangan ng mga mesh sync endpoint ang tahasang naka-set na `AGENTMEMORY_SECRET` sa dalawang peer.
Naka-on ang authentication bilang default. Kapag walang `AGENTMEMORY_SECRET`, gumagawa ang CLI ng random secret sa unang start sa `~/.agentmemory/secret` at kinokopya sa `secret` ng napiling data directory, na may mode `0600`. Inuuna ng bundled clients ang canonical file sa local connection at ipinapadala lang ang naka-save na secret sa loopback URL. Mas mataas ang prayoridad ng explicit na `AGENTMEMORY_SECRET`; dapat itong itakda ng remote clients sa environment. Gumagawa ang Docker deployment ng sarili nitong secret.
@@ -1251,7 +1253,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.tr-TR.md b/READMEs/README.tr-TR.md
index a5d36b5299..d4ef91d08b 100644
--- a/READMEs/README.tr-TR.md
+++ b/READMEs/README.tr-TR.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Eklenti kurulumu olmadan Claude Code (MCP-bağımsız yol)
-agentmemory'nin MCP sunucusunu `/plugin install` kullanmak yerine doğrudan `~/.claude.json` üzerinden bağlarsanız, Claude Code `${CLAUDE_PLUGIN_ROOT}`'u asla çözümlemez ve hook scriptlerini `~/.claude/settings.json` içinde absolute path'lere yöneltmeniz gerekir. Bu path'ler genellikle agentmemory sürümünü gömer (örn. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), bu yüzden bir sonraki yükseltme her hook'u sessizce bozar.
+agentmemory'nin MCP sunucusunu `/plugin install` kullanmak yerine doğrudan `~/.claude.json` (varsayılan yol) üzerinden bağlarsanız, Claude Code `${CLAUDE_PLUGIN_ROOT}`'u asla çözümlemez ve hook scriptlerini `~/.claude/settings.json` (varsayılan yol) içinde absolute path'lere yöneltmeniz gerekir. Bu path'ler genellikle agentmemory sürümünü gömer (örn. `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), bu yüzden bir sonraki yükseltme her hook'u sessizce bozar.
Geçici çözüm:
@@ -454,7 +454,9 @@ Geçici çözüm:
agentmemory connect claude-code --with-hooks
```
-Bu, aynı hook komutlarını, şu anda kurulu olan `@agentmemory/agentmemory` paketinin paketlenmiş `plugin/` dizinine çözümlenen absolute path'lerle `~/.claude/settings.json` içine birleştirir. Path'leri yenilemek için agentmemory'yi yükselttikten sonra komutu yeniden çalıştırın. Aynı dosyadaki kullanıcı girdileri korunur; yalnızca önceki agentmemory girdileri değiştirilir. `/plugin install` yolunu kullanmak, önerilen yaklaşım olmayı sürdürür.
+Bu komut MCP sunucusunu yapılandırır ve paketle gelen hook’ları Claude Code’un kullanıcı yapılandırmasına birleştirir. `CLAUDE_CONFIG_DIR` ayarlanmamışsa, boşsa veya yalnızca boşluk karakterleri içeriyorsa MCP için `~/.claude.json`, hook’lar için `~/.claude/settings.json` kullanılır. Diğer dizin değerleri, baştaki ve sondaki boşluk karakterleri de dâhil olmak üzere aynen kullanılır. Özel bir dizin kullanmak için `CLAUDE_CONFIG_DIR` değerini hem bu komut hem de Claude Code için aynı, boş olmayan değere ayarlayın; dosyalar sırasıyla `$CLAUDE_CONFIG_DIR/.claude.json` ve `$CLAUDE_CONFIG_DIR/settings.json` olur. Bağlayıcı değeri AgentMemory’nin `.env` dosyasından okusa bile Claude Code bu değeri kendi başlatma ortamında almalıdır. Bu komutu çalıştırmadan önce özel dizini oluşturun; aksi hâlde bağlayıcı Claude Code’u algılanmadığı için atlar. Shell’deki değer yalnızca boşluk karakterleri içeriyorsa Claude Code’u başlatmadan önce `CLAUDE_CONFIG_DIR` değişkenini ortamdan kaldırın; böylece o da varsayılan profili kullanır. Mutlak bir yol kullanın. Göreli yollar çalışma dizinine göre çözümlenir; bu nedenle her iki komut da aynı dizinden çalıştırılmalıdır.
+
+Hook komutları, kurulu paketin içerdiği `plugin/` dizinine giden mutlak yolları kullanır. Bu yolları yenilemek için agentmemory’yi yükselttikten sonra komutu yeniden çalıştırın. Yapılandırma dosyalarındaki kullanıcı girdileri korunur; yalnızca önceki agentmemory girdileri değiştirilir. `/plugin install` kullanımı önerilen yaklaşım olmaya devam eder.
Uzak veya korumalı dağıtımlar için Claude Code'u `AGENTMEMORY_URL` ve `AGENTMEMORY_SECRET` ayarlanmış şekilde başlatın. Eklenti, her iki değeri de paketlenmiş MCP sunucusuna iletir; `AGENTMEMORY_URL` boş olduğunda MCP shim'i `http://localhost:3111`'i kullanır.
### Codex CLI (Codex eklenti platformu)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Tam kılavuz: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory Windows 10/11’de çalışır. WSL2 Linux yolunu izleyerek engine’i otomatik kurabilir. Yerel Windows’ta iii-engine v0.25.0 elle kurulmalıdır: arşivi [iii v0.25.0 sürüm sayfasından](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) indirin, checksum’u doğrulayın ve `iii.exe` dosyasını `PATH` üzerine koyun. CLI Windows ZIP’ini otomatik açmaz
+agentmemory Windows 10/11’de çalışır. WSL2 Linux yolunu izleyerek engine’i otomatik kurabilir. Yerel Windows’ta iii-engine v0.25.1 elle kurulmalıdır: arşivi [iii v0.25.1 sürüm sayfasından](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) indirin, checksum’u doğrulayın ve `iii.exe` dosyasını `PATH` üzerine koyun. CLI Windows ZIP’ini otomatik açmaz
Yerel Windows’ta otomatik MCP yapılandırması yalnızca `agentmemory connect copilot-cli` için vardır; diğerleri için [Other agents](#other-agents) bölümünü kullanın. WSL’de `connect` yalnızca hedef agent aynı WSL ortamındaysa çalıştırılmalıdır
@@ -1159,7 +1161,7 @@ Tam [`.env.example`](../.env.example) sağlayıcıları, kayıt filtrelerini, sa
-`3111` portunda 146 endpoint. REST API, varsayılan olarak `127.0.0.1`'e bağlanır. Korumalı endpoint'ler `Authorization: Bearer ` gerektirir ve mesh sync endpoint'leri her iki peer'da da açıkça ayarlanmış bir `AGENTMEMORY_SECRET` gerektirir.
+`3111` portunda 147 endpoint. REST API, varsayılan olarak `127.0.0.1`'e bağlanır. Korumalı endpoint'ler `Authorization: Bearer ` gerektirir ve mesh sync endpoint'leri her iki peer'da da açıkça ayarlanmış bir `AGENTMEMORY_SECRET` gerektirir.
**Kimlik doğrulama varsayılan olarak açıktır.** `AGENTMEMORY_SECRET` ayarlanmamışsa CLI ilk başlatmada `~/.agentmemory/secret` dosyasında `0600` izinleriyle rastgele bir sır oluşturur ve seçilen veri dizinine de kopyalar. Paketli istemciler yerel sunucuya bağlanırken buradan okur; secret yalnız loopback URL’lerine (`localhost`, `127.0.0.0/8`, `::1`) gönderilir. Uzak istemciler secret’ı kendi ortamında sağlamalıdır. Docker self-host ve `deploy/` kendi secret’larını üretir. API’yi elle çağırmak için:
@@ -1241,7 +1243,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.uk-UA.md b/READMEs/README.uk-UA.md
index 4033a79f17..b26305144d 100644
--- a/READMEs/README.uk-UA.md
+++ b/READMEs/README.uk-UA.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code без встановлення плагіна (автономний шлях MCP)
-Якщо ви підключаєте MCP-сервер agentmemory напряму через `~/.claude.json`, а не через `/plugin install`, Claude Code ніколи не розгортає `${CLAUDE_PLUGIN_ROOT}`, і вам доведеться вказувати абсолютні шляхи до скриптів хуків у `~/.claude/settings.json`. Ці шляхи, як правило, містять версію agentmemory (наприклад, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), тому наступне оновлення непомітно зламає кожен хук.
+Якщо ви підключаєте MCP-сервер agentmemory напряму через `~/.claude.json` (типовий шлях), а не через `/plugin install`, Claude Code ніколи не розгортає `${CLAUDE_PLUGIN_ROOT}`, і вам доведеться вказувати абсолютні шляхи до скриптів хуків у `~/.claude/settings.json` (типовий шлях). Ці шляхи, як правило, містять версію agentmemory (наприклад, `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), тому наступне оновлення непомітно зламає кожен хук.
Обхідне рішення:
@@ -454,7 +454,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-Ця команда об'єднує ті самі команди хуків у `~/.claude/settings.json`, використовуючи абсолютні шляхи, визначені до вбудованого каталогу `plugin/` наразі встановленого пакета `@agentmemory/agentmemory`. Повторно запустіть команду після оновлення agentmemory, щоб оновити шляхи. Записи користувача в тому самому файлі зберігаються; замінюються лише попередні записи agentmemory. Шлях через `/plugin install` залишається рекомендованим підходом.
+Ця команда налаштовує MCP-сервер і додає включені до пакета хуки до конфігурації користувача Claude Code. Якщо `CLAUDE_CONFIG_DIR` не задано, вона порожня або містить лише пробільні символи, для MCP використовується `~/.claude.json`, а для хуків — `~/.claude/settings.json`. Інші значення каталогу використовуються без змін, включно з пробільними символами на початку та в кінці. Щоб використовувати власний каталог, задайте однакове непорожнє значення `CLAUDE_CONFIG_DIR` для цієї команди та Claude Code; тоді файлами будуть відповідно `$CLAUDE_CONFIG_DIR/.claude.json` і `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code має отримати це значення у своєму середовищі запуску, навіть якщо конектор читає його з файлу `.env` AgentMemory. Створіть власний каталог перед виконанням цієї команди; інакше конектор пропустить Claude Code як невиявлений. Якщо значення в оболонці містить лише пробільні символи, вилучіть `CLAUDE_CONFIG_DIR` із середовища перед запуском Claude Code, щоб він також використовував типовий профіль. Використовуйте абсолютний шлях. Відносні шляхи визначаються від робочого каталогу, тому обидві команди потрібно запускати з одного каталогу.
+
+Команди хуків використовують абсолютні шляхи до каталогу `plugin/`, включеного до встановленого пакета. Після оновлення agentmemory запустіть команду ще раз, щоб оновити ці шляхи. Записи користувача у файлах конфігурації зберігаються; замінюються лише попередні записи agentmemory. Використання `/plugin install` залишається рекомендованим підходом.
Для віддалених або захищених розгортань запускайте Claude Code зі встановленими `AGENTMEMORY_URL` та `AGENTMEMORY_SECRET`. Плагін передає обидва значення своєму вбудованому MCP-серверу; якщо `AGENTMEMORY_URL` порожній, MCP-шим використовує `http://localhost:3111`.
### Codex CLI (платформа плагінів Codex)
@@ -565,7 +567,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Повний посібник: [`integrations/hermes/`](../integrations/hermes/)
@@ -663,7 +665,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory працює у Windows 10/11; WSL2 може автоматично встановити engine. Нативна Windows потребує ручного встановлення iii-engine v0.25.0: завантажте архів зі [сторінки iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), перевірте checksum і розмістіть `iii.exe` у `PATH`. CLI не розпаковує ZIP автоматично
+agentmemory працює у Windows 10/11; WSL2 може автоматично встановити engine. Нативна Windows потребує ручного встановлення iii-engine v0.25.1: завантажте архів зі [сторінки iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), перевірте checksum і розмістіть `iii.exe` у `PATH`. CLI не розпаковує ZIP автоматично
Автоматичне налаштування MCP у нативній Windows підтримує лише `agentmemory connect copilot-cli`; для інших скористайтеся [Other agents](#other-agents). У WSL виконуйте `connect`, лише якщо агент встановлений у тому самому середовищі
@@ -1160,7 +1162,7 @@ EMBEDDING_PROVIDER=local
-146 ендпоінтів на порту `3111`. REST API за замовчуванням прив'язується до `127.0.0.1`. Захищені ендпоінти вимагають `Authorization: Bearer `, а ендпоінти синхронізації mesh вимагають явно встановленого `AGENTMEMORY_SECRET` на обох сторонах.
+147 ендпоінтів на порту `3111`. REST API за замовчуванням прив'язується до `127.0.0.1`. Захищені ендпоінти вимагають `Authorization: Bearer `, а ендпоінти синхронізації mesh вимагають явно встановленого `AGENTMEMORY_SECRET` на обох сторонах.
**Автентифікацію ввімкнено типово.** Якщо `AGENTMEMORY_SECRET` не задано, під час першого запуску CLI створює випадковий секрет у `~/.agentmemory/secret` з правами `0600` і копіює його також у вибраний каталог даних. Вбудовані клієнти читають його звідти для локального сервера; secret надсилається лише на loopback URL (`localhost`, `127.0.0.0/8`, `::1`). Віддалені клієнти мають отримати secret через власне середовище. Docker self-host і `deploy/` створюють власні секрети. Щоб викликати API вручну:
@@ -1242,7 +1244,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.ur-PK.md b/READMEs/README.ur-PK.md
index 53f941522e..31250f113a 100644
--- a/READMEs/README.ur-PK.md
+++ b/READMEs/README.ur-PK.md
@@ -52,7 +52,7 @@
-
+
@@ -71,7 +71,7 @@
-
+
@@ -446,7 +446,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code بغیر plugin انسٹال کے (MCP-standalone راستہ)
-اگر آپ `/plugin install` استعمال کرنے کے بجائے agentmemory کے MCP سرور کو براہِ راست `~/.claude.json` کے ذریعے جوڑتے ہیں، تو Claude Code کبھی `${CLAUDE_PLUGIN_ROOT}` کو resolve نہیں کرتا اور آپ کو hook اسکرپٹس کو `~/.claude/settings.json` میں absolute paths کی طرف پوائنٹ کرنا پڑتا ہے۔ یہ paths عام طور پر agentmemory کا ورژن شامل رکھتے ہیں (مثلاً `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)، لہٰذا اگلا اپ گریڈ خاموشی سے ہر ہک کو توڑ دیتا ہے۔
+اگر آپ `/plugin install` استعمال کرنے کے بجائے agentmemory کے MCP سرور کو براہِ راست `~/.claude.json` (پہلے سے طے شدہ راستہ) کے ذریعے جوڑتے ہیں، تو Claude Code کبھی `${CLAUDE_PLUGIN_ROOT}` کو resolve نہیں کرتا اور آپ کو hook اسکرپٹس کو `~/.claude/settings.json` (پہلے سے طے شدہ راستہ) میں absolute paths کی طرف پوائنٹ کرنا پڑتا ہے۔ یہ paths عام طور پر agentmemory کا ورژن شامل رکھتے ہیں (مثلاً `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`)، لہٰذا اگلا اپ گریڈ خاموشی سے ہر ہک کو توڑ دیتا ہے۔
متبادل حل:
@@ -454,7 +454,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-یہ انہی hook کمانڈز کو `~/.claude/settings.json` میں ضم کرتا ہے، ان absolute paths کے ساتھ جو currently installed `@agentmemory/agentmemory` پیکیج کی bundled `plugin/` ڈائرکٹری سے resolve ہوتے ہیں۔ paths کو تازہ کرنے کے لیے agentmemory اپ گریڈ کرنے کے بعد یہ کمانڈ دوبارہ چلائیں۔ اسی فائل میں موجود صارف کے entries محفوظ رہتے ہیں؛ صرف پہلے والے agentmemory entries تبدیل ہوتے ہیں۔ `/plugin install` راستہ استعمال کرنا ہی تجویز کردہ طریقہ رہتا ہے۔
+یہ کمانڈ MCP سرور کو کنفیگر کرتی ہے اور ساتھ آنے والے hooks کو Claude Code کی صارف کنفیگریشن میں ضم کرتی ہے۔ اگر `CLAUDE_CONFIG_DIR` سیٹ نہیں ہے، خالی ہے یا اس میں صرف وائٹ اسپیس ہے تو یہ MCP کے لیے `~/.claude.json` اور hooks کے لیے `~/.claude/settings.json` استعمال کرتی ہے۔ ڈائرکٹری کی دیگر قدریں بالکل اسی طرح استعمال ہوتی ہیں جیسے دی گئی ہوں، بشمول شروع اور آخر کی وائٹ اسپیس۔ اپنی مرضی کی ڈائرکٹری کے لیے اس کمانڈ اور Claude Code دونوں کے لیے `CLAUDE_CONFIG_DIR` کی ایک ہی غیر خالی قدر سیٹ کریں؛ تب فائلیں بالترتیب `$CLAUDE_CONFIG_DIR/.claude.json` اور `$CLAUDE_CONFIG_DIR/settings.json` ہوں گی۔ Claude Code کو یہ قدر اپنے لانچ ماحول میں ملنی چاہیے، چاہے کنیکٹر اسے AgentMemory کی `.env` سے پڑھتا ہو۔ اس کمانڈ کو چلانے سے پہلے اپنی مرضی کی ڈائرکٹری بنائیں؛ ورنہ کنیکٹر Claude Code کو شناخت نہ ہونے کی وجہ سے چھوڑ دے گا۔ اگر shell کی قدر میں صرف وائٹ اسپیس ہو تو Claude Code شروع کرنے سے پہلے ماحول سے `CLAUDE_CONFIG_DIR` ہٹا دیں تاکہ وہ بھی پہلے سے طے شدہ پروفائل استعمال کرے۔ مطلق راستہ استعمال کریں۔ نسبتی راستے کام کی ڈائریکٹری کے لحاظ سے متعین ہوتے ہیں، اس لیے دونوں کمانڈز ایک ہی ڈائریکٹری سے چلائیں۔
+
+Hook کمانڈز انسٹال شدہ پیکیج کے ساتھ آنے والی `plugin/` ڈائرکٹری کے مطلق راستے استعمال کرتی ہیں۔ agentmemory اپ گریڈ کرنے کے بعد ان راستوں کو تازہ کرنے کے لیے کمانڈ دوبارہ چلائیں۔ کنفیگریشن فائلوں میں صارف کی entries محفوظ رہتی ہیں؛ صرف agentmemory کی پچھلی entries تبدیل ہوتی ہیں۔ `/plugin install` کا استعمال ہی تجویز کردہ طریقہ رہتا ہے۔
ریموٹ یا محفوظ deployments کے لیے، Claude Code کو `AGENTMEMORY_URL` اور `AGENTMEMORY_SECRET` سیٹ کر کے لانچ کریں۔ plugin دونوں قدریں اپنے bundled MCP سرور تک پہنچاتا ہے؛ جب `AGENTMEMORY_URL` خالی ہو، تو MCP shim `http://localhost:3111` استعمال کرتا ہے۔
### Codex CLI (Codex plugin پلیٹ فارم)
@@ -561,7 +563,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
مکمل گائیڈ: [`integrations/hermes/`](../integrations/hermes/)
@@ -658,7 +660,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory Windows 10/11 پر چلتا ہے؛ WSL2 Linux طریقے سے engine خود انسٹال کر سکتا ہے۔ Native Windows پر iii-engine v0.25.0 binary دستی طور پر انسٹال کریں: [iii v0.25.0 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) سے archive ڈاؤن لوڈ، checksum کی تصدیق، اور `iii.exe` کو `PATH` پر رکھیں۔ CLI ZIP خود نہیں کھولتا
+agentmemory Windows 10/11 پر چلتا ہے؛ WSL2 Linux طریقے سے engine خود انسٹال کر سکتا ہے۔ Native Windows پر iii-engine v0.25.1 binary دستی طور پر انسٹال کریں: [iii v0.25.1 release page](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) سے archive ڈاؤن لوڈ، checksum کی تصدیق، اور `iii.exe` کو `PATH` پر رکھیں۔ CLI ZIP خود نہیں کھولتا
Native Windows پر MCP خودکار wiring صرف `agentmemory connect copilot-cli` کے لیے ہے؛ دوسرے agents کے لیے [Other agents](#other-agents) کا دستی MCP block استعمال کریں۔ WSL میں `connect` تب چلائیں جب target agent وہیں نصب ہو
@@ -1165,7 +1167,7 @@ EMBEDDING_PROVIDER=local
-پورٹ `3111` پر 146 اینڈ پوائنٹس۔ REST API ڈیفالٹ کے طور پر `127.0.0.1` سے bind ہوتا ہے۔ محفوظ اینڈ پوائنٹس کو `Authorization: Bearer ` درکار ہے، اور mesh sync اینڈ پوائنٹس کو دونوں peers پر واضح طور پر سیٹ کیا گیا `AGENTMEMORY_SECRET` درکار ہے۔
+پورٹ `3111` پر 147 اینڈ پوائنٹس۔ REST API ڈیفالٹ کے طور پر `127.0.0.1` سے bind ہوتا ہے۔ محفوظ اینڈ پوائنٹس کو `Authorization: Bearer ` درکار ہے، اور mesh sync اینڈ پوائنٹس کو دونوں peers پر واضح طور پر سیٹ کیا گیا `AGENTMEMORY_SECRET` درکار ہے۔
توثیق بطور طے شدہ فعال ہے۔ `AGENTMEMORY_SECRET` مقرر نہ ہو تو CLI پہلی بار بے ترتیب راز `~/.agentmemory/secret` میں محفوظ کرتا ہے اور منتخب ڈیٹا ڈائریکٹری کے `secret` میں اس کی نقل رکھتا ہے؛ اجازت `0600` ہوتی ہے۔ ساتھ آنے والے کلائنٹس مقامی رابطے میں اس اصل فائل کو ترجیح دیتے ہیں اور محفوظ راز صرف loopback URL کو بھیجتے ہیں۔ واضح `AGENTMEMORY_SECRET` مقدم ہے؛ دور کے کلائنٹس اسے environment میں مقرر کریں۔ Docker اپنا راز بناتا ہے۔
@@ -1246,7 +1248,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.vi-VN.md b/READMEs/README.vi-VN.md
index 2be083144f..fd842721a3 100644
--- a/READMEs/README.vi-VN.md
+++ b/READMEs/README.vi-VN.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -101,7 +101,7 @@ Yêu cầu:
- Node.js 20 hoặc mới hơn kèm npm và npx (`node -v`, `npm -v`, và `npx -v`).
- Thiết lập tự động trên macOS/Linux cần `curl`, POSIX `sh` và `tar`.
-Windows native cần cài thủ công `iii.exe` của iii v0.25.0 đã pin; WSL2 dùng trình cài tự động cho macOS/Linux
+Windows native cần cài thủ công `iii.exe` của iii v0.25.1 đã pin; WSL2 dùng trình cài tự động cho macOS/Linux
Lệnh cài mới chuẩn (canonical):
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code không cài plugin (đường MCP độc lập)
-Nếu bạn kết nối MCP server của agentmemory qua `~/.claude.json` trực tiếp thay vì dùng `/plugin install`, Claude Code sẽ không bao giờ resolve `${CLAUDE_PLUGIN_ROOT}` và bạn phải chỉ các hook script tới đường dẫn tuyệt đối trong `~/.claude/settings.json`. Các đường dẫn đó thường nhúng cả phiên bản agentmemory (ví dụ `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), nên lần nâng cấp kế tiếp sẽ lặng lẽ làm hỏng mọi hook.
+Nếu bạn kết nối MCP server của agentmemory qua `~/.claude.json` (đường dẫn mặc định) trực tiếp thay vì dùng `/plugin install`, Claude Code sẽ không bao giờ resolve `${CLAUDE_PLUGIN_ROOT}` và bạn phải chỉ các hook script tới đường dẫn tuyệt đối trong `~/.claude/settings.json` (đường dẫn mặc định). Các đường dẫn đó thường nhúng cả phiên bản agentmemory (ví dụ `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`), nên lần nâng cấp kế tiếp sẽ lặng lẽ làm hỏng mọi hook.
Cách khắc phục tạm:
@@ -452,7 +452,9 @@ Cách khắc phục tạm:
agentmemory connect claude-code --with-hooks
```
-Lệnh này gộp cùng các hook command đó vào `~/.claude/settings.json` với đường dẫn tuyệt đối được resolve tới thư mục `plugin/` đi kèm của package `@agentmemory/agentmemory` đang được cài. Chạy lại lệnh này sau khi nâng cấp agentmemory để làm mới các đường dẫn. Các entry của người dùng trong cùng file được giữ lại; chỉ các entry agentmemory trước đó bị thay thế. Dùng đường `/plugin install` vẫn là cách được khuyến nghị.
+Lệnh này cấu hình máy chủ MCP và gộp các hook đi kèm vào cấu hình người dùng của Claude Code. Nếu `CLAUDE_CONFIG_DIR` chưa được đặt, rỗng hoặc chỉ chứa khoảng trắng, lệnh dùng `~/.claude.json` cho MCP và `~/.claude/settings.json` cho các hook. Các giá trị thư mục khác được dùng đúng như đã cung cấp, kể cả khoảng trắng ở đầu và cuối. Để dùng thư mục tùy chỉnh, hãy đặt `CLAUDE_CONFIG_DIR` thành cùng một giá trị không rỗng cho cả lệnh này và Claude Code; khi đó, các tệp lần lượt là `$CLAUDE_CONFIG_DIR/.claude.json` và `$CLAUDE_CONFIG_DIR/settings.json`. Claude Code phải nhận giá trị này trong môi trường khởi chạy của chính nó, ngay cả khi trình kết nối đọc giá trị từ tệp `.env` của AgentMemory. Tạo thư mục tùy chỉnh trước khi chạy lệnh này; nếu thư mục chưa tồn tại, trình kết nối sẽ bỏ qua Claude Code vì không phát hiện được. Nếu giá trị trong shell chỉ chứa khoảng trắng, hãy xóa `CLAUDE_CONFIG_DIR` khỏi môi trường trước khi khởi chạy Claude Code để nó cũng dùng cấu hình mặc định. Hãy dùng đường dẫn tuyệt đối. Đường dẫn tương đối được xác định theo thư mục làm việc, nên cả hai lệnh phải được chạy từ cùng một thư mục.
+
+Các lệnh hook dùng đường dẫn tuyệt đối đến thư mục `plugin/` đi kèm trong gói đã cài đặt. Chạy lại lệnh sau khi nâng cấp agentmemory để cập nhật các đường dẫn này. Các mục của người dùng trong tệp cấu hình được giữ nguyên; chỉ các mục agentmemory trước đó bị thay thế. Dùng `/plugin install` vẫn là cách được khuyến nghị.
Với các deployment từ xa hoặc được bảo vệ, hãy khởi chạy Claude Code với `AGENTMEMORY_URL` và `AGENTMEMORY_SECRET` đã được đặt. Plugin sẽ truyền cả hai giá trị này xuống MCP server đi kèm của nó; khi `AGENTMEMORY_URL` để trống, MCP shim dùng `http://localhost:3111`.
### Codex CLI (nền tảng plugin của Codex)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
Hướng dẫn đầy đủ: [`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory chạy trên Windows 10/11; WSL2 có thể tự cài engine theo quy trình Linux. Windows native cần cài thủ công iii-engine v0.25.0: tải archive từ [trang phát hành iii v0.25.0](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0), xác minh checksum và đặt `iii.exe` trong `PATH`. CLI không tự giải nén ZIP Windows
+agentmemory chạy trên Windows 10/11; WSL2 có thể tự cài engine theo quy trình Linux. Windows native cần cài thủ công iii-engine v0.25.1: tải archive từ [trang phát hành iii v0.25.1](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1), xác minh checksum và đặt `iii.exe` trong `PATH`. CLI không tự giải nén ZIP Windows
Cấu hình MCP tự động trên Windows native chỉ hỗ trợ `agentmemory connect copilot-cli`; agent khác dùng khối MCP thủ công trong [Other agents](#other-agents). Chỉ chạy `connect` trong WSL nếu agent đích cũng cài trong cùng môi trường WSL
@@ -1170,7 +1172,7 @@ Tham chiếu đầy đủ ở [`.env.example`](../.env.example), gồm nhà cung
-146 endpoint trên port `3111`. REST API bind vào `127.0.0.1` theo mặc định. Các endpoint được bảo vệ cần `Authorization: Bearer `, và các endpoint mesh sync cần `AGENTMEMORY_SECRET` được đặt rõ ràng trên cả hai phía.
+147 endpoint trên port `3111`. REST API bind vào `127.0.0.1` theo mặc định. Các endpoint được bảo vệ cần `Authorization: Bearer `, và các endpoint mesh sync cần `AGENTMEMORY_SECRET` được đặt rõ ràng trên cả hai phía.
Xác thực bật mặc định. Nếu chưa đặt `AGENTMEMORY_SECRET`, CLI tạo bí mật ngẫu nhiên lần đầu tại `~/.agentmemory/secret` và sao chép vào `secret` trong thư mục dữ liệu đã chọn, với quyền `0600`. Client đi kèm ưu tiên tệp chính này khi kết nối cục bộ và chỉ gửi bí mật đã lưu đến URL loopback. `AGENTMEMORY_SECRET` đặt tường minh luôn được ưu tiên; client từ xa phải đặt qua biến môi trường. Triển khai Docker tạo bí mật riêng.
@@ -1251,7 +1253,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.zh-CN.md b/READMEs/README.zh-CN.md
index a96226f914..4c56b9e1e0 100644
--- a/READMEs/README.zh-CN.md
+++ b/READMEs/README.zh-CN.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -444,7 +444,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code 不使用插件安装(MCP 独立路径)
-如果你直接通过 `~/.claude.json` 接入 agentmemory 的 MCP 服务器,而不是使用 `/plugin install`,Claude Code 永远不会解析 `${CLAUDE_PLUGIN_ROOT}`,你必须把 hook 脚本指向 `~/.claude/settings.json` 中的绝对路径。这些路径通常会嵌入 agentmemory 的版本号(例如 `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`),因此下一次升级会悄悄破坏所有 hooks。
+如果你直接通过 `~/.claude.json`(默认路径)接入 agentmemory 的 MCP 服务器,而不是使用 `/plugin install`,Claude Code 永远不会解析 `${CLAUDE_PLUGIN_ROOT}`,你必须把 hook 脚本指向 `~/.claude/settings.json`(默认路径)中的绝对路径。这些路径通常会嵌入 agentmemory 的版本号(例如 `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`),因此下一次升级会悄悄破坏所有 hooks。
变通方法:
@@ -452,7 +452,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-这会把同样的 hook 命令合并进 `~/.claude/settings.json`,绝对路径会解析到当前安装的 `@agentmemory/agentmemory` 包自带的 `plugin/` 目录。升级 agentmemory 之后重新运行该命令以刷新路径。同一文件中的用户条目会被保留;只会替换之前的 agentmemory 条目。仍然推荐使用 `/plugin install` 路径。
+此命令会配置 MCP 服务器,并将包内的 hook 合并到 Claude Code 的用户配置中。`CLAUDE_CONFIG_DIR` 未设置、为空或仅含空白时,MCP 使用 `~/.claude.json`,hook 使用 `~/.claude/settings.json`。其他目录值按原样使用,包括首尾空白。若使用自定义目录,请为此命令和 Claude Code 设置相同且非空的 `CLAUDE_CONFIG_DIR`,此时两份配置文件分别为 `$CLAUDE_CONFIG_DIR/.claude.json` 和 `$CLAUDE_CONFIG_DIR/settings.json`。即使连接器从 AgentMemory 的 `.env` 读取该值,Claude Code 自身的启动环境中也必须设置该值。运行此命令前请先创建自定义目录;目录不存在时,连接器会以未检测到 Claude Code 为由跳过。若 shell 中的值仅含空白,请在启动 Claude Code 前取消 `CLAUDE_CONFIG_DIR`,使其也使用默认配置。建议使用绝对路径。相对路径以工作目录为基准,因此两个命令必须从同一目录启动。
+
+Hook 命令使用绝对路径,指向已安装包内的 `plugin/` 目录。升级 agentmemory 后,请重新运行此命令以刷新这些路径。配置文件中的用户条目会保留,仅替换之前的 agentmemory 条目。仍推荐使用 `/plugin install`。
对于远程或受保护的部署,启动 Claude Code 时设置好 `AGENTMEMORY_URL` 和 `AGENTMEMORY_SECRET`。插件会把这两个值传递给它捆绑的 MCP 服务器;当 `AGENTMEMORY_URL` 为空时,MCP shim 会使用 `http://localhost:3111`。
### Codex CLI(Codex 插件平台)
@@ -559,7 +561,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
完整指南:[`integrations/hermes/`](../integrations/hermes/)
@@ -656,7 +658,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory 支持 Windows 10/11;WSL2 可按 Linux 流程自动安装 engine。原生 Windows 需手动安装 iii-engine v0.25.0:从 [iii v0.25.0 发布页](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) 下载对应归档、验证校验和,并将 `iii.exe` 放到 `PATH`。CLI 不会自动解压 ZIP
+agentmemory 支持 Windows 10/11;WSL2 可按 Linux 流程自动安装 engine。原生 Windows 需手动安装 iii-engine v0.25.1:从 [iii v0.25.1 发布页](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) 下载对应归档、验证校验和,并将 `iii.exe` 放到 `PATH`。CLI 不会自动解压 ZIP
原生 Windows 仅为 `agentmemory connect copilot-cli` 提供自动 MCP 配置;其他 agent 请使用 [Other agents](#other-agents) 中的手动配置。仅当目标 agent 也安装在同一 WSL 环境时,才在 WSL 中运行 `connect`
@@ -1171,7 +1173,7 @@ EMBEDDING_PROVIDER=local
-端口 `3111` 上有 146 个端点。REST API 默认绑定到 `127.0.0.1`。受保护的端点需要 `Authorization: Bearer `,mesh 同步端点则需要双方都显式设置 `AGENTMEMORY_SECRET`。
+端口 `3111` 上有 147 个端点。REST API 默认绑定到 `127.0.0.1`。受保护的端点需要 `Authorization: Bearer `,mesh 同步端点则需要双方都显式设置 `AGENTMEMORY_SECRET`。
认证默认开启。未设置 `AGENTMEMORY_SECRET` 时,CLI 首次启动会将随机密钥保存到 `~/.agentmemory/secret`,并镜像到所选数据目录的 `secret`,权限为 `0600`。内置客户端连接本地服务器时优先读取该公共文件,只向回环 URL 发送保存的密钥。显式设置的 `AGENTMEMORY_SECRET` 优先;远程客户端需通过环境变量设置密钥。Docker 部署生成自己的密钥。
@@ -1252,7 +1254,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/READMEs/README.zh-TW.md b/READMEs/README.zh-TW.md
index 5ed8dc3dce..16d550226f 100644
--- a/READMEs/README.zh-TW.md
+++ b/READMEs/README.zh-TW.md
@@ -50,7 +50,7 @@
-
+
@@ -69,7 +69,7 @@
-
+
@@ -442,7 +442,7 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
#### Claude Code 若未安裝外掛(MCP 獨立路徑)
-若你直接透過 `~/.claude.json` 連接 agentmemory 的 MCP 伺服器,而不是使用 `/plugin install`,Claude Code 永遠不會解析 `${CLAUDE_PLUGIN_ROOT}`,你必須把 hook 腳本指向 `~/.claude/settings.json` 中的絕對路徑。這些路徑通常會嵌入 agentmemory 的版本號(例如 `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`),因此下次升級會靜默破壞每一個 hook。
+若你直接透過 `~/.claude.json`(預設路徑)連接 agentmemory 的 MCP 伺服器,而不是使用 `/plugin install`,Claude Code 永遠不會解析 `${CLAUDE_PLUGIN_ROOT}`,你必須把 hook 腳本指向 `~/.claude/settings.json`(預設路徑)中的絕對路徑。這些路徑通常會嵌入 agentmemory 的版本號(例如 `~/.codex/plugins/cache/agentmemory/agentmemory/0.9.22/scripts/…`),因此下次升級會靜默破壞每一個 hook。
變通方法:
@@ -450,7 +450,9 @@ Install agentmemory: run `npx -y @agentmemory/agentmemory@latest` in a separate
agentmemory connect claude-code --with-hooks
```
-這會把同樣的 hook 指令合併到 `~/.claude/settings.json` 中,絕對路徑會解析到目前安裝的 `@agentmemory/agentmemory` 套件所捆綁的 `plugin/` 目錄。升級 agentmemory 後重新執行此指令以刷新路徑。同一檔案中既有的使用者條目會被保留;只有先前的 agentmemory 條目會被取代。仍然建議使用 `/plugin install` 路徑。
+此指令會設定 MCP 伺服器,並將套件內的 hook 合併到 Claude Code 的使用者設定中。`CLAUDE_CONFIG_DIR` 未設定、為空或僅含空白時,MCP 使用 `~/.claude.json`,hook 使用 `~/.claude/settings.json`。其他目錄值按原樣使用,包括首尾空白。若使用自訂目錄,請為此指令和 Claude Code 設定相同且非空的 `CLAUDE_CONFIG_DIR`,此時兩份設定檔分別為 `$CLAUDE_CONFIG_DIR/.claude.json` 和 `$CLAUDE_CONFIG_DIR/settings.json`。即使連接器從 AgentMemory 的 `.env` 讀取該值,Claude Code 本身的啟動環境中也必須設定該值。執行此指令前請先建立自訂目錄;目錄不存在時,連接器會以未偵測到 Claude Code 為由略過。若 shell 中的值僅含空白,請在啟動 Claude Code 前取消 `CLAUDE_CONFIG_DIR`,使其也使用預設設定。建議使用絕對路徑。相對路徑以工作目錄為基準,因此兩個命令必須從同一目錄啟動。
+
+Hook 指令使用絕對路徑,指向已安裝套件內的 `plugin/` 目錄。升級 agentmemory 後,請重新執行此指令以更新這些路徑。設定檔中的使用者條目會保留,僅取代先前的 agentmemory 條目。仍建議使用 `/plugin install`。
若用於遠端或受保護的部署,啟動 Claude Code 時請設定 `AGENTMEMORY_URL` 和 `AGENTMEMORY_SECRET`。外掛會把這兩個值都傳給它捆綁的 MCP 伺服器;當 `AGENTMEMORY_URL` 為空時,MCP shim 會使用 `http://localhost:3111`。
### Codex CLI(Codex 外掛平台)
@@ -557,7 +559,7 @@ mcp_servers:
memory:
provider: agentmemory
-Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from the agentmemory repo to ~/.hermes/plugins/agentmemory.
+Verify with `curl http://localhost:3111/agentmemory/health`. Open http://localhost:3113 for the real-time viewer. For deeper 6-hook memory provider integration (pre-LLM context injection, turn capture, MEMORY.md mirroring, system prompt block), copy integrations/hermes from https://github.com/rohitg00/agentmemory to ~/.hermes/plugins/agentmemory.
```
完整指南:[`integrations/hermes/`](../integrations/hermes/)
@@ -654,7 +656,7 @@ npm install && npm run build && npm start
### Windows
-agentmemory 可在 Windows 10/11 執行;WSL2 可依 Linux 流程自動安裝 engine。原生 Windows 需手動安裝 iii-engine v0.25.0:從 [iii v0.25.0 發行頁面](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.0) 下載相符封存檔、驗證 checksum,並將 `iii.exe` 放入 `PATH`。CLI 不會自動解壓 ZIP
+agentmemory 可在 Windows 10/11 執行;WSL2 可依 Linux 流程自動安裝 engine。原生 Windows 需手動安裝 iii-engine v0.25.1:從 [iii v0.25.1 發行頁面](https://github.com/iii-hq/iii/releases/tag/iii%2Fv0.25.1) 下載相符封存檔、驗證 checksum,並將 `iii.exe` 放入 `PATH`。CLI 不會自動解壓 ZIP
原生 Windows 僅支援 `agentmemory connect copilot-cli` 自動設定 MCP;其他 agent 請使用 [Other agents](#other-agents) 的手動設定。只有目標 agent 也安裝在相同 WSL 環境時,才在 WSL 執行 `connect`
@@ -1163,7 +1165,7 @@ EMBEDDING_PROVIDER=local
-連接埠 `3111` 上有 146 個端點。REST API 預設綁定 `127.0.0.1`。受保護的端點需要 `Authorization: Bearer `,而網狀同步端點要求兩端都明確設定 `AGENTMEMORY_SECRET`。
+連接埠 `3111` 上有 147 個端點。REST API 預設綁定 `127.0.0.1`。受保護的端點需要 `Authorization: Bearer `,而網狀同步端點要求兩端都明確設定 `AGENTMEMORY_SECRET`。
驗證預設開啟。未設定 `AGENTMEMORY_SECRET` 時,CLI 首次啟動會將隨機密鑰儲存到 `~/.agentmemory/secret`,並鏡像到所選資料目錄的 `secret`,權限為 `0600`。內建客戶端連接本機伺服器時優先讀取此共用檔案,只向回環 URL 傳送儲存的密鑰。明確設定的 `AGENTMEMORY_SECRET` 優先;遠端客戶端需透過環境變數設定密鑰。Docker 部署會產生自己的密鑰。
@@ -1244,7 +1246,7 @@ curl -X POST http://localhost:3111/agentmemory/graph/compact -H "Authorization:
```bash
npm run dev # Hot reload
npm run build # Production build
-npm test # 4,100+ tests
+npm test # 4,900+ tests
npm run test:integration # API tests (requires running services)
```
diff --git a/assets/tags/light/stat-tests.svg b/assets/tags/light/stat-tests.svg
index 7248bfad00..e6fccac91e 100644
--- a/assets/tags/light/stat-tests.svg
+++ b/assets/tags/light/stat-tests.svg
@@ -1,5 +1,5 @@
-