Your AI Agent Said Done: Why {status:success} Proves Nothing About the Goal
GlenBradley · x · 2026-09-21
Glen Bradley walks through a real network ops failure: a corporate WLAN mapped to VLAN 70 instead of 40. An AI agent proposes the fix, the controller returns {"status":"success"}, and the ticket closes — yet users still can't connect.
The core point: command success is evidence about the command, not the goal. After the change, auth might still fail, DHCP/DNS might be broken, guest isolation might be violated, or VLAN 70 may have been wrong but not the outage's cause. These are distinct facts that today's agents routinely collapse into one word: Done.
He argues the right sequence is proposal → accepted → verified state, and has written a longer piece on designing a control plane that keeps command state and goal state separate.
Related event: Agent Says Done, But the Problem Isn't Fixed(4 posts)→
More from coding & agent
- Agent Drops Live Map Pins Mid-Conversation, No API Keys Needed — PilgrimofHaqq2 · 2026-09-21
- claude-deep-research-skill: 8-phase Claude Code research pipeline with citation validation — tom_doerr · 2026-09-21
- Open-source browser agent fastbrowse is 71x cheaper per task than hosted Browser Use — Scobleizer · 2026-09-21
- OpenAI's $200 plan burns 33% in 48 hours; user calls it a bait and switch — AIandDesign · 2026-09-21
- Codex Reset Shifts the Cycle, Users Find It Eats Into Monthly Allowance — machyume · 2026-09-21
- Coder's Price List 2026 Edition: AI Coding Tools Compared — Evgenii42 · 2026-09-21