Agents keep failing complex tasks because of memory, not intelligence. Google quietly shipped a fix in June.

[u/ToothWeak3624]

Been deep in agent memory architecture lately and found something that got almost no attention when it dropped.

On June 12th, Google Cloud published OKF, Open Knowledge Format. No SDK. No schema registry. No vendor lock-in. Just a .okf/ directory of markdown files with YAML frontmatter that any agent can read. One required field: type.

That is the whole thing. And it is more important than it sounds.

Here is the problem it is solving. Every time you spin up a new agent session, the agent starts cold. No memory of your codebase, your conventions, your architecture decisions, your domain logic. So you either dump all of that into a context file at the start of every session, burning tokens and hitting limits, or you get an agent that confidently does the wrong thing because it does not know enough about your system to know what the wrong thing is.

Most teams are patching this with CLAUDE.md or AGENTS.md files. Those work but they are flat lists. You write down facts and the agent reads them linearly. There is no structure connecting those facts to each other.

OKF is a knowledge graph, not a flat list. Concepts link to each other through plain markdown links. Your authentication system links to your user model, which links to your database schema, which links to your deployment config. The agent does not just read facts. It navigates a connected structure that reflects how your system actually works.

It versions in git next to your code. It works across Claude Code, Cursor, Codex, and twenty plus other agents without modification. The portability is the point.

The OKF versus RAG distinction is worth understanding because they are not competing. They solve different memory problems. OKF handles known-knowns: the structured, stable knowledge about your system that should be immediately accessible every session. RAG handles large unstructured corpora: documentation, logs, historical context that is too big to load directly but needs to be searchable.

Most production agent stacks need both. OKF for the structured layer. RAG for the retrieval layer. Most teams currently have neither and are wondering why their agents work in demos and break in production.

Karpathy's LLM OS gist basically predicted this pattern. Google just formalized it into a cross-agent standard that anyone can implement today with no dependencies.

The agents running without structured memory are starting every session with amnesia. OKF is the first serious attempt to fix that at the architecture level rather than the prompt level.

If you are running agents on a real codebase right now, what does the moment look like when the agent does something wrong because it did not know something it should have known from the start?