{"slug": "tunnel-vision", "title": "Tunnel Vision", "summary": "A developer reports that Claude and Codex, while generally producing mergeable code, repeatedly exhibit three failure modes: \"prop drilling\" data through every layer of the stack, writing unit tests that only verify trivial operations like string concatenation, and over-disclosing in comments and user-facing text — including a support document that repeated \"not implemented yet\" next to every unfinished button and setting. The developer attributes the pattern to tunnel vision, where the task in hand is the only thing in context, and describes a partial fix: running a separate agent that never saw the original task on a schedule to maintain the support site as a whole from a bundle of recent changes. The developer disputes Cognition's argument that splitting work across contexts loses implicit decisions, contending that decisions living only in context mean the code and supporting materials aren't self-evident.", "body_md": "I opened a support document the other day for a feature that was still being built and found \"not implemented yet\" scattered through it. Not once, as a note at the top, but next to every button and setting the agent hadn't got to. It *was* accurate, but (obviously) it had missed the point.\n\nClaude and Codex are both moving up the developer curve, and for the most part they write code I'm happy to merge. But there are a few things they both do that I keep hitting:.\n\n(1) \"Prop drilling\". The agent needs a piece of data at location X, so it threads that data through every layer between here and there, clobbering interfaces on the way. The case that stuck with me was expanding our error logging to return specific codes rather than a generic error. The agent drilled every fact the codes needed down through the stack, when at the point the error left the system all of those facts were already sitting there.\n\n(2) Unit tests for 1+1. The frontend ended up with a pile of tsx tests checking that string concatenation works. They're cumbersome, they cost build minutes<sup>[\\[1\\]](#fn1)</sup>, and they were written by the same context that wrote the code, so their value as an independent check is arguable at best.\n\n(3) Over-disclosure. Ten-line comments on three-line functions, and over-sharing in anything user-facing. That's where \"not implemented yet\" came from. It was true, but a support document isn't the place to say it a dozen times.\n\nMost of this, I think, is tunnel vision. The task in hand is the only thing in the context, so it feels like the most important thing in the world. The ten-line comment is *obviously* necessary (it isn't), and the concatenation test feels like diligence, because nothing in that context is looking at the whole.\n\nModel or harness? Probably both.\n\nMy partial fix is to separate the steps and give them different contexts. Subagents would do it, but I prefer a separate agent altogether -- one that never saw the original task and has no stake in it. For support docs it's a separate runner on a schedule<sup>[\\[2\\]](#fn2)</sup>. It takes a small bundle of recent changes<sup>[\\[3\\]](#fn3)</sup>, looks at the feature as a whole, and only then touches the document. The context isn't \"do this thing\" it's \"maintain the support site as a whole with a batch of changes.\" This modifies the outcome in a meaningful way.\n\nCognition argued against this a while back: split the work across contexts and you lose the implicit decisions the writer made along the way<sup>[\\[4\\]](#fn4)</sup>. I disagree. If those decisions lie only in the context then I think you have a problem - the code and supporting materials aren't self-evident. Also it cuts the other way. The same context has all the twists and turns that are better left in the tunnel.", "url": "https://wpnews.pro/news/tunnel-vision", "canonical_source": "https://jonathannen.com/tunnel-vision/", "published_at": "2026-11-01 00:00:00+00:00", "updated_at": "2026-11-18 21:41:51.213429+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "large-language-models"], "entities": ["Claude", "Codex", "Cognition"], "also_reported_by": [], "takeaway": "Run a separate agent that never saw the original task, on a schedule, over a bundle of recent changes, so its context is \"maintain the support site as a whole\" rather than \"do this thing\" — the author reports this meaningfully changes the output.", "recommendation": {"advice": "Give documentation and review work to a separate agent with no stake in the original task, feeding it a batch of recent changes so it judges the whole rather than the tunnel.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/tunnel-vision", "markdown": "https://wpnews.pro/news/tunnel-vision.md", "text": "https://wpnews.pro/news/tunnel-vision.txt", "jsonld": "https://wpnews.pro/news/tunnel-vision.jsonld"}}