Codex uses computer use to debug a broken MCP server in VS Code end to end
dfinke · x · 2026-10-08
When the author's MCP server wouldn't connect in VS Code Insiders, he told Codex to 'use computer use and figure it out' — never touching the keyboard.
Codex launched VS Code on its own, wrote the mcp., pointed it at the right port, started the local server from the right directory, and ran a baseline to confirm everything connected. It then made a breaking change, reproduced the failure for real, hunted down where VS Code logs MCP activity (the author didn't know), and diagnosed the issue — automating a manual slog of write-config-tweak-repeat.
More from coding & agent
- Agent Guard adds guardrails to running Claude Code in YOLO mode — Arindam_1729 · 2026-10-09
- OpenClaw slashes 1.3M flaky tests, doubling CI speed in big cleanup push — heyneighbor · 2026-10-09
- How do you decide what to optimize first in production AI agents? — Successful-Ask736 · 2026-10-09
- Matt Pocock's "Skills for Real Engineers" repo hits 280k GitHub stars — adnan_hashmi · 2026-10-09
- Steve Yegge: Rex Alpha Makes 20+ Claude Code Sessions Feel Local From a Hotel Laptop — Steve_Yegge · 2026-10-09
- Agent harnesses are crutches; least-privilege action authorization is what matters — andreisavu · 2026-10-09