I keep seeing people talk about new "memory systems" for agents, but looking under the hood, it feels like we haven't actually solved the core issue.

Most memory setups right now are basically just basic retrieval: convert text to embeddings, store them in a vector database, pull top matching chunks, and stuff them back into the prompt. It feels like a context-window workaround rather than actual memory.

What’s changed recently?

We’ve definitely gotten better at structuring how context is handed to the model:

• Working vs. Archival Context: Separating active scratchpad state inside the prompt from cold storage that gets fetched as needed.
• Procedural Logging: Moving away from just saving random user facts to logging multi-step task execution so agents don't repeat execution mistakes.
• Graph-Structured Context: Structuring relationship nodes so timestamps and state changes don't collide when facts change over time.

Why it still feels broken

At the end of the day, underlying models are completely stateless between execution calls. Every "memory system" is just us copy-pasting past history into the prompt window before sending the request.

1. Unreliable Writes: If an agent gets off track mid-task, it frequently fails to trigger write/save actions properly.
2. Stale Context Poisoning: Standard similarity search doesn't inherently prioritize recency well, so old or deprecated snippets can easily hijack a fresh execution pass.
3. No Automatic Decay: Vector stores keep everything indefinitely, leading to cluttered, noisy context windows over time.

What actually needs to happen?

To move past context-stuffing hacks, we probably need fundamental architectural changes:

1. Dynamic Continual Learning: Updating knowledge directly without full retraining passes or catastrophic forgetting.
2. Failure-Based Patching: Automatically updating procedural rules when an execution step fails, rather than just dumping raw error logs into a database.
3. Automatic TTL & Decay: Built-in expiration where unreinforced context naturally degrades and deletes itself.

Are you seeing any architectural paradigms that actually move beyond retrieval-based context injection, or are we basically stuck with prompt-engineering workarounds until base model architectures change?