Docs
Changelog

Moru 2026.11.5

November 10, 2026

Documentation on every node, notifications and webhooks, suggested changes and reviews, and “merge” instead of “land”.

  • Documentation. Every node serves these docs at /docs, for its own version, with search, and this changelog at /changelog. Links in the docs to a repository’s pages open them in yours, and the command menu finds docs pages by title.

  • Notifications. The Inbox has an Activity tab for what happened to you: mentions, replies, new threads on your changes and requests, approvals, revisions, merges, agents finishing and assignments. The header’s Inbox shows a dot for unread activity, live. Each reason can be switched off in Settings → Account → Notifications. See Inbox and notifications.

  • Watching a repo. A Watch button in the repo header (off by default) notifies you of new changes, new requests and merges in that repo.

  • Webhooks. Repo Settings → Webhooks: hooks for changes, requests, comments, reviews, Bake-off recommendations and pushes, signed with HMAC-SHA256 and retried with backoff, with a log of recent deliveries and “Send again”. Private and internal addresses are refused unless the node runs with --webhooks-allow-private. See Webhooks.

  • Suggested changes and reviews. A line comment can carry replacement lines, and a writer applies one or several in a click, as a new revision of the change (and of the branch it tracks). Comments can be gathered into a review and submitted once, as a comment, an approval or a request for changes. Reviewer agents do the same over MCP (submit_review, and suggestion on add_comment), and agents revising a change see the suggestions. See Reviewing.

  • Runners install from the node. curl -fsSL https://moruforge.com/install-runner.sh | sh. The node image carries its release’s runner archives and serves them at /download/runner/, so a self-hosted node installs runners of its own version from its own URL. “Add a runner” shows the command for your node. The script checks each download against its checksum before it installs it. New option: --runner-downloads (MORU_RUNNER_DOWNLOADS, set in the image). See Add a runner.

  • New repos can start with a README. “Add a README” is on by default when you create a repository ("readme": true on POST /api/v0/repos): main starts with one commit by you and gets the first branch’s protection. Agent work can no longer be started in a repo without main; before, an agent did the whole task and failed only when it submitted.

  • Assigning a person. Assigning someone to a request (yourself included) records it and notifies them, and works on an empty repo. The assignee pushes a branch and proposes it for the request; the propose form preselects requests assigned to you and offers a pre-review agent. Every revision of a change linked to a request is now pre-reviewed, including later pushes to its branch and to refs/for/….

  • Requests for any branch. A request can say which branch it merges into, under Merge into in the form ("target" in the API). Agents start from that branch, and its changes merge into it. See Requests.

  • Deleting repositories. Repo Settings ends in a Danger zone for admins: changing visibility asks first, and “Delete this repository” asks for the repo’s name. A deleted repo is gone at once but kept for 7 days: its owner, an owner of its organization or a site admin can restore it, with its requests, changes, discussions, collaborators and webhooks, from “Recently deleted” (account settings or the organization page) or with moru-node restore-repo. Backups leave deleted repos out.

  • “Merge”, not “land”. Everywhere: the UI, the node’s messages, the CLI, the API, events, webhooks and the stored history.

  • Fewer stuck tabs. A browser tab now shares one live connection to the node, and a tab hidden for a few seconds closes it and catches up when shown. Before, three tabs on plain HTTP could use up the browser’s connections and leave links hanging.

  • A new landing page that walks one example request from writing it to merging the change, and link previews: with the landing page on, / has a title, description and image for Slack, X, LinkedIn and Discord, and the node serves /robots.txt and /sitemap.xml.

  • Rules come along when you import a repository. Its protected branches, “approval from someone other than the author” and “only writers can comment” are taken from its access record where they’re stricter, and the default branch is protected, as in a new repository. People still wait until an admin applies the record. Applying a record now only tightens these rules: it adds protected branches and never removes or relaxes one. See Organizations and access.

  • Smaller things: repo Settings is a tab like the others, Enter in the last “done when” criterion adds another, a branch’s tree says whether it’s proposed or merged, the request form shows the right command to start a runner when none is online, an expired sign-in no longer sends you to the login page from public pages, and backups leave out temporary clones.

Upgrading#

  • Breaking: “land” is now “merge” in the API, events, webhooks and stored history. Repos with changes or Bake-offs landed before this release no longer load. Clients calling POST …/changes/{id}/land must call …/merge.
  • Breaking (API): POST …/scratch with request is refused (400), and the request detail no longer has attempts[].scratch.
  • The index is rebuilt on first start. Nothing to do.
  • Installing a runner needs sha256sum or shasum on the machine.
Command menu
Search for a page, repository, change or request, or run a command