Per-project database
Decisions, lessons, knowledge, handoffs and interfaces, never compacted.
Platform · Project Memory
Memory that does not compact.
Context windows fill and forget. agnte keeps what matters in a project database every agent reads.
Live in productionTimePeace
AgentWhy does the invoice export use UTC?example
illustrative
What is Project Memory in agnte?
agnte project memory stores decisions, lessons, knowledge, handoffs and interfaces in a database per project instead of a chat window, so nothing is lost to context compaction. Every machine in the fleet reads the same memory, agents share lessons over an MCP bus, and every decision is traceable to who made it and why.
Capabilities
What Project Memory does
TimePeace
Agents talk to each other
Ask and answer, handoffs and shared lessons over an MCP bus.
Curator roles
A knowledge curator and code investigator keep memory de-duplicated and findable.
Per-project isolation
Each project has its own models, instructions, roles, policy and knowledge.
Traceable decisions
Who decided, why and from which evidence, in a 1.42M-event journal.
Proof from production
Running today, measured.
8,574memory entries
7,893agent-to-agent messages
1,437handoffs
Source: Live agnte database, 2026-10-12.
How it works
How Project Memory works
- Agent learns
- Written to memory
- Shared across fleet
- Read by later agents
FAQ
Questions about Project Memory
How is this different from a context window?
A context window compacts and forgets. agnte memory lives in a database per project and is never compacted.
Do projects share memory?
No. Each project is isolated, which avoids contradictions between projects.
Can I add knowledge myself?
Yes, you can add instructions or knowledge at any time.
Related