#human-in-the-loop
Every post tagged "human-in-the-loop".
64 posts · showing 41–50
-
The Handoff That Breaks Every Autonomous SDLC Pipeline
Chain agents across the lifecycle and the first handoff fails hardest — because it's the only one whose input isn't a written artifact, and every downstream check verifies against its output rather than the intent.
-
Agents Are Better at Writing Code Than at Deciding What to Build
Both feel like thinking about the problem, and only one has complete inputs and a checkable answer. The reframe that makes a model genuinely useful near a decision it shouldn't be making.
-
The Ticket-to-PR Agent: Which Half of the Job It Does Well
The split wasn't by difficulty — some intricate tickets went fine and some trivial ones went badly. One question predicts it, and acting on it improves something other than your agent.
-
What "End-to-End Development Agent" Actually Means Right Now
The phrase covers demos that differ by orders of magnitude. Naming the eight stages shows which two are genuinely autonomous — and why chaining them is qualitatively harder than any one of them.
-
What Employers Pay For When Code Itself Is Cheap
Companies were never buying code exactly, but code was a big enough share that the distinction rarely mattered. Five things remain when it's cheap — and the proxies that used to demonstrate them stop working.
-
Output Went Up, Review Capacity Didn't
PR volume doubled and review capacity didn't, because review is human and got no faster. The number to watch isn't merge throughput — it's how fast approvals are arriving.
-
Half the Job Is a Real Answer: Designing for Partial Success
Thirty-one of forty invoices reconciled. Reporting success hides nine; reporting failure throws away thirty-one. The middle is where most runs land, and most designs can't express it.
-
The Inbox Agent That Filed Everything Correctly and Lost Two Questions
Every filing decision was defensible, and two unanswered questions still vanished into the archive. The bug wasn't the prompt — it was that the agent judged messages while acting on conversations.
-
Content Boundaries: What Your Agent Should Refuse, and How to Test It
Providers handle the general case. Scope, regulatory limits, commitments, and how your agent represents you are yours — and the test suite needs both halves, or you'll ship something that refuses everything.
-
Eval Cases Where the Right Answer Is "I Don't Know"
Suites measure whether the agent got it right, never whether it should have answered at all. Five case types where the correct response is a question — plus the paired cases that stop you from just making it timid.