← All IntelClip / AI AgentsContext sprawl and framework churn
From WTF Is the Context Layer? The Missing Infrastructure for Production Agents — Prukalpa Sankar · ≈10:11
Twelve months of moving across Relevance, Google ADK, Glean, Claude Code and Codex shows why context must live outside the agent framework — per-agent memory doesn't port.
What’s in it
- Twelve months of moving across Relevance, Google ADK, Glean, Claude Code and Codex shows why context must live outside the agent framework — per-agent memory doesn't port.
Clip transcript
fix this? Um and over time we started dealing with context sprawl. Uh we had the The hard part about this was agents all had their own memory systems to a certain extent. So, they were learning They were all learning separately and they were learning differently. Uh it became very, very difficult very quickly to say, "Okay, what does the single version of truth here look like?" Um and then over time we actually went through In the last 12 months we've gone through cycles of at the agent tech layer. About 12 months ago we were using one of these no-code type builders uh called Relevance. We went from there into Google ADK, then we tried Glean. Uh start of this year we moved to Claude Code. Now we are kind of like 50/50 Claude and Codex. Um and every single time as these changes happened, uh our context got trapped in each of these individual systems. Um
Comments
Sign in to comment.
Loading comments…