AgentWorkingMemory: A Local Memory System for AI Coding Agents

What AgentWorkingMemory Solves
AI coding agents like Claude Code lack persistent memory between sessions. Developers end up re-explaining architecture, database schemas, and previous decisions every time they start a new session, wasting time and context window space. While Claude Code offers some tools like --continue to resume conversations, auto-memory that saves notes to markdown files, and CLAUDE.md project documentation, these have limitations:
--continueor--resumerestores entire chat threads but consumes context window space and only works with one thread at a time- Auto-memory loads the first 200 lines of
MEMORY.mdbut lacks retrieval intelligence—it doesn't know which notes are relevant to current work - Project docs like
CLAUDE.mdwork for stable information but go stale quickly in fast-evolving projects
AgentWorkingMemory addresses these issues by accumulating knowledge across sessions, surfacing relevant context for current work, and improving over time without manual management.
How It Works
AWM runs entirely locally on your machine with no cloud dependencies. The system consists of:
- A SQLite database for storage
- Three local ML models (~124MB total, downloaded once and cached)
- A Node.js process
There's no server to run, no Docker container, and no background daemon. When you start Claude Code, it automatically spins up AWM through MCP (Model Context Protocol). When you close the session, it stops. Everything stays local—no cloud, no API keys, no data leaving your machine. For extra security, AWM supports bearer token authentication to lock down access to the memory API.
Setup and Usage
Installation requires two commands:
npm install -g agent-working-memory
awm setup --globalAfter restarting Claude Code, 14 memory tools appear automatically. The first session takes about 30 seconds while the ML models download (~124MB, cached after that). From that point on:
- The agent writes memories when it learns something important
- It recalls relevant memories when starting new work
- It checkpoints its state to recover after interruptions
The system was developed while rebuilding a 20-year-old codebase (~1.4 million lines) into a modern stack (~250K lines estimated), specifically for a membership management platform with 88 database tables and multi-sprint development using multiple AI agents in parallel.
📖 Read the full source: r/ClaudeAI
👀 See Also

sqlite-utils 4.0rc2: Written by Claude Fable, $149.25, Fixes Data Loss Bug
Simon Willison shipped sqlite-utils 4.0rc2, mostly written by Claude Fable for $149.25. Fable found a data loss bug in delete_where() and helped rewrite transaction handling.

Google PM Open-Sources Always On Memory Agent with SQLite Storage, No Vector DB
Google senior AI product manager Shubham Saboo has open-sourced an Always On Memory Agent that stores structured memories in SQLite instead of using vector databases, running on Gemini 3.1 Flash-Lite with scheduled memory consolidation every 30 minutes.

Gemma Gem: On-Device AI Agent for Browser Automation via WebGPU
Gemma Gem is a Chrome extension that runs Google's Gemma 4 model (2B or 4B) entirely on-device using WebGPU, with no API keys or cloud dependencies. It provides tools to read page content, take screenshots, click elements, type text, scroll, and run JavaScript through a chat interface.

ACO System: Open-Source Multi-Agent Pipeline from GitHub Issue to Merged PR
ACO System is an open-source multi-agent framework that autonomously runs a full software pipeline—from GitHub Issue to merged PR—using six specialized AI agents. Features a deterministic Architect gate that blocks hallucinations.