The investigation that used to pull an engineer off their work for an hour now happens in the background. We review the PR, not the logs.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at End-to-End Bug Debugging.
Cognition sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-04).
Verbatim match in End-to-End Bug Debugging. First-party Cognition text.
Cognition, “How Cognition Uses Devin to Build Devin”, Cognition, 2026-02-27, at End-to-End Bug Debugging. https://cognition.com/blog/how-cognition-uses-devin-to-build-devin Archived at https://the-ai-record.com/passages/cognition-investigation-used-pull-engineer-hour-background-2026
A powerful result is that anyone is able to contribute regardless of their technical expertise or role in the company, they don’t need to understand and set up Git or any command line tools to start contributing to our codebases.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at Core Experience.
As we ship more code with agents, the bottleneck shifted from writing code to reviewing it. Devin Review turns large, complex GitHub PRs into intuitively organized diffs and precise explanations. We use it for every PR now.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at Automated Code Review.
We set up a !triage-bug playbook that captures how our engineers actually investigate: read the report, search for relevant code paths, check git history, then summarize findings with root cause and suggested fix. The automation fires when anyone adds the Bug label to a ticket—no assignment needed.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at Bug Triage Automation.
We've found it especially useful for the kind of ad-hoc questions that used to sit in someone's queue for days. Questions like "why did signups drop Tuesday?" or "break down consumption by enterprise vs self-serve" can be answered by anyone on the team just asking in Slack, with the SQL included so we can validate the logic.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at DANA (Data Analyst Agent).
Last week, we merged 659 Devin PRs into our own codebase, up from 154 in our best week in 2025.
CognitionPublished by the organization itself (post), no named author
Post: How Cognition Uses Devin to Build Devin, Cognition, February 27, 2026, at Intro.
Something wrong? Report a correction. JSON: /api/v1/passages/cognition-investigation-used-pull-engineer-hour-background-2026.json