Trace a file, function, or line through Git history to the agent session linked to its commit. It presents recorded commit details, session summaries, and important observations to help explain the change.
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
Review the instructions the agent will receive before you install.
The user wants commit context for: $ARGUMENTS
git blame -L 40,52 src/auth/refresh.ts # -> SHA 9a1b2c3d
memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }
Expected output:
9a1b2c3 on main by dev: "rotate refresh tokens"
Linked session 7f3a9c2 "Auth refresh rework", 14 obs.
Report only what git and the lookup return. When the lookup gives commit: null,
the commit predates session linking; do not invent intent.
git blame -L <start>,<end> <file> for a line range;
git log -L :<function>:<file> for a function; git log -n 1 -- <file> for a
bare path.memory_commit_lookup { "sha": "<full-sha>" }.memory_recall when available.WRONG: lookup returns { "commit": null }, you narrate "the agent was
refactoring auth" from the diff alone.
RIGHT: "This commit predates session linking, so there is no recorded agent
session. From git show: it changed token rotation in refresh.ts."
commit: null reported as "predates linking", no fabricated session.commit-history: list many agent-linked commits at once.recall: dig deeper into the linked session's observations.See TROUBLESHOOTING.md if memory_commit_lookup is not available.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.
Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.
Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.