Segment 10: Vaishant Kameswaran & Rohan Kumar (Greptile): what five million vibe coded PRs reveal about agent bug profiles

• Timestamp: 03:11:13
• Duration: 9m 56s
• Livestream range: 03:11:13 → 03:21:09
• Transcript evidence: 19 chunks, about 1697 words

Actionable Insights

1. Turn what five million vibe coded PRs reveal about agent bug profiles into an operating checklist. Turn the speaker’s idea into a concrete workflow: define the user, the input, the tool boundary, the review step, and the failure condition.
2. Separate capability from accountability. The recurring lesson in this chapter is that more capable AI changes who does the work, but not who owns the outcome. When applying it to agentic coding and software delivery, write down what the system may do autonomously and what still requires explicit human judgment.
3. Instrument the loop before scaling it. The useful operating loop is: capture context, let the tool act, review the result, preserve the learning, and tighten the next run. Write down acceptance criteria and review notes early so the workflow can be audited later.
4. Design for the failure mode, not the demo. The polished demo version of what five million vibe coded PRs reveal about agent bug profiles is less important than the places it breaks: weak context, unsafe permissions, weak evaluation, unclear ownership, latency, or poor human review.
5. Convert this into a agentic software delivery checklist. The durable takeaway from Vaishant Kameswaran & Rohan Kumar (Greptile) is to turn “what five million vibe coded PRs reveal about agent bug profiles” into explicit operating rules: what the system may do, what it must prove, what evidence a reviewer needs, and where a human must stay accountable. The next useful artifact is a short checklist or eval case that someone can actually run.

What they actually use/show that is worth copying

• Claude for slides/drafts: Claude is used for first drafts, speeches, and slides. The key lesson is using a frontier model to speed up expression while the human still owns the judgment and accountability.
• GitHub PR workflow: The agent is embedded in the existing delivery workflow. That makes review, testing, and handoff happen where the team already works.
• Codex as software lifecycle agent: The harness is the product. Model capability becomes dependable only when planning, tools, execution, review, and rollback are explicit.
• ChatGPT / AGI builder stack: The valuable part is preserving editability and taste. The tool is useful when it keeps design intent alive instead of producing generic one-shot output.
• Sonar remediation/eval loop: The practical value is that behavior becomes measurable. Instead of vibe-checking the agent, the speaker is using traces, tests, logs, or evals to make failures visible and repeatable.
• Exa search primitive: The agent is embedded in the existing delivery workflow. That makes review, testing, and handoff happen where the team already works.
• Simular computer-use agents: The infrastructure choice affects product behavior. Latency, cost, routing, and model availability shape what kind of agent experience is actually possible.

Core thesis

Vaishant Kameswaran & Rohan Kumar (Greptile) uses this chapter to make a specific argument about what five million vibe coded PRs reveal about agent bug profiles. The useful pattern is not just the named product or institution; it is how the segment exposes the new operating model for agentic coding and software delivery: humans keep taste, accountability, and deployment judgment while agents or models absorb more of the execution loop.

The chapter starts from this evidence: “We’re reviewing four billion lines of code every month for companies like Nvidia, Coinbase, and Meta. And there are 100,000 bugs that are identified by Reptile and fixed every single day.” That opening matters because it frames the segment as a concrete slice of the broader AIE Singapore Day 1 theme: agentic systems are moving from novelty demos into production workflows, institutions, creative tools, infrastructure, and embodied systems. The analysis should therefore be read as a nested talk-level packet, not as a generic summary of the entire livestream.

Comment insights

The extracted YouTube comments do not provide reliable speaker-specific audience reactions for Vaishant Kameswaran & Rohan Kumar (Greptile). So this section should not pretend there is detailed sentiment about the talk. The useful audience-facing read is instead content-based: this segment is valuable for viewers who care about what five million vibe coded prs reveal about agent bug profiles, especially the concrete implementation choices and operating constraints called out in the transcript.

Deep research

The research value of this talk is the practical architecture behind what five million vibe coded PRs reveal about agent bug profiles. Vaishant Kameswaran & Rohan Kumar (Greptile) is not only making a broad claim; the useful details are the concrete mechanisms named in the transcript: Claude for slides/drafts, GitHub PR workflow, Codex as software lifecycle agent, ChatGPT / AGI builder stack, Sonar remediation/eval loop, Exa search primitive.

The main question to take away is how those mechanisms change the workflow. What becomes cheaper, what needs a stronger checkpoint, and what must remain human-owned? For this talk, the strongest evidence is in the speaker’s examples rather than in generic AI optimism. Use the named tools and operating choices as the starting point for further research, then validate whether the same pattern fits your own environment, security constraints, and evaluation loop.

Verdict

• The talk contains a specific operating lesson about what five million vibe coded PRs reveal about agent bug profiles: Agree. The speaker gives enough segment-level evidence to extract concrete implications rather than treating it as generic conference commentary.
• The named tools/examples should be copied blindly: Disagree. They are useful design references, but each needs to be checked against local security, data, latency, cost, and human-review requirements.
• The most valuable part is the concrete workflow detail: Agree. The strongest takeaways are the mechanisms, constraints, and examples the speaker actually names.
• The implementation details are transcript-supported: Agree. This page cites details such as Claude for slides/drafts, GitHub PR workflow, Codex as software lifecycle agent, ChatGPT / AGI builder stack.
• Human accountability disappears when agents improve: Disagree. The recurring production pattern is to move execution into tools while keeping ownership, review, and failure handling explicit.

Screen-level insights

• 3:12:03 — opening frame: Vaishant Kameswaran & Rohan Kumar (Greptile) frames the talk around what five million vibe coded prs reveal about agent bug profiles, with the useful setup being: “are able to make small multifile changes. And since 2025, we’ve entered a new age of fully agentic coding. AI agents are now able to create uh to go directly from spec to PR. But this leads us to wonder, are these fully vibecoded PRs actually any good?”
• 3:17:08 — Claude for slides/drafts: The talk shows or names this as part of the actual workflow. The relevant evidence is: “bugs. We once again broke this down by bot author and we found that a few bots were actually able to get their PRs merged on average more quickly than humans. Namely, Devon and Claude we found uh were the best on this metric.”
• 3:12:03 — GitHub PR workflow: The talk shows or names this as part of the actual workflow. The relevant evidence is: “are able to make small multifile changes. And since 2025, we’ve entered a new age of fully agentic coding. AI agents are now able to create uh to go directly from spec to PR. But this leads us to wonder, are these fully vibecoded PRs actually any good?”
• 3:13:03 — Codex as software lifecycle agent: The talk shows or names this as part of the actual workflow. The relevant evidence is: “database were able to be identified this way. And so obviously many more than 1% of PRs are vioded. We needed a stronger signal. And for that we move to looking at the PR descriptions themselves.”
• 3:15:37 — ChatGPT / AGI builder stack: The talk shows or names this as part of the actual workflow. The relevant evidence is: “Grappile also rates those comments on a scale of P 0 to P2 where P 0 is a critical codereing change and P2 is a nit.”
• 3:18:08 — closing implication: The later part of the talk turns the idea into a practical takeaway: “red over here means that the the bots make more of that type of bug compared to humans and blue means that they make less and the intensity of the color uh corresponds to the magnitude of that change.”

Verification notes

Verified against the extracted transcript for Vaishant Kameswaran & Rohan Kumar (Greptile)’s talk on what five million vibe coded PRs reveal about agent bug profiles. The supported claims in this page are based on concrete tools/artifacts named in the talk: Claude for slides/drafts, GitHub PR workflow, Codex as software lifecycle agent, ChatGPT / AGI builder stack, Sonar remediation/eval loop, Exa search primitive, Simular computer-use agents. I treated auto-caption wording cautiously, kept only details that are explicitly present in the segment transcript, and avoided importing claims from adjacent speakers or from the overall conference description.