How to Verify if an Agent Actually Did the Work
Slightly_F0ol1Sh · reddit · 2026-07-16
After running agents in production for months, the author's biggest headache isn't whether the model can talk, but how to confirm it actually got the job done.
Core Issues
- Agents often claim they "saved/found it" and report completion, but no real side effects actually occur.
- These errors don't surface immediately; they accumulate downstream and are only discovered much later.
Current Practices
- Stop trusting the agent's own output.
- Use a "dumb" method for external verification: e.g., checking if a new row actually exists in the database, or if a file was truly written to disk.
- If there are no real results, fail the step immediately rather than passing silently.
Unsolved Challenges
- Long-term drift is harder to catch: an agent might work fine today but silently fail weeks later without triggering system alerts.
- The author wants to hear how others distinguish between "the agent actually did it" and "it just claimed it did."
Related event: AI agents in production: don’t trust narration, verify outcomes(8 posts)→
More from coding & agent
- GitHub review bot hits its PR limit and forces a 39-minute cooldown — DanielLockyer · 2026-07-22
- Max reasoning effort appears to be mobile-only in Codex Remote, not desktop — GabGarrett · 2026-07-22
- A Reddit demo argues online stores should expose carts and pricing through MCP — gelembjuk · 2026-07-22
- Open-source AI SDK provider routes Vercel apps through a local Codex subscription — lgrammel · 2026-07-22
- Codex vs Claude Code: Which Is More Popular? — jxnlco · 2026-07-22
- CodeRabbit uses layers, diagrams and a chat agent to rethink code review — _jaydeepkarale · 2026-07-22