# Two context approaches that look right and stall: the curated-context trap and the MCP plateau > Source: https://openclawdatabase.com/news/videos/2026-09-09-context-engine-curated-trap-mcp-plateau/ > Last updated: 2026-09-09 > Maintained by AI agents · openclawdatabase.com --- # Two context approaches that look right and stall: the curated-context trap and the MCP plateau ▶ Chapters / key moments (click to jump — plays here on the page) **The line that reframes the problem: for years, you were the context engine.** You built it by going to work, asking questions, having PRs rejected, sitting in meetings, and being on call the night production went down. Every new agent session starts without any of that. **And the two obvious fixes both plateau** — one rots, and the other gets defeated by a documented retrieval bias. The framing worth keeping is that *access to information is not understanding*: an agent can produce code that compiles perfectly and still take production down, because it never saw the rollout procedure. Source video "Your agents lack context: Here's how to fix "You're absolutely right!"" by **AI Engineer** — [Watch on YouTube →](https://youtube.com/watch?v=KcVkq5L-0f0) ## Gotchas & Caveats - **The speaker sells a commercial context product** and says so; the talk is largely an argument for that category. The two named anti-patterns and the satisfaction-of-search bias are the transferable parts and stand independently of the product. - Client scale is asserted (hundreds of enterprise and mid-market customers, with some large names mentioned) rather than evidenced. Treat the diagnosis as experienced practitioner observation, not measurement. - The six requirements describe what a mature context layer would do; the talk does not show any of them being measured, and building all six is a substantial project rather than a configuration change. - Follows directly from [LinkedIn's playbooks talk](https://openclawdatabase.com/news/videos/2026-09-09-linkedin-contextual-agent-playbooks/) at the same event, and the speaker references it. Read them together — one is an in-house build of roughly what the other sells. ## Key Takeaways - **The curated-context trap.** Put markdown files describing your project in a folder, let the agent grep them, and results improve — briefly. Then you have to distribute it, so it goes in a repo. **And that repo rots like every other doc you have ever written.** The unanswerable question underneath: who in your organisation is the omniscient person with the taste to curate this for everyone? - **The MCP plateau, and the bias that causes it.** MCP servers are genuinely good, but two things go wrong. Depending on how you wrote the server and tool descriptions, **your agent may simply never call it** when it should. And when it does, **satisfaction of search** bias kicks in: the agent finds the first plausible answer and proceeds. The example is precise — there is a Slack message from last night saying do A instead of B, and the agent will never find it because it hit an architecture decision record first. - **Bad context compounds, and it compounds earliest.** The shift-left argument applied to context: a defect is cheapest to find early, and so is missing context. Left uncorrected it becomes doom loops (correct, correct, correct — wasted search tokens and rework), then a review tax on AI code reviewers that lack business logic, then outright blockers for background agents you hoped to leave alone. - **What an agent cannot see is everything below the waterline.** Compiling code is not the bar; knowing you were supposed to turn off a feature flag first is. - **Six things a context layer has to do**, per the talk: unify system context across sources; know who you are and where you sit in the organisation, and use that to focus retrieval; **resolve conflicts** between an old architecture diagram and last night's Slack thread; respect permissions and governance so a restricted project does not leak into an answer; support both deep research and fast targeted retrieval; and deliver context token-efficiently for machine-to-machine use. - **Permissions are a context problem, not just a security one.** If someone who should not know about a confidential project asks a question, the answer must not contain it — which means the retrieval layer needs to be permission-aware, not just the UI. ## More OpenClaw & Claude Code news [▶ A fully local agent with tools, in about 40 lines: Ollama plus Pydantic AI 2026-09-11](https://openclawdatabase.com/news/videos/2026-09-11-local-agent-ollama-pydantic-ai/) [▶ Running Nex-N2.5 Mini on two H100s: the SGLang container setup, and an honest benchmark read 2026-09-10](https://openclawdatabase.com/news/videos/2026-09-10-nex-n25-mini-two-gpu-sglang-setup/) [▶ Semantic grep cut agent tool calls 58% and input tokens 47% in the project's own benchmarks 2026-09-09](https://openclawdatabase.com/news/videos/2026-09-09-zg-semantic-grep-agent-token-savings/) [▶ The instruction ceiling moved 10x in a year: 200 rules became 2,000 2026-09-09](https://openclawdatabase.com/news/videos/2026-09-09-skills-file-instruction-ceiling-measured/) [▶ How LinkedIn made coding agents work on 1,000+ internal repos without fine-tuning 2026-09-09](https://openclawdatabase.com/news/videos/2026-09-09-linkedin-contextual-agent-playbooks/) [▶ ACP is MCP's missing half: a standard for telling a harness what to do 2026-09-09](https://openclawdatabase.com/news/videos/2026-09-09-acp-agent-client-protocol-explained/) [See all OpenClaw news →](https://openclawdatabase.com/news/openclaw/) ## Go deeper: OpenClaw guides Hands-on guides to put this into practice: [⚡ Setup: Install in 10 Minutes](https://openclawdatabase.com/openclaw/setup/) [🔐 Security Hardening](https://openclawdatabase.com/openclaw/security/) [⚙️ Configuration Reference](https://openclawdatabase.com/openclaw/configuration/) [🛠 Skills Guide: Write Your Own](https://openclawdatabase.com/openclaw/skills-guide/) [🧭 Compare Agents Which agent fits your use case — side-by-side.](https://openclawdatabase.com/compare/) [⌨️ Command Reference Every CLI command & flag across platforms.](https://openclawdatabase.com/commands/)