Observed Signal · Mar 28, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
MySQL Journal Fixes Claude's Session Amnesia
A developer describes a lightweight approach to give Anthropic's Claude persistent session context without relying on heavyweight vector stores. The solution stores structured 'journal' entries in a flat MySQL table and exposes them via three MCP (Model Context Protocol) tools (journal_get, journal_post, journal_get_all). Claude reads the journal at session start via mcp-remote, restoring user instructions and recent context each session. The post includes the dev_journal table schema, a deterministic RK key generator using MD5, MCP server setup notes (MapMcp needs a leading slash; options.Stateless = true), nginx proxy settings, deployment options (ngrok, VPS, Raspberry Pi), and links to source code on GitHub. The author recommends this simpler pattern for remembering coding standards and project context instead of vector DBs or semantic search pipelines.
Provides a practical, low-complexity pattern to persist conversational context for LLMs without vector stores; relevant to teams integrating chat-based LLMs into applications and owning their data/infra but not a major platform policy or broad industry shift.
Track Anthropic Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Author implemented a persistent session-context solution for Claude using a flat MySQL table named dev_journal and three MCP tools.
- The dev_journal table schema (fields and types) and a deterministic RK key formula using MD5 are provided in the article.
- MCP server must use MapMcp with a leading slash (app.MapMcp("/mcp")) and be configured with options.Stateless = true to avoid tool-call hangs.
- Three MCP tools exposed are journal_get, journal_post, and journal_get_all; journal_get_all returns all entries for a service and is used to load permanent instructions.
- Deployment notes include nginx proxy_buffering off, using mcp-remote to connect Claude Desktop to the MCP endpoint, and self-hosting options (ngrok, VPS, Raspberry Pi) on .NET 8.
Connected Companies & Entities
6 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Vector Memory for Claude Code
An engineer replaced large, static CLAUDE.md files with a server-side vector memory system for Claude Code. They built an open-source MCP server, claude-memory-mcp, that stores structured memories in Supabase + pgvector and uses OpenAI's text-embedding-3-small for semantic retrieval. The system exposes MCP tools (remember, recall, forget, project_status) over HTTP (port 3101), enforces structured memory types (eight categories), imposes a 2,000-token recall cap, and implements soft-deletes and TTLs. CLAUDE.md remains for stable rules while vector memory holds evolving decisions, bug fixes, and patterns; Claude is instructed to call the MCP tools during sessions. The author reports low estimated monthly embedding costs (~$0.50) for typical consulting volumes and provides a 15-minute setup path using Docker, Supabase, and an OpenAI key.
Persist Claude Code Session Memory with Local Markdown
The article describes a simple, file-based approach to persist context for Claude Code sessions by loading a small set of markdown files at session start. The recommended structure places global and project-specific instruction files under ~/.claude/, with a MEMORY.md index (kept under 200 lines) that references more detailed memory files (user profile, feedback, project overview, reference links). The author argues that capturing corrections and preferences as files (especially 'feedback' entries) prevents repeating the same setup conversations, requires no cloud or external dependencies, and includes an open-source repository with one-command setup instructions.
Anthropic ships memory into Claude Code
A developer describes building an MCP-based persistent memory layer for AI coding assistants called cachly and how Anthropic's announcement that Claude Code gained a memory feature prompted re-evaluation of that work. The author explains a reproducible test for measuring whether an assistant truly persists facts between sessions, shares benchmark results from a personal corpus, and summarizes community feedback that changed the project's metrics and reliability checks. The post notes cachly offers a free tier hosted in the EU and links to the project's site.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.