Devin Session Review Agent

A Devin session ending tells you the run stopped, which is a different fact from the job being finished, and the difference only shows up when a person opens the session and reads it properly. This agent does that reading the moment a session finishes: what was asked, what came out, the pull request link when there is one, and a verdict from a vocabulary your team agreed on beforehand. Where a session died waiting on a secret or an access grant, it can send one message back asking for precisely that, and nothing more.

What people use it for

• Know which sessions produced code - A verdict of SHIPPED needs a real link in the session data, so a run that ended tidily with nothing attached is reported as exactly that. Most teams have never seen the honest version of that number.
• Unstick a waiting session - Sessions die on a staging credential or a repository nobody granted. The agent names the single missing thing in the session thread, so whoever is reading Slack can clear it in under a minute.
• Catch the shortcut answer - Skipping the flaky test, dropping the assertion, quietly narrowing the job down to whatever went green: no session summary leads with any of it. This puts it on its own line with the session's own words attached.
• See the queue as a queue - Recent sessions get read alongside the one that just finished, so a third attempt at the same task arrives labelled as a third attempt rather than as fresh progress.

Before you fork

Devin already posts when a session ends. What does this add?

Devin tells you the run is over. This tells you what came out of it, measured against rules you wrote: a link or no link, the shortcut it took to get green, the third attempt at something two earlier sessions failed. It is the read one of your engineers is currently doing by hand, or has quietly stopped doing.

Can it talk back to Devin, and where does that stop?

Only on a NEEDS INPUT verdict, only where your rules permit replies, and only one message naming the thing that is missing. It cannot open a session, terminate one, archive one, or queue follow up work. If nobody answers that message, nothing further happens from this side, because chasing it is a person's job and the queue stays theirs.

Which credentials does it use, and what is the running cost?

A Devin credential that can read sessions and post a session message, plus one Slack channel. It fires once per finished session, so fifteen sessions a day is fifteen short runs, and a three hour session costs no more to review than a five minute one. Your definition of done and the shortcuts you refuse go in as a variable during setup.