Your coding agent doesn't always follow your rules — Talha Sheikh, Checkout.com

Talha Sheikh highlights the limitations of AI coding agents like Claude Code in fully automating tasks due to their tendency to miss details, and introduces Vector V1, a verification system that enforces correctness by automatically testing and prompting retries until outputs meet specifications. He emphasizes that building robust, language-agnostic verification layers is essential for trustworthy AI workflows, urging the industry to prioritize verification over mere code generation to achieve reliable automation.

In this talk, Talha Sheikh discusses the challenges of relying on AI coding agents like Claude Code to fully complete tasks without human intervention. While these agents can break down tasks into subtasks and produce outputs, they often miss small details or make errors that require manual correction. Talha realized that he was effectively acting as an enforcement layer, constantly needing to verify and instruct the agent to fix issues, which undermined the goal of fully automating work and freeing up his time.

To address this, Talha developed a product called Vector V1, which acts as a deterministic verification layer that automatically checks the output of Claude Code using hooks. This system runs predefined test cases to verify whether the agent’s output meets the required specifications. If the output fails any checks, Vector prompts Claude to retry until all tests pass. This approach shifts the focus from simply instructing the agent to enforcing correctness and trustworthiness in the results, highlighting the importance of verification in AI workflows.

Talha also reflects on the broader industry trend, noting that many companies including Anthropic, OpenAI, and Meta are independently building their own enforcement and verification systems. He emphasizes that verification needs to be a universal, language-agnostic pattern that can be applied at multiple stages—during conversations, before commits, in multi-agent workflows, and asynchronously. The goal is to establish a contract or standard that defines what successful task completion looks like, enabling consistent and reliable enforcement across different contexts.

The talk highlights a shift in AI development priorities: the value is no longer just in generating code or outputs but in designing robust verification and harness systems that ensure correctness. Talha points out that even as models become more capable, reliability does not automatically improve, so verification remains essential. He cites examples from industry where feedback loops, advisor patterns, and comprehensive code reviews are used to enforce quality, underscoring that verification is critical to trust and effective automation.

In conclusion, Talha urges developers and organizations to focus on building strong verification layers rather than solely improving code generation capabilities. The key takeaway is that working on the harness—the system that verifies and enforces correctness—yields better outcomes and more trustworthy AI agents. His Vector Harness product is publicly available for those interested, and he encourages the community to adopt verification-first approaches to fully realize the potential of AI coding agents.