User-aware agents Open-source memory and context for user-aware agents.
Remnic helps agents understand the people they work with: their
preferences, projects, constraints, decisions, patterns, and definition
of good, so they can help with fewer unnecessary questions.
Technical version
A memory and context layer with control surfaces.
Remnic is an open-source memory and context layer for user-aware agents,
focused on scoped memory, provenance, retrieval quality, user
correction, and ask-versus-act decisions.
Local-first storage is a trust feature. The category is user-aware
agents: systems that need to understand a user over time without
turning personalization into uncontrolled surveillance.
1 User model, not just memory storage
Most memory tools store facts. Remnic models working context: what the
agent needs to understand about this user to act well right now.
- Preferences, goals, projects, constraints, and current priorities
- Communication style, risk tolerance, people, and relationships
- Past decisions, definitions of good, and repeated patterns
- "Ask me before..." and "do not use this outside..." rules
2 Provenance on retrieved memory
Retrieved memory should carry enough metadata for the agent and user
to understand why it appeared and whether it belongs in the current
context.
- Source, creation time, scope, retrieval reason, and confidence
- Staleness, correction state, and trust-zone state
- Safety checks for whether memory can be used in the current scope
- Inspection paths for why memory was remembered, corrected, or forgotten
3 Scopes and boundaries
Personalization without boundaries becomes surveillance.
Personalization with correction and control becomes agency.
- Personal, work, client, project, repo, tool, and temporary scopes
- Private and do-not-use-outside-this-context boundaries
- Project and repo memory that stays isolated where it should
- Human-readable storage so users can inspect and edit context
4 Ask-versus-act decisions
A good agent should spend the user's attention carefully. Remnic can
help decide whether an agent should ask, draft, act, refuse, or
escalate.
- Action confidence for deciding when memory is enough
- Interruption budgeting for asking fewer low-value questions
- Escalation when scope, confidence, or risk is unclear
- Refusal or draft-only behavior when boundaries require it
Memory evals
Agent memory without evals is vibes with a database.
Remnic treats memory quality as something to measure. The eval surface
should answer whether memory reduced repeated context, reduced
unnecessary clarification, retrieved the right memory, avoided stale
memory harm, respected scope, asked when it should have asked, acted
when it had enough context, and improved the final output.
Demos to build toward
Where user-aware memory becomes concrete.
MCP and ChatGPT Apps compatibility
MCP server, ChatGPT Apps-compatible demo, memory inspection UI,
"why did you remember this?" UI, and forget/correct/scope controls.
Agentic commerce
Buyer memory for brand preferences, size and fit, budget thresholds,
purchase constraints, excluded products, gift preferences, shipping
urgency, and ask-before-checkout rules.
Developer workflows
Repo conventions, preferred architecture patterns, test
expectations, release process, past bugs, review preferences, and
ask-before-changing-public-API rules.