Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
The user wants to resume work. Optional cwd override: $ARGUMENTS
memory_sessions { "limit": 20 }
Pick the most recent session whose cwd matches this project, then:
memory_recall { "query": "<session top concepts>", "limit": 10 }.
Expected output:
Resuming 7f3a9c2 "Auth refresh rework".
Open question: should logout revoke all device tokens or just the current one?
Next step: decide revoke scope, then update auth/logout.ts.
Match the session by directory boundary, not raw prefix, so a sibling repo never gets mistaken for this one. Never invent observations for an empty session.
$ARGUMENTS is given, normalize it to absolute
(path.resolve(process.cwd(), $ARGUMENTS)); else use the cwd.memory_sessions. Pick the most recent session whose normalized cwd
matches by directory boundary: equality, OR cwd.startsWith(projectPath + sep),
OR projectPath.startsWith(cwd + sep). Prefer completed over abandoned.
No match: report that this project has no matching session and stop. Do not
substitute a different project's session.summary or recent conversation observations whose narrative
ends in ?.memory_recall on the top concepts, limit 10. Check each result's session or
project provenance before including it; a query alone does not enforce scope.WRONG: session.cwd.startsWith(projectPath) matches /repo-a-staging when the
project is /repo-a, resuming the wrong repo's session.
RIGHT: session.cwd === projectPath || session.cwd.startsWith(projectPath + sep),
a directory-boundary check that cannot cross sibling repos.
recap, session-history, recall: same session data, broader views.See ../_shared/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.
日本語の概要は準備中です。原文の説明を表示しています。