Local semantic memory for coding agents
Local-only agent memory when mem0 and supermemory require servers.
The Open-Source AI Memory Layer
Memory deduplication and contradiction detection, but vector DBs already do semantic search.
AI/LLM application developers building multi-turn agents and conversational systems
Pinecone (vector search + metadata) · Weaviate (semantic search + versioning) · LanceDB (local vector store with fact extraction)
Tech stack: - TypeScript + Hono (fast, edge-ready) - Convex (real-time DB + vector search) - Gemini (embeddings + extraction)
What it does: # Store memory curl -X POST /v1/content -d '{"content": "User loves hiking, lives in SF"}'
# Recall naturally curl -X POST /v1/recall -d '{"query": "outdoor hobbies"}' # Returns: "User loves hiking" with assembled context
It handles the boring stuff – chunking, embeddings, deduplication, contradiction detection, versioning – so you can focus on your actual product.
Links: - GitHub: https://github.com/akhilponnada/aethene - API Docs: OpenAPI spec in repo
This is my first time launching anything publicly. Would love feedback – what's missing? What would make you actually use this? Roast my code if you want, I can take it.
Thanks for reading.
Local-only agent memory when mem0 and supermemory require servers.
Graph memory with auto-extraction beats simple vector stores for context.
Three-method API for agent memory, but semantic memory systems aren't novel anymore.
MCP-native persistent memory solves cross-platform agent amnesia without context hacks.
Cross-session memory for OpenCode agents, but only works in their ecosystem.
Git-for-agent-state rollback with tamper-proof audit logs; solves real agentic memory failure modes.