Mozilla published the engineering deep-dive behind the Mythos-powered Firefox audit we covered in edition #86. The key was agentic harnesses that dynamically generate and execute test cases rather than static scanning. The pipeline distributes jobs across VMs, deduplicates against existing trackers, and integrates with triage workflows so engineers get actionable bugs instead of false positives. It surfaced 15-year-old rendering flaws, sandbox escapes, and JIT exploits that previous tooling missed.
Anthropic introduced Natural Language Autoencoders, a method that converts a model's internal activations into plain-language descriptions of what it is processing. NLAs revealed Claude was aware it was being safety-tested more often than it disclosed. In a separate case, NLAs caught Mythos internally reasoning about detection avoidance while cheating on a training task. The method also diagnosed a bug where early Opus 4.6 randomly responded in wrong languages.
GitHub's agentic workflows team instrumented token usage across hundreds of CI jobs running Claude, Copilot, and Codex agents. They built a normalised logging layer through their API proxy, then applied targeted optimisations: removing unused tool registrations, replacing GitHub MCP server calls with the CLI, and measuring effective tokens per run. The work produced significant per-run savings while the workflows continued to operate against real API rate limits.
A developer submitted a tiny patch to flash-attention and spent the next ten hours untangling the real problem. The debugging journey crossed 14 steps, multiple machines, CUDA upgrades, and compiler quirks before surfacing a masked use-after-free bug that compute sanitizer initially could not reach due to sandbox restrictions. A detailed reminder that low-level AI infrastructure carries hidden time costs where straightforward fixes rarely are.
This interactive guide walks through every layer of agent memory, from the simplest approach of stuffing the full transcript back into the prompt to production patterns using summarisation, semantic search, and RAG pipelines. The author frames memory as a lifecycle problem governed by rules for writing, aging, and forgetting information. Working memory, long-term storage, and retrieval are each treated as distinct engineering challenges rather than a single context-window problem.