From working code to a merged pull request
Hoplite agents run your tests, check the change in the running app and open the pull request. You review the diff, the preview and the checks, then merge from the thread that did the work.
What does it mean for a coding agent to verify its work?
A coding agent that verifies its work doesn't stop at a diff. It runs the project's tests and type checks, starts the app and looks at the change in a browser, then hands you the evidence alongside the code.
In Hoplite, all of that happens in the thread's own sandbox. Commands and their output stay in the activity timeline, the preview opens inside the thread, and the pull request view puts checks, reviews and the merge button next to the conversation that produced the change.
Tests run where the code was written
The agent runs your tests, type checks and linters in its sandbox, and every command lands in the activity timeline with its input and output. Add a check command to .hoplite/settings.json and the agent knows how your project verifies a change.
Checked in the running app
The agent starts your dev server, drives a browser against it and checks the page for console errors and uncaught exceptions. For UI changes it attaches a review checklist to the Preview panel, with the paths to visit and what to look for. Only you can mark a step reviewed.
Review the diff without leaving the thread
The Diff tab compares the workspace with its base branch in one continuous scroll, with a file tree, viewed marks, and the [ and ] keys to step between files. Comment on a line or a range, then send every comment to the agent at once.
Open the pull request, then merge it
Type /pr for a draft pull request from the thread's diff, or ask the agent to open one. The PR tab shows checks, reviews and changed files, and merges with the methods your repository allows, joining the merge queue when the branch requires one. If CI or a reviewer pushes back, PR Auto-fix takes it from there.
A bare diff vs. verified work
| Question | Agent that hands over a diff | Hoplite verify and merge |
|---|---|---|
| Tests | Run after you check out the branch | Run in the agent's sandbox, output in the thread |
| Seeing the change | Start the app on your machine | Open the preview from the thread |
| What to check | Worked out from the diff | A review checklist on the preview |
| Review comments | Copied back into a prompt | Line comments sent to the agent together |
| Opening the PR | Branch, push and fill in the form | /pr, or one sentence to the agent |
| Merging | Switch over to GitHub | From the PR tab, within your repository's merge rules |
Verify and merge, answered
- How does the agent know which tests to run?
- Add a check command, such as your test suite or typecheck, to .hoplite/settings.json, or name the command in your request. Editing files never runs repository commands by itself; verification runs as explicit commands you can inspect in the activity timeline.
- Can the agent approve its own work?
- No. The agent can attach review steps to the Preview panel, but only you can mark them reviewed, and later changes can reset a step to unreviewed.
- How do I open a pull request from a thread?
- Type /pr to create a draft pull request from the thread's current diff, or ask the agent. It can open draft or ready pull requests, promote a draft, request reviewers and reply to review comments. The pull request links back to the thread with an Open in Hoplite button.
- Which merge methods can I use?
- The ones your repository allows. The merge picker shows only allowed methods and starts on the one you last used. When the branch requires a merge queue, the pull request joins the queue and shows Queued to merge.
- Will Hoplite merge without me?
- Not unless you ask the agent to or turn on merge when green for the thread or as a workspace default. Automatic merging waits for required checks and review-loop work to settle, and an explicit opt-out keeps the pull request open for a person to merge.
- Who can open previews and screenshots?
- Preview links require Hoplite sign-in and membership in the workspace. Screenshots and videos shown in a thread stay restricted to workspace members unless workspace policy allows a public link, which expires after seven days.
- What happens when CI fails or a reviewer comments?
- Linked pull requests sync their checks and reviews into the thread. With PR Auto-fix on, the agent picks up the feedback in the same thread and pushes fixes to the same branch.
Merge work you've already seen running
Connect a GitHub repository, start a thread and review the result where it was built. Start on Free.