Sign in

Moru vs Tangled: Same identity. Different forge.

Tangled and Moru both sign you in with an AT Protocol account, and both keep issues and reviews in the repository. Tangled is a network of knots with one app at tangled.org. Moru is your team’s own forge, built for coding agents.

The clone test

A repository on Tangled
$ git clone https://tangled.org/acme.tngl.sh/app
Tangled passes the clone test too: since October 2026 its knots keep issues, pull requests and comments as signed objects in the repository, fetched by name. CI results stay in the spindle’s database.
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 Tangled?

Tangled and Moru both use AT Protocol accounts and both keep issues and reviews as signed objects in the git repository. Tangled is a network: repositories on knots, CI on spindles, and one app at tangled.org where people star, follow and fork across knots. Moru is a self-hosted forge 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, CI results are signed records in the repository, and repositories can be private. Tangled is the better fit if you want a hosted, social forge for open source.

What this page says about Tangled was checked against Tangled’s documentation and blog on .

What happens when…

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

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

01 An agent’s token leaks

Tangled
Pushing over HTTPS takes a service-auth token bound to git pushes, and a knot can mint tokens for one repository. Access is decided by the knot; Tangled’s docs describe no rules per 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

02 An agent writes something terrible

Tangled
Tangled has no features for agents yet; skills for agents are on its list of what’s next. An agent pushes and opens pull requests like anyone else.
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

03 You rebase, and the review has to survive

Tangled
A pull request is a series of immutable rounds: reviewers comment on a fixed round, with interdiffs between rounds. Change IDs come from jj’s commit header, and stacked pull requests work with jj or plain git.
Moru
Much the same: a change keeps its ID across revisions, every revision stays reachable, and the conversation carries over. 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

04 You want several agents to try the same task

Tangled
Tangled’s documentation describes nothing for this. Each attempt would be its own pull request, 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

05 Someone asks who made this, and who checked it

Tangled
Issues and pull requests are signed by the knot, which holds each repository’s key, and authors counter-sign with a record in their own account. CI results aren’t records: they stay in the spindle’s database.
Moru
Every revision carries a signed record of which agent made it, where it ran and what it was asked. CI results are signed records in the repository too, and both verify offline.
moru-node verify acme/app kpqzrvlm
r3  agent-run  did:key:z6Mk…q4  ✓
r3  ci-run     checks/test      ✓

06 You need a private repository

Tangled
Tangled doesn’t have private repositories yet. They’re next on its list.
Moru
Repositories are public or private, and the node serves a private one 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

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

Tangled
Spindles run .tangled/workflows in Nix-built containers or microVMs, on Tangled’s spindle or your own. Tangled’s docs describe no way to run a workflow on your machine, and no GitHub Actions support.
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

08 You want to move

Tangled
Your profile, stars and follows live in your AT Protocol account and move with it. Repositories can’t move between knots yet, and Tangled’s importer copies git only.
Moru
Import a repository into another node with its changes, requests and Bake-offs, and it still verifies there. Or back the whole node up and restore it somewhere else.
moru-node import-repo acme/app \
  https://old.example.com/git/acme/app.git

Fair is fair

Where Tangled wins

Tangled is a network of people as much as a forge. If that’s what you want, it’s the better choice.

A network, not one forge
Profiles, stars, follows and forks across knots, all on tangled.org. A Moru node is one team’s forge.
Hosting
Tangled hosts your repositories and runs CI on its own knot and spindle, and has said both are free. Moru is self-hosted.
CI in a sandbox
Spindles run workflows in containers or microVMs. Moru runs CI on its owner’s machine, without a sandbox.
Stacked pull requests
Built in, with jj or plain git. Moru doesn’t have them.
Code search
Full-text search across Tangled’s network. Moru doesn’t have it.
SSH
Knots serve git over SSH and HTTPS. Moru speaks git over HTTPS only.

Questions

Both use AT Protocol. What’s the difference?

Tangled is built on AT Protocol: knots, spindles and the app at tangled.org, with your profile, stars and follows in your own account. Moru uses AT Protocol for who you are: people sign in with their account, and everything else lives on a node and in its repositories. Moru is built around coding agents; Tangled is built around a network of people.

Can I sign in to Moru with my Tangled account?

Yes, if its DID is a did:plc, as Tangled’s accounts are: they’re AT Protocol accounts, and Moru lets people sign in with one. Each node’s admins decide whether new people may join.

Can I bring a Tangled repository to Moru?

Its code, yes: moru-node import-repo copies a repository from any git URL, with its branches and tags. Issues and pull requests don’t come across.

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.

Bring the account you already have

Run a node, sign in with your AT Protocol account, and give the same request to several agents.

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