Sign in

Moru vs Radicle: Same idea. Different shape.

Radicle and Moru both keep issues, reviews and decisions as signed git objects in the repository. Radicle spreads them peer to peer, with a node on every device. Moru is one server your team runs, built around coding agents.

The clone test

A repository on a Radicle seed
$ git clone https://seed.example.org/z4Xq….git
A Radicle repository passes the clone test too: issues, patches and their reviews are signed git objects in each peer’s namespace. Seeds serve them over HTTPS read-only; you write through a Radicle node of your own.
A repository on Moru
$ git clone https://moruforge.com/git/acme/app.git
A clone of a Moru repository brings the code, and with one more fetch every request (Moru’s issues), discussion, label, milestone, Bake-off, revision, identity and access record, signed. They still verify after the repository moves.

The short answer

How is Moru different from Radicle?

Moru and Radicle both store collaboration data as signed git objects inside the repository, so it moves with the code. Radicle is peer to peer: everyone runs a node, there are no accounts, and seeds serve a read-only web view. Moru is a self-hosted forge a team runs, built for coding agents: agents work in throwaway scratch repositories with a token for one repository that expires in hours, several agents can try the same request in a Bake-off, and nothing merges until the repository’s review rules are met. Radicle is the better fit if you want no server at all.

What this page says about Radicle was checked against Radicle’s documentation and source on .

What happens when…

Where the shared idea ends, the day-to-day begins.

Nine things that come up on a team that works with agents. Pick who you are.

01 Someone asks where the forge is

Radicle
Radicle is peer to peer: every user runs a node on their device, and always-on seed nodes keep repositories available. Seeds serve a read-only web view; you write with the CLI, the terminal UI or Radicle Desktop.
Moru
A node is one server your team runs, with a web UI for requests, review, Bake-offs and CI. People need git and a browser; only the people running agents install anything else.
git clone https://moruforge.com/git/acme/app.git
open https://moruforge.com/r/acme/app

02 An agent’s credentials leak

Radicle
Radicle’s documentation describes no access tokens. Each person or bot is a key on its own node and pushes only to its own namespace, and the delegates’ signatures decide the canonical branch.
Moru
The agent’s token names the agent, the person it works for, one repository, the scratch repository and refs it may push, and what it may do. It expires after 4 hours by default and is checked on every push and API call.
agent      did:key:z6Mk…q4
for        did:plc:alice…
repo       acme/app
push to    scratch/01JC8…
expires    in 3h 52m

03 An agent writes something terrible

Radicle
Radicle has no features for agents. An agent would be another key on its own node, opening patches from its own namespace until a delegate merges one.
Moru
The agent never writes to your repository. It works in a throwaway scratch repository, only the change it submits crosses over, and nothing merges until a person approves it.
scratch/01JC8….git   push ✓
  └─ submit kpqzrvlm  → acme/app
                        waiting for your review

04 Someone merges without a review

Radicle
A delegate merges with plain git and pushes, and Radicle marks the patch merged. Reviews accept or reject a revision; Radicle’s documentation describes no rule that requires one before a merge.
Moru
Merging goes through the node, which checks the repository’s rules first: protected branches, approval from someone other than the author, required CI jobs and trusted attestations.
merge kpqzrvlm → main
  approved by  did:plc:bob…   ✓
  checks/test  ci-run         ✓

05 You rebase, and the review has to survive

Radicle
A force push makes a new, immutable revision, and every earlier one stays. Reviews and comments belong to the revision they were made on.
Moru
A change keeps its ID across revisions and every revision stays reachable, as on Radicle. The conversation carries over to the new revision, and if you use jj, Moru keeps the change IDs jj gave your commits.
change kpqzrvlm
  r1  3f9a1c  14 comments
  r2  b27e04  rebased onto main
  r3  5d4f19  review carried over

06 You want several agents to try the same task

Radicle
Radicle has nothing for this. Each attempt would be its own patch, compared by hand.
Moru
A Bake-off: up to eight agents, any mix, get the same request. Reviewer agents rank what comes back with their reasons, and you pick one, or overrule them.
1st  claude-opus    kpqzrvlm  +64 −9
2nd  codex          wmtyxopl  +112 −31
3rd  gemini         zrnvoxkm  +18 −2

07 Someone asks who made this, and who checked it

Radicle
Every change to an issue or patch is signed with its author’s node key, and each peer signs its refs. Radicle CI can record jobs as collaborative objects in the repository too.
Moru
Moru’s objects are signed too, and every revision also carries a signed record of which agent made it, where it ran and what it was asked. CI results are signed records, and the merge policy checks them.
moru-node verify acme/app kpqzrvlm
r3  agent-run  did:key:z6Mk…q4  ✓
r3  ci-run     checks/test      ✓

08 You need a private repository

Radicle
A private repository is an allow list in its identity document, and the data isn’t encrypted at rest. Since a vulnerability disclosed in September 2026, Radicle advises against private repositories until a fix ships.
Moru
The node decides who may read a private repository and serves it only to people and tokens with access. An agent’s token reads the one repository it names.
acme/app        private
  read   alice, bob, agents for alice
  write  alice

09 CI breaks and you want to debug it on your machine

Radicle
Radicle CI is a separate broker on a node of its own. It hands jobs to adapters: a shell script on the CI host, GitHub Actions, Woodpecker and others. rad ci runs it locally.
Moru
moru-runner ci run runs a workflow’s job in your working tree, without a node. Workflows in .github/workflows run as they are, and ci lock pins every action and image.
moru-runner ci lock
moru-runner ci run checks/test

Fair is fair

Where Radicle wins

Radicle answers a different question: how to collaborate with nobody in the middle. If that’s yours, it’s the better tool.

No server to run, or to lose
Every peer holds a full copy, issues and patches included. A Moru node is a server someone has to run and back up.
No accounts
A key is an identity, and nobody signs up anywhere. On Moru, people sign in to a node.
Anyone can contribute without asking
Anyone can open a patch, or a new revision of someone else’s, from their own namespace. On Moru, a node’s admins decide who may join and comment.
BSD
Radicle runs on Linux, macOS and BSD. Moru’s nodes and runners run on Linux and macOS.

Questions

Isn’t Moru Radicle with a server?

They share the idea that collaboration data belongs in git, and Moru looked at Radicle’s collaborative-object crates before writing its own format. The shape differs: Radicle is a network of peers, and Moru is a forge a team runs, with scratch repositories, short-lived tokens, Bake-offs and CI built for coding agents.

Can Moru read Radicle’s issues and patches?

No. Both are chains of signed commits in git, but the layouts and signatures differ, and Moru doesn’t convert between them.

Can I bring a Radicle repository to Moru?

Its code, yes: seeds serve repositories over HTTPS, and moru-node import-repo copies a repository from any git URL. Issues and patches don’t come across.

What do people need to install to use Moru?

git and a browser. They push and clone over HTTPS and review in the node’s web UI. Whoever runs agents installs moru-runner on their machine.

Which coding agents work with Moru?

Claude Code, Codex, Gemini CLI, or any agent you can start from a command line. Each runner belongs to one person and runs their agents on their machine.

Try it with your agents

Run a node, import a repository from a Radicle seed, and give the same request to several agents.

Command menu
Search for a page, repository, change or request, or run a command