惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
Blog — PlanetScale
Blog — PlanetScale
Vercel News
Vercel News
L
LangChain Blog
Google DeepMind News
Google DeepMind News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
Recent Announcements
Recent Announcements
D
DataBreaches.Net
云风的 BLOG
云风的 BLOG
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
A
About on SuperTechFans
博客园_首页
N
Netflix TechBlog - Medium
Y
Y Combinator Blog
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog
Apple Machine Learning Research
Apple Machine Learning Research
罗磊的独立博客
美团技术团队
V
V2EX

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Nonmem addition to agent, that personalised experience
Neonmem Dev Team · 2026-06-14 · via DEV Community

One place for everything your AI needs to know about your project


If you build anything big with an AI assistant, you've felt the gap. A real project isn't just code — it's folders of docs, months of decisions, meeting notes, the reasons behind the architecture, the timelines, the plans, and the things you tried that didn't work. To be genuinely useful on a project like that, an assistant has to understand the domain you're working in, not just autocomplete inside it.

That's the problem we've been working on with Neonmem.

Even when an agent has "memory," it's usually a flat pile of text it can search but can't put in order. It doesn't know which decision replaced an earlier one, what's a plan versus a settled fact, or where you stopped yesterday. As the project grows, so does the mess — more data, more decisions, more threads to keep straight.

We wanted one place that holds all of it, in order, so your agent works like a real code buddy: aware of the project, and aware of how you work. So we built Neonmem as a single-point memory — one local cartridge that carries your project's reasoning, structure, and direction, with an understanding layer that keeps it organized.

What's inside

  • A single memory cartridge. One local .neonmem file — not a vector database, but a connected graph of decisions, dead ends, rules, and the reasoning between them. Yours, on your machine.
  • An understanding layer. Neonmem doesn't just store facts, it organizes them — clustering the memory into subsystems and mapping how the project fits together, so your agent gets the shape of the whole thing, not just fragments.
  • Resume where you left off. It keeps the open thread and the exact point you stopped, so a fresh session picks up instead of starting cold.
  • The importer. Point it at your docs, your codebase, and your meeting notes, and it reads the lot — turning them into one connected memory: the decisions, the endpoints, the call graph, the plans. Run it again as things move and it updates the memory in place, merging what's new and skipping what it already knows. Your agent opens already knowing the project.
  • Plans. Most memory only looks backward. Neonmem also tracks where you're going — the goals and next steps — so the agent knows the direction, not just the history.
  • Local and private. Offline embeddings, no cloud calls, no third-party model reading your code. It runs as its own small, self-built brain.

Where we are

Neonmem is in public beta. It's genuinely useful today, but we're early, and a lot is on the way — team memory (sharing a project's cartridge across a whole team), more autonomous workflows where the agent acts more on its own, broader platform support (macOS and Linux), and steady improvements to everything above.

If you live in an AI assistant and you're tired of re-explaining your project every morning, give it a try and tell us where it falls short — that feedback is shaping what comes next.

https://neonmem.com/ · Windows x64 · free for personal use