Moru 2026.11.2
November 8, 2026
A daily driver for people.
Code browser. Browse a repo’s files at any branch, tag or commit, with syntax highlighting, rendered READMEs, a file tree, “Go to file” (
t), links to lines and raw URLs (/r/{owner}/{name}/raw/{path}?rev=).Discussions on changes, requests and commits. Line comments follow the code across revisions. Reply, edit (with the edit history), hide and resolve. A repo setting decides who may comment (
everyoneorwriters). Discussions are stored in git and move with the repo.Agents in discussions. Reviewer agents leave line comments, implementers reply to threads, and “Revise with an agent” on a change sends an agent back to address the open threads.
Changes proposed by people. Push a branch and propose it, or push to
refs/for/<branch>. Later pushes add revisions. Protected branches, and an optional “someone else must approve” rule, under Settings → Merging. See Changes.Preferences. Per-account settings on the node, starting with the diff layout.
Runner setup moved into
moru-runner register. The git check, the AppArmor profile offer and the sandbox check run there, before the one-time code is spent.install-runner.shonly downloads and unpacks.Images rebuilt weekly with fresh base packages (
YYYY.M.N-rYYYYMMDD, andlatest). See Upgrading.Smaller things: the clone URL includes your handle, a hint about using a token as the git password, a new repo opens its page, and clearer sign-in when the node has a waitlist.
Upgrading#
- Breaking: new repos protect the branch their first push creates; push other branches and propose them, or push to
refs/for/<branch>. Existing repos are unchanged until an admin turns protection on. Unlinking a GitHub-linked repo protects its default branch unless you uncheck it (or pass--no-protect). - Breaking:
MORU_RUNNER_NO_APPARMORis gone frominstall-runner.sh. Usemoru-runner register --sandbox dockerto skip the AppArmor offer. - The index is rebuilt from the repos on first start.