Don't Lock In Tools, Lock In Context
Roger_M_Taylor · x · 2026-07-19
A quote tweet debates whether switching from Claude Code to Codex should only take a few minutes. The author argues that for most people, the hard part to migrate isn't the harness itself, but the accumulated context.
Thus, a design principle is proposed: treat the harness as a disposable consumable while preserving all other assets. As long as agents continuously learn new knowledge, acquire new skills, and automate more workflows, the cost of switching frameworks will grow, making it crucial to decouple the core data layer.
The suggested implementation direction is "Unified Memory": centralize the agent's knowledge in one place, supporting documents, full-text search, semantic search, and knowledge graph traversal. The diagram also shows a layered "Context Layer": various harnesses at the top, MCP servers / apps in the middle, and unified memory, knowledge graphs, file systems, and embedding retrieval at the base.
More from coding & agent
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11