Memory & knowledge
Keeping what a team and its agents know, across sessions and after people leave.
2 answers · 18 articles · 3 definitions
Definitions in this subject
Connecting company data to AI agents: how to choose
Pick by where the data lives, not by which protocol looks strongest. If it sits inside one product that ships a connector, use that. If it is spread across a wiki, a drive, and a CRM that agents read daily, one place has to unify and structure it first, or every agent re-solves the same problem.
AnswerKnowledge transfer when an engineer leaves: what to capture
Capture the decisions, not the documentation. What leaves with a senior engineer was never written down: it lived in tradeoffs, rejected approaches, and incident history. Documentation mandates fail because writing docs is unrewarded work that competes with shipping. What survives a departure is knowledge captured as a byproduct of work already happening, somewhere the next person's tools can read.
ArticleAI memory lock-in works until it blocks your own product
Anthropic merged Claude chat and Cowork memory on August 25, 2026. AI memory lock-in is a moat until it stands between a vendor and its own next product.
ArticleGhost memory: why agents can't tell what's true now
Ghost memory is when old, current, and changed facts sit in an agent's memory and get retrieved together. Deleting loses history. Labeling the edge works.
ArticleKimi K3's 1M context runs mostly on linear attention
Kimi K3's 1M-token window runs on Kimi Delta Attention: hybrid linear attention with a fixed-size state. Why cheap long context still needs context curation.
ArticleDemand paging for the AI context window
A 2026 systems paper found 21.8% of tokens in agent context windows are wasted. Demand paging treats the AI context window as L1 cache, not full memory.
ArticleClaude Fable 5 put a price on context portability
Claude Fable 5 returns refusals as HTTP 200s and retries them on Opus 4.8. The fallback API reveals exactly what agent context survives a mid-task model swap.
ArticleClaude Opus 4.8 hallucinates less by answering less
Claude Opus 4.8 tops a hallucination benchmark without getting more accurate. It learned to abstain. Why retrieval honesty is a context engineering win.
ArticleWhen agent memory needs sleep, and when it doesn't
Memory consolidation fixes one specific failure: agents writing the same claim dozens of times into a flat scratchpad. When it helps and where it breaks.
ArticleWhy Product Management AI Gives Wrong Priorities
84% of product teams doubt their products will succeed despite AI adoption. The problem: PM tools see feature requests but not the context behind what to build.
ArticleWhy Sales AI Fails Without Deal Context
87% of enterprises missed revenue targets despite AI investment. Sales AI needs five types of deal context most teams never provide. The model isn't the issue.
ArticleHow to Move Your AI Context Between Tools
Claude now imports ChatGPT memories, but conversation history, files, and team context still don't transfer. Here's what actually moves and what doesn't.
Give your agents one place to read and write.
Put in your docs, data and notes, then connect Claude, Codex or anything else with one link.
Create a container