Automated Devin Session Review Handoff
Every hour, WebRun opens Devin, checks which coding sessions finished since the last check, logs each one to Airtable with its task and status, and saves a review doc in Notion summarizing what changed and which files were touched, leaving the pull request open for a developer to review and merge themselves.
How do I make sure finished Devin coding sessions get reviewed before merge?
Every hour, WebRun checks Devin for coding sessions that finished, logs each one to Airtable with its task and status, and saves a Notion doc summarizing what changed, tagged Needs Review. Every pull request stays open and unmerged. Merging code is irreversible in production, so a developer always reviews and merges it themselves.
- No AI-written code merges without a human review
- Finished sessions get tracked instead of scattered across chats
- A developer gets a summary instead of a cold, unread diff
Built for engineering teams · startup CTOs · platform teams · software agencies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
devin.aiin a real browser with your saved login - no setup, no API keys. -
1
Devin - check finished coding sessions
devin.ai
WebRun opens Devin to check finished coding sessions. - Open Devin and check sessions completed since the last check
- Note the original task, the session status, and the linked pull request
- Leave every pull request open. Never merge it
Done when Every session completed since the last check is listed.
-
2
Airtable - log the session and its status
airtable.com
WebRun opens Airtable to log the session and its status. - Open the Devin session tracker in Airtable
- Add a row per finished session with its task and status
- Mark whether the session needs review or ran into a blocker
Done when Every new session is logged in Airtable.
-
3
Notion - save a review doc with the changes
notion.so
WebRun opens Notion to save a review doc with the changes. - Open the code review doc in Notion
- Summarize what changed and which files were touched for each session
- Tag the doc Needs Review and link back to the pull request
Done when Every finished session has a summary in Notion tagged Needs Review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it merge the pull request once a session finishes?
No. WebRun only logs the session and summarizes the changes for review. Merging a pull request is irreversible in production, so a developer always reviews and merges it themselves.
What happens if a session hits a blocker instead of finishing cleanly?
It still gets logged in Airtable and marked as blocked, so a stuck session does not just disappear from the record.
How do I know what actually changed without reading the full diff?
The Notion review doc summarizes the changed files and the task, giving a developer a starting point before they open the full pull request.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.