Pagerox for engineering
Pull requests stall for dull reasons: nobody reproduced the bug, the reviewer forgot, the red check is a flaky test. This guide sets up one agent that does that legwork on its own computer. It reads, runs and reports. Merging stays with people.
1. Connect GitHub
Create an agent for the job; Lumen Labs calls theirs Vera. Ask it about a repository and it shows a Connect card for GitHub. Sign in once and choose whether every agent may use the connection or only this one. Add Slack the same way if that is where the team talks.
2. Let it reproduce on its computer
The agent has a terminal, files and a browser on a computer in the cloud. It can clone the branch, install, run the tests and read the output, then tell you what it saw.
Open the step log under the answer to see each command and how long it took. You can also open the computer and watch the terminal while it works.
3. Start on a GitHub event
Work can start when something happens in a repository. Ask for it in a sentence. The agent adds a webhook to the repository, and because that changes something outside Pagerox, it asks you first.
- "When a pull request opens on lumenlabs/billing, read the diff and post a first review in this thread."
- "When an issue is opened on lumenlabs/app, try to reproduce it and tell me what you found."
What the event carries is data for the run, never an instruction to the agent. The work is listed in the panel under Work, with a toggle to pause it.
4. Never merges
Publishing and changes to production wait for you by default, and so does every command the computer's policy marks as risky. A push or a comment arrives as an approval card that says exactly what will happen and where.
To make the line explicit, add an Ask first rule under Settings, Auto-review: "Ask first before merging or closing a pull request". Ask first always wins over an Always allow rule, so nobody can wave it through by habit.
5. Nudge reviewers on a schedule
The rest is scheduled Work. It runs with nobody signed in, and it posts where the team reads.
- "Every weekday at 10, list pull requests that have waited more than a day for review and who they wait on."
- "Every Friday at 15:00, write what merged this week, in plain words, for the changelog."
A post to a Slack channel is a send, so the first one asks. If you allow it always, the rule is for that channel only.
Next: Sharing agents with your team, so every engineer can ask Vera in their own thread.