
Agentmemory Architecture
- 6.4k installs
- 26.6k repo stars
- Updated August 3, 2026
- rohitg00/agentmemory
agentmemory-architecture is an agent skill: How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memor
About
The agentmemory-architecture skill 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.. 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. It is built on the iii engine. 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 is hybrid: BM25 keyword search
- Covers agentmemory-architecture quick start, workflow steps, and reference pointers from SKILL.md.
- Tagged for stage build and subphase backend in the closed Skillselion taxonomy.
- Documents prerequisites, permissions filesystem, and compatible agents.
- Includes AEO tagMeta with task queries, keywords, and evidence quotes for discovery.
- Cross-links related skills and generated REFERENCE.md tables where the repo provides them.
Agentmemory Architecture by the numbers
- 6,371 all-time installs (skills.sh)
- +650 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #125 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
agentmemory-architecture capabilities & compatibility
- Capabilities
- agentmemory architecture documented workflow · quick start examples · reference parameter lookup · taxonomy aligned metadata · aeo discovery fields
- Use cases
- memory · documentation
What agentmemory-architecture says it does
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the vi
npx skills add https://github.com/rohitg00/agentmemory --skill agentmemory-architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 6.4k |
|---|---|
| repo stars | ★ 26.6k |
| Last updated | August 3, 2026 |
| Repository | rohitg00/agentmemory ↗ |
How do I run agentmemory-architecture correctly without guessing steps, tools, or parameters?
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
Who is it for?
Teams using agentmemory-architecture when SKILL.md triggers match the user request.
Skip if: Skip when the task is outside agentmemory-architecture documented triggers or sibling skill scope.
When should I use this skill?
User mentions agentmemory-architecture, related trigger phrases, or asks to follow this SKILL.md workflow.
What you get
Completed agentmemory-architecture workflow with outputs and checks defined in SKILL.md.
- agentmemory-architecture output per SKILL.md
By the numbers
- Stage build/backend
- Category AI & Agent Building
- Complexity advanced
Files
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. It is built on the iii engine.
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 is hybrid: BM25 keyword search plus vector similarity plus graph expansion over linked concepts. The default install needs no API key because embeddings run on-device and BM25 needs none. An LLM provider only adds richer summaries and auto-injection, both opt-in.
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 is the anchor at 3111. Streams = N+1 (3112), viewer = N+2 (3113), engine = N+46023 (49134). --instance N shifts the whole block by N*100.
Viewer
A real-time web viewer at http://localhost:3113 shows memory building as sessions run. 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.
Related skills
How it compares
agentmemory-architecture implements its own SKILL.md workflow rather than a generic substitute skill.
FAQ
Who is agentmemory-architecture for?
Agents and developers following the agentmemory-architecture SKILL.md guidance.
When should I use agentmemory-architecture?
When user intent matches description triggers and quick start scenarios.
Is agentmemory-architecture safe to install?
Review the Security Audits panel before production shell or network use.