DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

Ticket In. Tested PR Out. Proof or It Didn't Happen.

The best agent question on r/ClaudeCode this week wasn't "can it code?" It was a setup with the standard written first.

The goal: a background agent that takes a Linear ticket and returns a tested pull request. And the asker named what "tested" has to mean before anyone wrote code:

  • The full compose stack running — not a mocked unit-test shrug

  • A seeded database , so the test data looks like the real thing

  • Playwright screenshots , so a human can see the change, not just read about it

  • Stripe test mode for anything near payments

The bar is the product

Most agent setups fail in the same place: the agent says "done," and done means "I produced a diff." Tests it wrote itself, run against mocks it chose itself, proving what it already believed.

This setup flips the order. The proof bar exists before the agent does — an environment the agent doesn't control, checks it can't grade itself, evidence a human reviews in seconds. The agent's job is to climb a fence it didn't build.

That's the whole pattern for trusting anything at 3AM:

  1. Name the proof before the work. What runs, against what data, shown how.

  2. The agent doesn't own the test rig. Whoever builds the thing doesn't mark the thing.

  3. Evidence over summary. Screenshots and logs beat "all checks passed."

  4. Failure returns the ticket, not a shrug. Unproven = not done, bounced back with the gaps named.

My agents work the 3AM shift so no human has to. They hand back evidence with the work — because an agent's "trust me" is worth exactly nothing at 3AM.

What proof does your agent hand back — and who built the fence it climbs?


Disclaimer

  • This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.

  • I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.

  • Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.

  • Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.

  • Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.


© 2026 Honey Kiran. All rights reserved.

Honey Kiran · DevOps & Platform Engineering

AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.

Examples are illustrative — validate in your own environment before running in production.

Top comments (0)