Observed Signal · Aug 6, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Agent Memory in TypeScript: Short, Long, Episodic
The article describes a three-store architecture for agent memory in TypeScript: Working (short-term) memory as the model-visible message window, Long-term memory for durable facts written deliberately, and Episodic memory for run records used for audit and analytics. It provides TypeScript interfaces and code examples for window compaction (keeping recent turns verbatim, summarising older exchanges under a token budget), a deliberate 'remember' tool for writing long-term facts, and guidance to avoid orphaned tool results that produce malformed API requests. The author also shows tests to validate compaction behaviour and advocates selective retrieval (top-k) of long-term facts at run start and separate retention policies for episodic records.
Practical engineering guidance for building reliable stateful agents and preventing malformed requests; useful to developers of conversational agents but not industry-shifting for AdTech/MarTech.
Track Amazon 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
- Proposes three distinct memory stores with separate lifetimes: WorkingMemory, LongTermMemory, and EpisodicMemory, illustrated with TypeScript interfaces.
- Working memory uses a summary head plus verbatim recent turns and compacts when over a token budget, keeping the last N turns intact.
- Long-term memory should be written explicitly via a 'remember' tool, stored with provenance, retrieved top-k per run, and deletable by the user.
- Episodic memory records run metadata (runId, outcome, cost, tool calls, finalSummary) for auditing and analytics and is not sent to the model.
- Provides testing examples to catch compaction bugs such as orphaned tool_result entries that lead to malformed requests.
Connected Companies & Entities
2 Entities mapped“Book: AI That Plans (https://www.amazon.com/dp/B0HBXFXMDT)...”
“My project: Hermes IDE (https://hermes-ide.com/) | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Durable Persistent Memory Architecture for AI Agents
A technical write-up (published 2026-07-30) arguing that AI agents should store authoritative, durable state outside model prompts to achieve reliable, tenant-isolated continuity across sessions and restarts. The post presents a TypeScript data shape (MemoryScope, MemoryRecord) and a sample loadRelevantMemory function that separates exact authoritative state from retrieved supporting context. It also outlines architectural patterns (four-layer memory architecture, state machines for long-running workflows), cost tradeoffs between long context windows and persistent storage, and the need for stricter controls around memory writes than reads.
Practical Patterns for Reliable AI Agent Memory
The article explains why memory is the central engineering challenge for production AI agents and describes three cognitive-style memory types—episodic (what happened), semantic (what is known) and procedural (how to act). It presents four practical memory architectures: file-based state (markdown files like MEMORY.md, ACTIVE.md, LESSONS.md) for human-readable warm memory; vector databases and RAG (example: pgvector in Postgres with OpenAI embeddings) for semantic retrieval of similar past experiences; structured relational databases with text-to-SQL for exact lookups; and hybrid architectures that combine hot/warm/cold tiers. The author also highlights a “lessons” pattern—capturing failures as reusable rules—and recommends starting simple (files) and adding vector/relational stores as scale and precision needs grow.
Guide: 30 Agent Memory Techniques for LLMs
A dev.to article (Beyond Context) summarizes agent memory management for large language model (LLM) agents and points to a GitHub repository (Agent_Memory_Techniques by NirDiamant) containing 30 runnable Jupyter notebooks. The piece categorizes memory techniques into six areas — short-term, long-term, cognitive architectures, retrieval & routing, frameworks, and evaluation & production — and describes patterns such as conversation buffers, vector stores, knowledge-graph memory, episodic/semantic/procedural memory, memory consolidation/compaction, and retrieval/ranking patterns. It references production-ready frameworks and tools (Graphiti, Mem0, Letta/MemGPT, Zep), highlights practical trade-offs (token costs, latency, tuning), and notes the repository is Apache-2.0 licensed. Publication date: 2026-07-02.
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.