Multi-Agent Collaboration for Team and Friends
TypeScript agent-automationagent-orchestrationagent-workflowai-agentsai-collaborationai-memoryai-workforceautonomous-agentsclaude-codeclaude-code-skillscodexcoding-agentmulti-agentmultiple-agentone-person-businessone-person-companyone-person-teamopencodesolopreneur
docs(web): add Claude Code memory verification guide (#1041)
Gener6e7497f02fe3
diff --git a/src/web/blog/public/blog/claude-code-memory/cli-evidence.webp b/src/web/blog/public/blog/claude-code-memory/cli-evidence.webpnew file mode 100644index 000000000..0b498667cBinary files /dev/null and b/src/web/blog/public/blog/claude-code-memory/cli-evidence.webp differdiff --git a/src/web/blog/public/blog/claude-code-memory/hero.webp b/src/web/blog/public/blog/claude-code-memory/hero.webpnew file mode 100644index 000000000..9216bf505Binary files /dev/null and b/src/web/blog/public/blog/claude-code-memory/hero.webp differdiff --git a/src/web/blog/public/blog/claude-code-memory/memory-files.webp b/src/web/blog/public/blog/claude-code-memory/memory-files.webpnew file mode 100644index 000000000..1f125e4f9Binary files /dev/null and b/src/web/blog/public/blog/claude-code-memory/memory-files.webp differdiff --git a/src/web/blog/public/blog/claude-code-memory/test-record.md b/src/web/blog/public/blog/claude-code-memory/test-record.mdnew file mode 100644index 000000000..e425fa8ea--- /dev/null+++ b/src/web/blog/public/blog/claude-code-memory/test-record.md@@ -0,0 +1,618 @@+# Claude memory test record — v3 companion++Date: 2026-10-21. Stable 2.1.304, macOS arm64. Official artifact checksum: b9ac5374839f14abf3f1f45610637c332b5daee5ce0d1634726cef87aab78e6a.++Publication status: review attachment only. No public URL has been created. Publish this sanitized record beside the article and link it before claiming that readers can download the evidence.++## Scope and starting state++Separate binary and CLAUDE_CONFIG_DIR; empty test Git repo and configuration folder; default memory placement; no autoMemoryDirectory or autoMemoryEnabled override. Tools Read/Write/Edit only, project/local settings sources, strict empty MCP. Machine instruction ancestry was not fully isolated. No daily installation upgrade.++The article’s three-step interactive check is a reader procedure based on current documentation, not a transcript of our experiment. Below is the exact CLI harness used for the recorded test, with paths normalized. All tested prompts are here; the article no longer presents abbreviated prompts as the ones we ran.++```python++from pathlib import Path+import subprocess,os,json,sys+p=Path(__file__).parent.resolve(); env=os.environ.copy();env['CLAUDE_CONFIG_DIR']=str(p/'config')+name=sys.argv[1]+prompts={+ 'save':f'This is a disposable memory experiment. Save this non-sensitive persistent project preference using auto memory: the demo review label is OPAL-742. You may write only under {p/"config"}. Do not modify any repository file or instruction file. Then report what file was saved. Do not claim a save unless the write succeeded.',+ 'recall':'This is a fresh-session memory experiment. What review label should this demo project use? If it is unknown say UNKNOWN. Do not guess and do not search repository files. You may read your memory files if needed. Report the answer and distinguish any file you actually read from what was already available.',+ 'correct':f'In this disposable memory experiment the previous OPAL-742 review label is retired. Update the saved project preference so the current review label is CEDAR-915. Write only under {p/"config"}. Do not modify repository or instruction files. Report actual changed files only.'}+args=[str(p/'bin/claude'),'-p',prompts[name],'--output-format','stream-json','--verbose','--tools','Read,Write,Edit','--allowedTools','Read,Write,Edit','--permission-mode','acceptEdits','--setting-sources','project,local','--strict-mcp-config','--mcp-config',str(p/'empty-mcp.json')]+with (p/(sys.argv[2]+'.jsonl')).open('w') as out,(p/(sys.argv[2]+'.stderr')).open('w') as err:+ try:r=subprocess.run(args,cwd=p/'repo',env=env,stdout=out,stderr=err,timeout=55);print('exit',r.returncode)+ except subprocess.TimeoutExpired:print('timeout after 55s')+++```++## Evidence handling++Tool-call inputs, tool-result blocks and file snapshots are extracted from retained logs. Unrelated response greetings, machine instructions, credentials and environment variables are omitted. Paths are normalized; this is an evidence extract, not a complete transcript. originSessionId and timestamps are test-generated metadata.++## Current stable++### save-default++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_015a9nesQNmAhgKS2BLLqVHV",+ "name": "Read",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/MEMORY.md"+ }+ },+ {+ "type": "tool_result",+ "content": "File does not exist. Note: your current working directory is <test-root>/repo.",+ "is_error": true,+ "tool_use_id": "toolu_bdrk_015a9nesQNmAhgKS2BLLqVHV"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01GduyQ9di51CY24jc779rRy",+ "name": "Write",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/demo-review-label.md",+ "content": "---\nname: demo-review-label\ndescription: The demo review label for this project is OPAL-742\nmetadata:\n type: project\n---\n\nThe demo review label is OPAL-742.\n\n**Why:** The user set this as a persistent project preference (stated 2026-10-21, in a disposable memory experiment).\n\n**How to apply:** Use OPAL-742 whenever a demo review label is needed.\n"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01GduyQ9di51CY24jc779rRy",+ "type": "tool_result",+ "content": "File created successfully at: <test-root>/config/projects/<encoded-project>/memory/demo-review-label.md"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_011PZ6MGagaEKRQWGqhYvgGY",+ "name": "Write",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/MEMORY.md",+ "content": "- [Demo review label](demo-review-label.md) — demo review label is OPAL-742\n"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_011PZ6MGagaEKRQWGqhYvgGY",+ "type": "tool_result",+ "content": "File created successfully at: <test-root>/config/projects/<encoded-project>/memory/MEMORY.md (file state is current in your context — no need to Read it back)"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "756434b4-dae6-4e48-b1b8-ab11b3148007",+ "answer_extract": "OPAL-742"+ }+]++```++### recall-default++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01ML3qJn9enVQ5GB6GTWsRVh",+ "name": "Read",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/demo-review-label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01ML3qJn9enVQ5GB6GTWsRVh",+ "type": "tool_result",+ "content": "1\t---\n2\tname: demo-review-label\n3\tdescription: The demo review label for this project is OPAL-742\n4\tmetadata:\n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007\n8\t modified: 2026-10-21T03:38:09.753Z\n9\t---\n10\t\n11\tThe demo review label is OPAL-742.\n12\t\n13\t**Why:** The user set this as a persistent project preference (stated 2026-10-21, in a disposable memory experiment).\n14\t\n15\t**How to apply:** Use OPAL-742 whenever a demo review label is needed.\n16\t"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "4870485f-166b-4512-92ab-1fe773cad6e8",+ "answer_extract": "OPAL-742"+ }+]++```++### correct-default++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01A3ojtAptBSAVuir3KbTE4V",+ "name": "Read",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/demo-review-label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01A3ojtAptBSAVuir3KbTE4V",+ "type": "tool_result",+ "content": "1\t---\n2\tname: demo-review-label\n3\tdescription: The demo review label for this project is OPAL-742\n4\tmetadata:\n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007\n8\t modified: 2026-10-21T03:38:09.753Z\n9\t---\n10\t\n11\tThe demo review label is OPAL-742.\n12\t\n13\t**Why:** The user set this as a persistent project preference (stated 2026-10-21, in a disposable memory experiment).\n14\t\n15\t**How to apply:** Use OPAL-742 whenever a demo review label is needed.\n16\t"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01Vaerh4NiKkcr5piBviMwgS",+ "name": "Write",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/demo-review-label.md",+ "content": "---\nname: demo-review-label\ndescription: The current demo review label for this project is CEDAR-915 (OPAL-742 is retired)\nmetadata:\n node_type: memory\n type: project\n originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007\n modified: 2026-10-21T00:00:00.000Z\n---\n\nThe current demo review label is CEDAR-915. The previous label, OPAL-742, is retired. Do not use it.\n\n**Why:** The user replaced OPAL-742 with CEDAR-915 on 2026-10-21, in a disposable memory experiment.\n\n**How to apply:** Use CEDAR-915 whenever a demo review label is needed.\n"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01Vaerh4NiKkcr5piBviMwgS",+ "type": "tool_result",+ "content": "The file <test-root>/config/projects/<encoded-project>/memory/demo-review-label.md has been updated successfully."+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01LS1uHMaKEUT3bVoja9ZJeS",+ "name": "Write",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/MEMORY.md",+ "content": "- [Demo review label](demo-review-label.md) — current demo review label is CEDAR-915 (OPAL-742 retired)\n"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01LS1uHMaKEUT3bVoja9ZJeS",+ "type": "tool_result",+ "content": "The file <test-root>/config/projects/<encoded-project>/memory/MEMORY.md has been updated successfully. (file state is current in your context — no need to Read it back)"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "5784872f-329a-4188-9da7-7e6188ea2553",+ "answer_extract": "CEDAR-915"+ }+]++```++### recall-corrected++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01E1FtoABR9bucmf8oWuxKUW",+ "name": "Read",+ "input": {+ "file_path": "<test-root>/config/projects/<encoded-project>/memory/demo-review-label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01E1FtoABR9bucmf8oWuxKUW",+ "type": "tool_result",+ "content": "1\t---\n2\tname: demo-review-label\n3\tdescription: The current demo review label for this project is CEDAR-915 (OPAL-742 is retired)\n4\tmetadata:\n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007\n8\t modified: 2026-10-21T03:38:56.849Z\n9\t---\n10\t\n11\tThe current demo review label is CEDAR-915. The previous label, OPAL-742, is retired. Do not use it.\n12\t\n13\t**Why:** The user replaced OPAL-742 with CEDAR-915 on 2026-10-21, in a disposable memory experiment.\n14\t\n15\t**How to apply:** Use CEDAR-915 whenever a demo review label is needed.\n16\t"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "f8d72520-8ea7-4fe0-a16b-c1e677cbd60d",+ "answer_extract": "CEDAR-915"+ }+]++```++### recall-removed++```json++[+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "f7fa9d37-9484-4d66-9e3b-17851ed0f95a",+ "answer_extract": "UNKNOWN"+ }+]++```++### File snapshots++#### snapshots/after-correction/MEMORY.md++SHA256: c550fb5898c72a7b12239d306d6b1041efeb15e2ea60fa55552e7b7d861e2b8c++```markdown++- [Demo review label](demo-review-label.md) — current demo review label is CEDAR-915 (OPAL-742 retired)+++```++#### snapshots/after-correction/demo-review-label.md++SHA256: 20c49da0c9de434450e4d5a30b41395c4f33dc5a7e76839d9e6ded576d14cee2++```markdown++---+name: demo-review-label+description: The current demo review label for this project is CEDAR-915 (OPAL-742 is retired)+metadata:+ node_type: memory+ type: project+ originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007+ modified: 2026-10-21T03:38:56.849Z+---++The current demo review label is CEDAR-915. The previous label, OPAL-742, is retired. Do not use it.++**Why:** The user replaced OPAL-742 with CEDAR-915 on 2026-10-21, in a disposable memory experiment.++**How to apply:** Use CEDAR-915 whenever a demo review label is needed.+++```++#### snapshots/after-removal/MEMORY.md++SHA256: 37e414b60756a00a80760f95693fc6fd21936487334ff9a78f0464ba98596afc++```markdown++# Disposable test memory++No saved project preferences.+++```++#### snapshots/after-save/MEMORY.md++SHA256: 0b421e28e4c9834fe214b4a5fc18232a2d75dd36f023dcdc181df91d04c4056d++```markdown++- [Demo review label](demo-review-label.md) — demo review label is OPAL-742+++```++#### snapshots/after-save/demo-review-label.md++SHA256: 185980317c82e6a1b6677193702231e730b85f289d047a47fb7c76b408713620++```markdown++---+name: demo-review-label+description: The demo review label for this project is OPAL-742+metadata:+ node_type: memory+ type: project+ originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007+ modified: 2026-10-21T03:38:09.753Z+---++The demo review label is OPAL-742.++**Why:** The user set this as a persistent project preference (stated 2026-10-21, in a disposable memory experiment).++**How to apply:** Use OPAL-742 whenever a demo review label is needed.+++```++#### snapshots/removed-demo-review-label.md++SHA256: 20c49da0c9de434450e4d5a30b41395c4f33dc5a7e76839d9e6ded576d14cee2++```markdown++---+name: demo-review-label+description: The current demo review label for this project is CEDAR-915 (OPAL-742 is retired)+metadata:+ node_type: memory+ type: project+ originSessionId: 756434b4-dae6-4e48-b1b8-ab11b3148007+ modified: 2026-10-21T03:38:56.849Z+---++The current demo review label is CEDAR-915. The previous label, OPAL-742, is retired. Do not use it.++**Why:** The user replaced OPAL-742 with CEDAR-915 on 2026-10-21, in a disposable memory experiment.++**How to apply:** Use CEDAR-915 whenever a demo review label is needed.+++```++## Earlier custom-directory test 2.1.185++### save++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01Urw4FPHXvF13AU7vL9eThA",+ "name": "Write",+ "input": {+ "file_path": "<old-test-root>/memory/project_demo_review_label.md",+ "content": "---\nname: project-demo-review-label\ndescription: Demo review label identifier for the project\nmetadata:\n type: project\n---\n\nDemo review label: OPAL-742\n\n**Why:** Persistent project preference for tracking demo reviews.\n\n**How to apply:** Use this label when referencing or tagging demo review work in the project.\n"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01Urw4FPHXvF13AU7vL9eThA",+ "type": "tool_result",+ "content": "File created successfully at: <old-test-root>/memory/project_demo_review_label.md (file state is current in your context — no need to Read it back)"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "25f99130-085d-452e-b0e1-31a82b8f78bf",+ "answer_extract": null+ }+]++```++### recall-before-correction++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01JJCaKBgnaK1nRHzEeDADAi",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory/MEMORY.md"+ }+ },+ {+ "type": "tool_result",+ "content": "File does not exist. Note: your current working directory is <old-test-root>/repo.",+ "is_error": true,+ "tool_use_id": "toolu_bdrk_01JJCaKBgnaK1nRHzEeDADAi"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_019mA8xDZMiFginpQNBMaxmw",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory"+ }+ },+ {+ "type": "tool_result",+ "content": "EISDIR: illegal operation on a directory, read '<old-test-root>/memory'",+ "is_error": true,+ "tool_use_id": "toolu_bdrk_019mA8xDZMiFginpQNBMaxmw"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "32f0a8e3-4a94-4500-8ba0-463b8fc99dd8",+ "answer_extract": "UNKNOWN"+ }+]++```++### recall-after-index++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01NS5sESVFccNqkbMp4J1n7x",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory/project_demo_review_label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01NS5sESVFccNqkbMp4J1n7x",+ "type": "tool_result",+ "content": "1\t---\n2\tname: project-demo-review-label\n3\tdescription: Demo review label identifier for the project\n4\tmetadata: \n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 25f99130-085d-452e-b0e1-31a82b8f78bf\n8\t---\n9\t\n10\tDemo review label: OPAL-742\n11\t\n12\t**Why:** Persistent project preference for tracking demo reviews.\n13\t\n14\t**How to apply:** Use this label when referencing or tagging demo review work in the project.\n15\t"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "db9fbbfe-251c-4e5d-95b6-70a39bf254e0",+ "answer_extract": "OPAL-742"+ }+]++```++### correct++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_019XUsFv7wrUm2U7WNMUzheQ",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory/project_demo_review_label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_019XUsFv7wrUm2U7WNMUzheQ",+ "type": "tool_result",+ "content": "1\t---\n2\tname: project-demo-review-label\n3\tdescription: Demo review label identifier for the project\n4\tmetadata: \n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 25f99130-085d-452e-b0e1-31a82b8f78bf\n8\t---\n9\t\n10\tDemo review label: OPAL-742\n11\t\n12\t**Why:** Persistent project preference for tracking demo reviews.\n13\t\n14\t**How to apply:** Use this label when referencing or tagging demo review work in the project.\n15\t"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01CaGeQd6xHo6nyhfNBjUtUu",+ "name": "Edit",+ "input": {+ "replace_all": false,+ "file_path": "<old-test-root>/memory/project_demo_review_label.md",+ "old_string": "Demo review label: OPAL-742",+ "new_string": "Demo review label: CEDAR-915"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01CaGeQd6xHo6nyhfNBjUtUu",+ "type": "tool_result",+ "content": "The file <old-test-root>/memory/project_demo_review_label.md has been updated successfully. (file state is current in your context — no need to Read it back)"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "71e0fa49-1825-4048-8f65-f1f9226405db",+ "answer_extract": null+ }+]++```++### recall-after-correction++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01JpZmSGbTFmS4NNqr27smwh",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory/project_demo_review_label.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01JpZmSGbTFmS4NNqr27smwh",+ "type": "tool_result",+ "content": "1\t---\n2\tname: project-demo-review-label\n3\tdescription: Demo review label identifier for the project\n4\tmetadata: \n5\t node_type: memory\n6\t type: project\n7\t originSessionId: 25f99130-085d-452e-b0e1-31a82b8f78bf\n8\t---\n9\t\n10\tDemo review label: CEDAR-915\n11\t\n12\t**Why:** Persistent project preference for tracking demo reviews.\n13\t\n14\t**How to apply:** Use this label when referencing or tagging demo review work in the project.\n15\t"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "c2865614-53f5-4501-9058-f87105a79a1d",+ "answer_extract": "CEDAR-915"+ }+]++```++### recall-after-removal++```json++[+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01LxyT3GQaDSMvCKS6kAMhFE",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory/MEMORY.md"+ }+ },+ {+ "tool_use_id": "toolu_bdrk_01LxyT3GQaDSMvCKS6kAMhFE",+ "type": "tool_result",+ "content": "1\t# Demo memory index\n2\t\n3\tNo saved test preferences.\n4\t"+ },+ {+ "type": "tool_use",+ "id": "toolu_bdrk_01SaGPhsxfdC1Q7YL9g9s8ir",+ "name": "Read",+ "input": {+ "file_path": "<old-test-root>/memory"+ }+ },+ {+ "type": "tool_result",+ "content": "EISDIR: illegal operation on a directory, read '<old-test-root>/memory'",+ "is_error": true,+ "tool_use_id": "toolu_bdrk_01SaGPhsxfdC1Q7YL9g9s8ir"+ },+ {+ "type": "result_status",+ "is_error": false,+ "session_id": "a7edcb75-aa2e-47ff-97e6-58f34e713c40",+ "answer_extract": "UNKNOWN"+ }+]++```++### File snapshots++#### snapshot-after-save/project_demo_review_label.md++SHA256: f6437758e5a221a318dc85cecbbacf41002c455c63febfc07e73a1d4e00120f2++```markdown++---+name: project-demo-review-label+description: Demo review label identifier for the project+metadata:+ node_type: memory+ type: project+ originSessionId: 25f99130-085d-452e-b0e1-31a82b8f78bf+---++Demo review label: OPAL-742++**Why:** Persistent project preference for tracking demo reviews.++**How to apply:** Use this label when referencing or tagging demo review work in the project.+++```++#### snapshot-after-correction/MEMORY.md++SHA256: 6cd2b9d20d851b8c26a2f9137031b0c274c2700e21abd6f75fb948a4f104de56++```markdown++# Demo memory index++- Review label preference: [project_demo_review_label.md](project_demo_review_label.md)+++```++#### snapshot-after-correction/project_demo_review_label.md++SHA256: 2911776542dc179732b4ae6ed428f51986f1b892766a2d327d2baa956f164520++```markdown++---+name: project-demo-review-label+description: Demo review label identifier for the project+metadata:+ node_type: memory+ type: project+ originSessionId: 25f99130-085d-452e-b0e1-31a82b8f78bf+---++Demo review label: CEDAR-915++**Why:** Persistent project preference for tracking demo reviews.++**How to apply:** Use this label when referencing or tagging demo review work in the project.+++```++## Author interventions++Current release: after the corrected recall, the author moved demo-review-label.md out of active memory and replaced MEMORY.md with a no-preferences index. No manual intervention between current save and first recall. Earlier release: author added a missing index pointer before the successful recall. Both removals were test-file edits, not privacy-erasure demonstrations.++## Review claims++Current correction used Write for topic and index, not Edit. The earlier correction provides the Edit event. The fresh current recalls directly read the topic. Startup index injection is model-reported, not independently established. Index itself contains the answer; topic read is established, exclusive causal source is not.diff --git a/src/web/blog/src/content/claude-code-memory.mdx b/src/web/blog/src/content/claude-code-memory.mdxnew file mode 100644index 000000000..4d79accfc--- /dev/null+++ b/src/web/blog/src/content/claude-code-memory.mdx@@ -0,0 +1,200 @@+export const jsonLd = {+ "@context": "https://schema.org",+ "@type": "FAQPage",+ "mainEntity": [+ {+ "@type": "Question",+ "name": "Why does memory work in one project but not another?",+ "acceptedAnswer": {+ "@type": "Answer",+ "text": "Compare the actual save destination with the memory folder shown in the second project before changing the note. Our experiment used one Git project and one configuration directory; it did not test transfer to another repository or machine."+ }+ },+ {+ "@type": "Question",+ "name": "Should I add an index entry when recall fails?",+ "acceptedAnswer": {+ "@type": "Answer",+ "text": "Check first. Our 2.1.304 run created its own index. The older 2.1.185 custom-directory run needed a manual pointer before recall succeeded. That earlier repair is evidence for that setup, not a universal installation step."+ }+ },+ {+ "@type": "Question",+ "name": "Which should I correct: memory or project instructions?",+ "acceptedAnswer": {+ "@type": "Answer",+ "text": "Correct the source that owns the fact. A standing project rule belongs in maintained instructions; a retired preference needs its stale memory updated. If both mention it, inspect both and repeat the fresh-session check. Adding another contradictory note leaves the conflict in place."+ }+ },+ {+ "@type": "Question",+ "name": "Does compaction delete saved memory files?",+ "acceptedAnswer": {+ "@type": "Answer",+ "text": "Compaction reduces conversation context. A missing answer does not prove a saved file was deleted. Inspect the file and check whether the session can access it."+ }+ },+ {+ "@type": "Question",+ "name": "Can subagents use the main session's auto memory?",+ "acceptedAnswer": {+ "@type": "Answer",+ "text": "Do not assume they inherit it. The official subagent guide describes separate memory configuration and context behavior; forks have different inheritance behavior. Check the agent type and version. For the broader distinction, see Claude Code subagents and independent agents."+ }+ }+ ]+};++export const metadata = {+ slug: "claude-code-memory",+ title: "Claude Code Memory: Persistent Memory Across Sessions",+ date: "2026-10-22",+ author: "Alook Team",+ excerpt: "Check Claude Code's native memory, inspect saved notes, and verify recall in a fresh session. Follow the steps and fix stale facts.",+ readingTime: "9 min read",+ image: "/blog/claude-code-memory/hero.webp",+};++[](/blog/claude-code-memory/hero.webp)++**Claude Code has native persistent memory. Start with its built-in notes before deciding whether you need a plugin.** Run the three-step check below to confirm memory works for your project.++## Check Claude Code memory in three steps++1. **Save a harmless fact.** In a disposable project, ask Claude to remember a fictional review label, such as `OPAL-742`, using auto memory. Ask it to leave repository instructions unchanged.+2. **Inspect the files.** Open `/memory`, then the auto memory folder. Check the saved note and its index entry. A promise to remember is not proof of a successful write.+3. **Ask in a fresh session.** Exit and launch `claude` again in the same project, without resume flags. Ask “What review label should this demo project use?” Keep the label itself out of this question.++Compare the answer with the saved files and any visible read record. If you only have the answer, you have checked recall, but have not independently confirmed its loading path.++## What does Claude Code remember between sessions?++Claude Code can carry project instructions and saved auto-memory notes into new sessions. Resuming a session continues an earlier conversation. Use the carrier that matches what you need to preserve.++| Carrier | Use it for | What to check |+|---|---|---|+| Instruction files | Rules the project expects an agent to follow | Which files this client selected |+| Auto memory | Selected notes that remain useful later | Whether the note exists and is available when needed |+| Session history and resume | Continuing an earlier conversation | Whether you reopened the intended session |++### CLAUDE.md and conditional AGENTS.md loading++Put a standing requirement in an instruction file. A note about an earlier experiment belongs elsewhere if it is likely to change.++The current [official memory documentation](https://code.claude.com/docs/en/memory) makes `AGENTS.md` loading conditional: direct support requires v2.1.277 or later, and local `CLAUDE.md` or `CLAUDE.local.md` files affect the default choice. `/config` can select both; unsupported sessions can import `AGENTS.md` through `CLAUDE.md`. Check the selected files rather than assuming that every instruction file is loaded.++### Where is Claude Code auto memory stored?++The [documented default location](https://code.claude.com/docs/en/memory#storage-location) is `~/.claude/projects/<project>/memory/`, with a `MEMORY.md` index and separate topic notes. Use `/memory` to confirm the location for your session; custom configuration can change it. Our experiment used a separate configuration directory, so its `config/projects/...` path below is a test location.++[](/blog/claude-code-memory/memory-files.webp)++*Memory-file schematic. Both the index and topic note contain the test label; custom configuration can change the memory location.*++### Session history and resume++Use resume when you want to continue the earlier conversation itself. The [session guide](https://code.claude.com/docs/en/sessions) documents `claude --continue` for the most recent session in the current directory and `claude --resume` for choosing another.++For a cross-session memory check, start a separate session so the earlier conversation does not supply the answer.++## Verify memory in a new Claude Code session++Open `/memory` to check that auto memory is enabled, save a test note, then ask for it in a new session. Inspect the saved files and available read records to separate a successful save from successful recall.++### Use the interactive memory controls++The following route is based on the [documented `/memory` controls](https://code.claude.com/docs/en/memory#view-and-edit-with-memory), checked on October 22, 2026. Our hands-on test used CLI calls; the interactive steps are documentation-based and were not tested here.++Run `claude --version` and record it. Open Claude Code from your terminal in the intended project, then:++- Enter `/memory` and check the auto memory toggle. If it is off, enable it in a directly launched terminal session before testing.+- Select the option to open the auto memory folder. After your save request, inspect the note and `MEMORY.md`; compare the actual path and contents with what Claude reported.+- Use `/context` to check loaded instruction files. The instruction-file list answers a different question from whether a topic note was read.+- Exit, start `claude` again from the same project, and ask the recall question. Inspect whatever read activity your client exposes.++If the toggle cannot be enabled here, restart directly from your terminal. Avoid selecting a nonexistent instruction-file entry just to inspect it: `/memory` can create that file.++### What we tested with the CLI++We ran the save, recall, correction and removal checks on macOS with **Claude Code 2.1.304**, the stable release returned by the official download endpoint on **October 21, 2026**.++An empty Git project and separate `CLAUDE_CONFIG_DIR` kept the test notes apart from daily work. We used default memory placement, with no `autoMemoryDirectory` or `autoMemoryEnabled` override. Tools were limited to Read, Write and Edit, with project/local settings sources and a strict empty MCP configuration. These controls narrowed storage and tool access; machine-level instruction ancestry was not fully isolated.++Each `-p` call started a separate conversation without `--continue` or `--resume`. The [CLI reference](https://code.claude.com/docs/en/cli-reference) documents these output and session controls. We inspected successful tool results and file snapshots, rather than treating Claude's explanation as an execution log.++Claude wrote `demo-review-label.md` and `MEMORY.md` under `config/projects/<encoded-project>/memory/`. Its index entry was:++```markdown+- [Demo review label](demo-review-label.md) — demo review label is OPAL-742+```++The next call returned `OPAL-742` and recorded a successful read of the topic file. Both files contained the answer, so this does not prove that the topic was its only source. It does establish that the topic was read. We made no manual index repair in this run.++### Separate observed recall from an unverified loading path++Our results were:++| Test state | Direct observation | Fresh-session answer |+|---|---|---|+| 2.1.304, default memory placement | Claude wrote topic and index; next call read topic | `OPAL-742` |+| Saved preference corrected through Claude | File changes inspected; next call checked separately | `CEDAR-915` |+| Disposable note and index entry removed | Author intervention, followed by a separate recall | `UNKNOWN` |+| Earlier 2.1.185, custom memory directory | Topic created without index; first recall failed | `UNKNOWN` |++The earlier failure is a troubleshooting example for that setup, not the observed default behavior of 2.1.304. This is one project's save/recall/correction exercise, rather than a recall-rate benchmark. Interactive controls, other machines and subagents were outside the test.++[](/blog/claude-code-memory/cli-evidence.webp)++*CLI test-record excerpts, Claude Code 2.1.304, October 21, 2026. Paths are normalized; this is a layout of selected tool events and answers, not a terminal screenshot. The index also contained the answer, so the topic read does not prove it was the only source. See the [complete sanitized test record](/blog/claude-code-memory/test-record.md).*++## Fix Claude Code memory that is not working++Check the save destination, index entry, project scope and available read records. Fix the first failed step, then repeat the recall check in a fresh session; if an old value persists, look for another copy or conflicting instruction.++### Saved files are not being loaded++Open the intended memory location and compare it with the file your earlier save actually created. Look for a missing index pointer, a different project directory, or a settings mismatch before adding another memory tool.++| Symptom | First check | Useful evidence |+|---|---|---|+| Save was reported, but no note is found | Actual write result and destination | File exists with the intended content |+| Note exists, but recall fails | Index, project scope, and available read records | Missing pointer, wrong path, or a read error |+| Correct note was read, but answer is wrong | Other instructions and the current question | Conflicting input or an unsupported conclusion |++### An edited or deleted note still appears++Ask Claude to retire the old value and update the saved preference. Then inspect every changed memory file and ask the same recall question in a new conversation. Our test replaced `OPAL-742` with `CEDAR-915`: successful `Write` events rewrote the topic and index, and the next call read the topic and answered with the new value.++For the removal check, we archived the disposable topic outside the memory directory and removed its index pointer. The next conversation answered `UNKNOWN`. This was a manual file-and-index change, not a test of a delete button or a privacy-erasure guarantee.++If an old value still appears, inspect the active conversation, other files and the question itself for another copy.++## Do you need a Claude Code memory plugin?++Keep native memory if your task is to retain a few project preferences and the save/recall check works. Consider an extension only for a specific missing capability, such as searching a large archive or retrieving notes from another client. Before installing it, check what it captures, where it stores data and who can retrieve it; our test did not compare plugins.++[Alook](https://alook.ai/) provides shared discussions where you can post a changed decision and its source for the people and bots doing the work. That handoff does not synchronize Claude Code's private memory; see [sharing context between agents](/blog/shared-context-between-agents).++When switching runtimes, carry the approved decision and the next verification step explicitly. The guide to [keeping context across coding agent sessions](/blog/keep-context-across-coding-agent-sessions) covers those portable records. Check the destination tool's memory setup before expecting it to recall them.++## Claude Code memory FAQs++### Why does memory work in one project but not another?++Compare the actual save destination with the memory folder shown in the second project before changing the note. Our experiment used one Git project and one configuration directory; it did not test transfer to another repository or machine.++### Should I add an index entry when recall fails?++Check first. Our 2.1.304 run created its own index. The older 2.1.185 custom-directory run needed a manual pointer before recall succeeded. That earlier repair is evidence for that setup, not a universal installation step.++### Which should I correct: memory or project instructions?++Correct the source that owns the fact. A standing project rule belongs in maintained instructions; a retired preference needs its stale memory updated. If both mention it, inspect both and repeat the fresh-session check. Adding another contradictory note leaves the conflict in place.++### Does compaction delete saved memory files?++Compaction reduces conversation context. A missing answer does not prove a saved file was deleted. Inspect the file and check whether the session can access it.++### Can subagents use the main session's auto memory?++Do not assume they inherit it. The [official subagent guide](https://code.claude.com/docs/en/sub-agents) describes separate memory configuration and context behavior; forks have different inheritance behavior. Check the agent type and version. For the broader distinction, see [Claude Code subagents and independent agents](/blog/claude-code-subagents-vs-independent-agents).diff --git a/src/web/blog/src/lib/blog/image-assets.json b/src/web/blog/src/lib/blog/image-assets.jsonindex e0b64e998..263d92b37 100644--- a/src/web/blog/src/lib/blog/image-assets.json+++ b/src/web/blog/src/lib/blog/image-assets.json@@ -35,6 +35,9 @@"/blog/claude-code-and-codex-same-team/review-loop-20261015.png": {"width":800,"height":1138,"srcSet":"/blog/_generated/2918fc3990127414-480.webp 480w, /blog/claude-code-and-codex-same-team/review-loop-20261015.png 800w"},"/blog/claude-code-dynamic-workflow-alternative/audit-to-handoff.webp": {"width":1000,"height":1400,"srcSet":"/blog/_generated/0ac21039c904f1a6-480.webp 480w, /blog/_generated/0ac21039c904f1a6-960.webp 960w, /blog/claude-code-dynamic-workflow-alternative/audit-to-handoff.webp 1000w"},"/blog/claude-code-dynamic-workflow-alternative/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/367ac6d6ab928946-480.webp 480w, /blog/_generated/367ac6d6ab928946-960.webp 960w, /blog/claude-code-dynamic-workflow-alternative/hero.webp 1200w"},+ "/blog/claude-code-memory/cli-evidence.webp": {"width":1200,"height":840,"srcSet":"/blog/_generated/f3a93b193ed2d81d-480.webp 480w, /blog/_generated/f3a93b193ed2d81d-960.webp 960w, /blog/claude-code-memory/cli-evidence.webp 1200w"},+ "/blog/claude-code-memory/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/a76c28a557500cc3-480.webp 480w, /blog/_generated/a76c28a557500cc3-960.webp 960w, /blog/claude-code-memory/hero.webp 1200w"},+ "/blog/claude-code-memory/memory-files.webp": {"width":1200,"height":740,"srcSet":"/blog/_generated/12563ec337a0b072-480.webp 480w, /blog/_generated/12563ec337a0b072-960.webp 960w, /blog/claude-code-memory/memory-files.webp 1200w"},"/blog/claude-code-subagents-vs-independent-agents/architecture-compare.webp": {"width":1400,"height":933,"srcSet":"/blog/_generated/5898f03690f372b0-480.webp 480w, /blog/_generated/5898f03690f372b0-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/architecture-compare.webp 1400w"},"/blog/claude-code-subagents-vs-independent-agents/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/2a0837c3d61bfdca-480.webp 480w, /blog/_generated/2a0837c3d61bfdca-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/hero.webp 1200w"},"/blog/claude-code-subagents-vs-independent-agents/three-layers.webp": {"width":1400,"height":933,"srcSet":"/blog/_generated/622dcce0a4478293-480.webp 480w, /blog/_generated/622dcce0a4478293-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/three-layers.webp 1400w"},diff --git a/src/web/blog/src/lib/blog/topics.test.ts b/src/web/blog/src/lib/blog/topics.test.tsindex 410bd9a90..f0293b5ec 100644--- a/src/web/blog/src/lib/blog/topics.test.ts+++ b/src/web/blog/src/lib/blog/topics.test.ts@@ -74,6 +74,7 @@ describe("blogTopics", () => {"claude-code-and-codex-same-team","claude-code-dynamic-workflow-alternative","keep-context-across-coding-agent-sessions",+ "claude-code-memory","share-claude-code-session","multiple-ai-agents-edit-same-repository","prevent-claude-code-codex-duplicating-work",@@ -147,6 +148,8 @@ describe("blogTopics", () => {"Choose between session workflows and persistent coordination","keep-context-across-coding-agent-sessions":"Carry decisions across coding agent sessions",+ "claude-code-memory":+ "Verify Claude Code memory across fresh sessions and fix stale notes","share-claude-code-session":"Share a Claude Code session or transcript so a teammate can review or continue the work","multiple-ai-agents-edit-same-repository":diff --git a/src/web/blog/src/lib/blog/topics.ts b/src/web/blog/src/lib/blog/topics.tsindex eb8b4b2b2..efa8fa46b 100644--- a/src/web/blog/src/lib/blog/topics.ts+++ b/src/web/blog/src/lib/blog/topics.ts@@ -58,6 +58,10 @@ export const blogTopics = [slug: "keep-context-across-coding-agent-sessions",userJob: "Carry decisions across coding agent sessions",},+ {+ slug: "claude-code-memory",+ userJob: "Verify Claude Code memory across fresh sessions and fix stale notes",+ },{slug: "share-claude-code-session",userJob: "Share a Claude Code session or transcript so a teammate can review or continue the work",