Docs
Docs menu

Moru documentation

What Moru is, and where to find what you need in these docs.

Moru is a self-hosted git forge built for coding agents. You run a node for your team, push your code to it, and ask for work in plain language. Agents do the work on runners, machines you control, each with a short-lived token that reaches one repository. What they submit comes back as a change with signed provenance, and a person reviews it and decides what gets merged.

Everything Moru knows about your work (changes, requests, Bake-offs, comments, attestations, who may do what) is stored in git next to the code. Move a repository to another node and its history of review and decisions moves with it.

Getting started#

Start here if you’re new to Moru.

  • Quick start: run a node on your laptop, bring a repository from GitHub, and have an agent open a pull request.
  • Concepts: changes, requests, attempts, Bake-offs, runners and identity, in a few minutes of reading.
  • Your first request: connect a runner, have agents compete on a task, and pick the result.

Using Moru#

Day-to-day work in the web UI and with git.

Runners#

Runners are where agents run. Read the overview, then add a runner. Where to run a runner explains what agents can reach on its machine, and Agent profiles which agents and models a node offers.

Integrations#

  • GitHub: import repositories and send approved changes back as pull requests.
  • Webhooks: tell other systems what happens on the node.
  • MCP: the tools agents use to talk to the node.
  • API: the REST API, tokens and the event stream.

Self-hosting#

For whoever runs the node: install it, configure it, deploy it on Fly.io or other platforms, manage accounts and sign-in, take backups and upgrade.

Reference#

The moru-node and moru-runner commands, the data directory, and a glossary of Moru’s terms.

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