사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/rohitg00/agentmemory --skill agentmemory-architecture시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
agentmemory is a memory server for coding agents. It runs locally, captures observations, indexes them for hybrid retrieval, and serves them back over REST and MCP. Worker Compose runs the pinned iii engine with AgentMemory and the registry state and http workers. The state worker uses a file-backed KV store by default, with Redis available by configuration; it is not SQLite.
iii primitives
Everything is a function, a trigger, or worker state on the iii engine. There is no separate plugin system; the worker registers functions (mem::*) and HTTP triggers (api::*) and the engine routes calls. agentmemory does not bypass iii; new capability is a new function plus a trigger.
Retrieval model
Recall combines BM25 keyword search with configured vector similarity and graph expansion. A clean installation has no embedding provider and uses BM25 without an API key. Set EMBEDDING_PROVIDER=local to enable on-device embeddings, which download a model once. A remote embedding provider runs only when EMBEDDING_PROVIDER names it. LLM summaries, consolidation and reflection run only when AGENTMEMORY_LLM_PROVIDER selects a provider or AGENTMEMORY_ALLOW_AGENT_SDK=true turns on the Claude Agent SDK fallback; a key in the environment alone does not turn them on. Per-observation LLM compression also needs AGENTMEMORY_AUTO_COMPRESS=true.
Data boundary
Captured prompts, tool inputs and outputs, and memories stay in the local store. They leave the machine only through options the user turns on: a selected LLM provider, the Agent SDK fallback (AGENTMEMORY_ALLOW_AGENT_SDK=true), a remote embedding provider, a Redis state backend, or mesh sync to peer servers the user registers.
Storage and lifecycle
Memories carry content, concepts, files, importance, and timestamps, grouped into sessions and optionally linked to commits. A lifecycle of capture, compress, consolidate, and forget keeps the store useful over time rather than letting it grow unbounded.
Ports
REST defaults to port 3111, the viewer to 3113, and the internal engine WebSocket to 49134. Use --port <N> or --instance <N> to select another local runtime.
Viewer
A real-time web viewer at http://localhost:3113 shows memory building as sessions run, with authenticated SSE updates over the REST port. Useful for demos and for confirming capture is working.
See also
- agentmemory-mcp-tools and agentmemory-rest-api for the surfaces.
- agentmemory-hooks for automatic capture.
- agentmemory-config for ports and feature flags.