How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The user wants a recap. Time window args: $ARGUMENTS
memory_sessions { "project": "<current-project-id>", "limit": 30 }
Then per surviving session: memory_recall { "query": "<top concepts>", "project": "<current-project-id>", "limit": 3 }.
When an agent is requested, pass the same agentId to both calls.
Expected output:
2026-06-07
7f3a9c2 · "Auth refresh rework" · 14 obs · completed
- [8] Rotate refresh tokens on every use
3 sessions across 2 days, 41 observations.
Only summarize sessions and observations the tools returned. An empty window is a real answer, not a prompt to invent activity.
$ARGUMENTS: today = current local date; this week = last 7 days;
last <n> or bare numeric = most recent N; empty = last 10.memory_sessions with the exact recorded project identifier when known
and the requested agentId. Follow nextCursor with the same filters until
the requested window is covered or pages end. When the project identifier is
unknown, match normalized cwd by directory boundary across pages before
applying the time/count window. Sort by startedAt descending.memory_recall, retaining project/agent scope,
and verify each result belongs to that session before including it.WRONG: window is empty, so you summarize "a productive week of auth work" from memory of the conversation.
RIGHT: "No sessions in the last 7 days for this project."
memory_recall, not paraphrase.handoff, session-history, recall: same session data, different lens.See TROUBLESHOOTING.md if memory_sessions or memory_recall is not available.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
日本語の概要は準備中です。原文の説明を表示しています。
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and diagnose local agentmemory, including MCP, environment variables, ports, and feature flags. Use when getting started, checking a connection, enabling a feature, configuring auth, or explaining why a feature is off by default.
日本語の概要は準備中です。原文の説明を表示しています。
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
日本語の概要は準備中です。原文の説明を表示しています。
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
日本語の概要は準備中です。原文の説明を表示しています。
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.
日本語の概要は準備中です。原文の説明を表示しています。