Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says "recall", "what did we do about", "did we ever", "have we seen", or needs context from past sessions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The user wants to recall past context about: $ARGUMENTS
memory_smart_search { "query": "jwt refresh token rotation", "limit": 10 }
Expected output:
2 results across 2 sessions.
[importance 8] decision · "Rotate refresh tokens on every use" (session 7f3a9c21)
[importance 5] code · "limit.ts counts per-IP" (session b21d004e)
Only surface what the tool returned. Never fabricate an observation, a session id, or an importance score. If nothing comes back, say so.
memory_smart_search with the user's text as query and limit: 10.
Pass project when the user scopes to a specific repo and agentId when
they request one agent's history.
Use targetLayer: "memory" for explicitly saved knowledge, or
targetLayer: "observation" for captured activity. Omit it for mixed search.memory_smart_search with the selected IDs as a
comma-separated expandIds string and the same project, agent, and layer
filters. If expansion fails or the record is no longer available, report
that limitation; a title alone is not the full fact.memory_recall, inspect matched_count, excluded_by_budget, and
content_truncated before treating an empty or shortened response as absent
knowledge. Recover full content with memory_smart_search using expandIds
and the same project, agent, and layer filters. minimum_budget reports the
estimated budget needed for a minimal preview when the budget is too small.WRONG: results are empty, so you write "We probably discussed token expiry last week" from assumption.
RIGHT: "No memories matched that query. Try refresh token, session expiry,
or auth rotation."
remember: the write side; recall retrieves what it stores.recap, handoff, session-history: session-scoped views of the same data.memory-discipline: when to run this search unprompted.See TROUBLESHOOTING.md if memory_smart_search 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.
日本語の概要は準備中です。原文の説明を表示しています。