Ticket in. Draft merge request out. You approve twice.
Mergehand takes a task from your tracker through a plan you approve, implementation, independent review and testing to a draft merge request. Nothing is pushed until you approve the result.
7 days free · no card · your own AI account
Plan · written after reading the code
Fix rounding drift in checkout totals
AC1Cart total equals the sum of rounded line totals for any currency.AC2Discounts apply before tax, matching the invoice service.AC3A new property test covers 1,000 random carts.No code is written until you approve. Silence is never approval.
Approve planRequest changesHow it works
Eight steps. Two are yours.
Every task goes through the same fixed steps, so you always know where it is and what it is waiting for.
- 01TaskStart from an issue in GitHub Issues, YouTrack, Trello or Jira.
- 02PlanThe agent reads the code and writes acceptance criteria and open questions.
- 03 · youApprove the planNo code before your yes. Answer questions or ask for changes.
- 04ImplementIn a separate working copy, with the quality checks your repository already uses.
- 05ReviewBy a fresh agent that did not write the code. Findings go back for a fix.
- 06TestEvery acceptance criterion, one by one. Unchecked is never shown as green.
- 07 · youApprove the resultWith the report and the diff. Nothing is pushed before.
- 08Draft merge requestMergehand pushes the branch and opens it – a pull request on GitHub and Bitbucket. Merging stays with your team.
See it run
One ticket, start to finish, in under two minutes.
A screen recording of the Mergehand app on a demo project. No sound.
Walk through the same task step by step · Numbers from twelve weeks of real use
Step 6 · test report
Not checked means not green.
Every check is reported in one of four states, with the reason.
More than tasks
Code review
A review of a merge request as draft comments that only you see. You edit them and publish them yourself.
Epics
A large task is analyzed and split into parts that can be delivered one by one.
After the merge request
Address review comments, fix a failing CI pipeline or resolve conflicts – new commits on top, history is not rewritten.
Your code, your AI account
The agent runs on your machine, with your own AI sign-in.
You sign in to the AI agent on your runner with your own AI subscription or API key and pay your AI provider directly. Mergehand never receives your AI credentials and never bills tokens.
The server reads what it needs through your code host's API, keeps the tokens for your code host and tracker encrypted, and is the only part that pushes – after your approval.
Human approval
The plan and the finished code wait for an explicit approval. Silence is never taken as a yes.
Honest checks
Every check is reported as passed, failed, not applicable or not run – with the reason.
Your name on the commits
Commits carry the name and email of the developer who owns the run. Mergehand does not push a commit with a different author.
Isolated runs
Each run is a fresh container on your runner with an outbound network allowlist. It is removed when the run ends.