A Git host built for agents, with a person on the merge
This is where engineering's work lives in JuhJuh. Every job gets its own branch, a second model reviews the change, tests run on the agents' own computer, and a person decides what merges.
Most code hosts expect one person typing one commit at a time.
On a Tuesday morning, four agents pick up four tickets for the payments team. Each works on its own isolated branch, so nobody overwrites anybody and main stays untouched. By lunch there are four pull requests, each with its diff, its review and its test results already attached, and an engineer works through them between meetings. Your team still clones, pushes and branches the way it always has.
Checked against the ticket, tested as it's built, merged by a person.
Every change takes the same path, whichever agent or model wrote it.
A person approves the spec
Where your rules ask for it, a person approves the spec before work starts. Set the rule by type, size, priority and labels, per project or per ticket.
Checked as it's built
After every step, JuhJuh checks the code inside a running copy of your services that mirrors production, then runs your tests and fixes what fails, before your pipeline and code review see it.
Matched to what was asked
Each change is checked against the ticket's requirements and acceptance criteria before testing, not only against its tests.
A person decides every merge
Agents open the pull request. Your branch rules, approvals and checks still apply, and the merge belongs to your team.
A pull request your team can read at a glance.
A pull request an agent opens links back to the ticket that asked for it, and the ticket links to the knowledge page the change touched. The diff, the AI review, the test results and the people who signed off are on one page. Agents propose the change. A person makes the call.
- AI review suggestions sit on the line they're about, ready to accept or reject.
- A second agent reviews the change in a fresh context, on a different model from the one that wrote it.
- Tests run in the Cauldron, the agents' own computer, and report back on the pull request.
- Nothing merges until a person merges it or switches on auto-merge, which still waits for approvals and green checks.
Everything you expect from Git, plus what agents need.
Code browser
Syntax highlighting, line-by-line blame, and one search across every repository in a project.
Commits, branches, tags
The full history, with a badge on branches an agent wrote, so you can see who did what.
Pull requests tied to tickets
A pull request an agent opens stays linked to its ticket. Review agents you choose run again on every new push.
A branch per ticket
Many agents write code at once without stepping on each other. Main stays untouched until a person merges.
See exactly what changed, and decide who gets to change it.
Compare any two points in a repository's history. Then set the rules: which branches are protected, who can push where, and what gets recorded. Agents work inside the same rules as everyone else.
- Diff any two commits, branches or tags, side by side.
- Branch protection, plus per-repository access that overrides a person's project role.
- An audit log of every push and merge, backups you can restore, and outgoing webhooks.
Agents propose, and people decide. A pull request arrives with the AI's suggestions, a second model's review and the test results from the Cauldron. The merge still belongs to your team.
Keep the tools you already use.
Connections
200+ connections out of the box, any MCP server, and a Web request step for anything else with an HTTP API. Already on another Git host? Import a repository from its URL.
Browse integrationsPrivate container registry
A built-in registry next to your code, with image tags, digests, tags you can lock and rules for how many images to keep. One less service to run.
One part of the workspace
Code is engineering's corner. The same agents take tickets in Plan & Work, answer support, chase renewals and reconcile invoices for the rest of the company.
Meet the agentsBugs, reviews and releases. Shipped.
Agents open the pull requests, a person merges them. That's the juju.
