Moru 2026.11.9
November 18, 2026
Changes now stay mergeable while they wait: Moru checks every open change against its target branch whenever that branch moves, shows the ones that no longer apply, and has an agent rebase them before you review them again. Requests become an issue tracker too: anyone who can read a repository can report a bug or ask for a feature, and a team triages, plans and orders its work in a backlog and on a board.
Conflicts show up when they happen. Each time a target branch moves, the node checks every open change on it, and a change whose latest revision no longer applies gets a Conflicts with
mainbadge on its page and in lists, with the files that conflict and the commit it was checked against. A change that’s behind the branch but still applies is fine and gets no badge. The Changes tab has a Conflicts filter. Merging still has the last word: a merge that hits a conflict the check missed marks the change Conflicted as before. See When a change no longer applies.Revise rounds count conflicts. In a loop, a revision passes only when CI passes, the pre-reviewer is satisfied and it still applies to its target. When it doesn’t, the next round tells the agent to rebase onto the branch first, keeping both its own change and what landed, and the agent can read what landed since its revision was made. See Revise rounds.
Passed changes are kept current. When a change that passed its loop starts to conflict while it waits for review, its attempt uses the rounds it has left: the agent rebases, CI and the pre-review run again, and the attempt ends again. Its timeline shows the rebase and Passed again. This happens for attempts that passed in the last seven days. Stop fixing conflicts on the attempt turns it off. See Keeping a passed change current.
Revise rounds don’t grade their own checks. The quickest way to turn red CI green is to edit the check, so a round that changes a CI workflow file (in
.moru/workflows/,.github/workflows/,.github/actions/or.moru/actions.lock) now ends the loop, even if CI then passes. The attempt reads Changed its CI workflows, names the files, and you’re notified. Rounds may still change tests, since sometimes the test is what’s wrong, but the attempt lists the test files each round changed ahead of its results. The agent is told to fix the code rather than the check, and the pre-reviewer to request changes for weakened tests. Only what a round changes counts: an agent’s first revision can add or fix CI and tests freely. See When a round edits the checks.Fix with an agent. A conflicting change made for a request has Fix with an agent, which starts a revise whose agent rebases first. Any revise you start on a conflicting change gets the same instructions.
Told once, when nothing is fixing it. If no agent is working on a conflict, because none was asked or the one that was gave up, the change’s owner gets one notification: “Your change conflicts with its target”. An attempt that rebased and still couldn’t make it pass says so in its own notification. The notification setting that used to be Couldn’t merge is now Conflicts and covers both.
A new revision clears Conflicted. A change marked Conflicted when a merge failed goes back to Open when a new revision arrives. It needs a fresh approval, since the rebase changed the code.
Runners don’t submit half-done rebases. If an agent exits in the middle of a rebase, merge, cherry-pick or revert, the runner submits nothing and the job says “left a rebase unfinished”, instead of committing conflict markers.
For scripts and agents. A change in the API carries
base, with its state, the commit it was checked against and the conflicting files, and the change list takes?base=conflicts. Webhooks can subscribe tochange.base, sent when an open change starts or stops conflicting. An agent’sget_taskreturnsrebase_onto,base_stateandlanded_since. See the API, webhooks and MCP docs.Requests from anyone who can read. Anyone signed in who can read a repository can file a request: on a public one, anyone with an account on the node. A request from someone without write access waits in triage, with a shorter form (a title, a kind and details) and Already asked? beside it, which lists requests with similar titles to vote on instead. People with write access accept it, accept and start work on it in one step, or decline it with a reason; a request declined as spam is hidden from everyone without write access. Those who can write to the repository and watch it hear when one comes in, and the person who filed it hears the answer. A repository admin can limit filing to people with write access under Settings → Requests. See Triage.
What agents read is marked. Text by someone without write access, a request’s details or a comment, goes into an agent’s instructions between markers, as a description of a problem rather than an instruction, and
get_taskmarks itoutside. Before, comments from anyone on a public repository reached revising agents as they were. Criteria are only ever set by people with write access. What an agent would be given, on a request’s page, shows the request’s part of an agent’s instructions.Planning. Requests get a kind, a priority, labels, a milestone and relations to other requests (part of, blocked by, duplicate of), in a Planning card on the request page. Labels and milestones are set up in the repository’s settings and, like everything else on a request, stored in the repository. See Plan requests.
Backlog and board. The request list gets Backlog and Board views, and filters by kind, priority, label and milestone, kept in the address. Drag requests into the order you’ll take them; filtered to a milestone, the backlog is its plan. On the board, dragging from Triage accepts a request and to Closed declines it, while In progress, In review and Done follow the work. See Backlog and board.
Votes, reactions and templates. Requests and comments take the eight GitHub reactions; a 👍 on a request is a vote, and the list sorts by Most wanted. Templates in
.moru/request-templates/give new requests a kind, labels and a starting text. See Request templates.Agents file what they find.
search_requestsandfile_requestlet an agent look for related requests and file what it notices outside its task instead of fixing it there. Its requests wait in triage, and the person it works for hears how they’re triaged. See MCP.Release notes on their own pages. Each release now has its own page, such as
/changelog/2026.11.9, with screenshots of what’s new.Link previews for the docs and the changelog. A link to a docs page or a release, shared in chat or on social media, now shows a preview card with the page’s title and summary. The links point at the node’s address, so set
MORU_PUBLIC_URLto the address people use.Link previews for public repos. A link to a public repo now shows a card with its name, the first paragraph of its README, and how many requests are open and changes merged. Links to a request or a change get their own card with its title, description and status. Private repos show no preview, so a link can’t reveal that one exists.
A shorter first run. A public GitHub repository can now be followed without a token: on Import from GitHub, leave Token empty and choose Follow without a token. Agents work on it right away, and Moru asks for a token with Add a token when there’s an approved change to send back as a pull request. A private repository still needs a token first. A node that has no admin yet now says so on its front page, with the command that prints the setup link, where it used to show an empty repository list. See the quick start and GitHub.
Tags on the Code tab. A repository with tags shows how many next to Go to file, and the count opens a list of them, newest first, with each annotated tag’s message and who made it, the commit it points at, and links to its files and history. The branch picker keeps branches and tags on separate tabs, so tags don’t get lost below a long list of branches. The API lists tags at
/repos/owner/name/tags. See Tags.Tabs say what’s waiting. A repository’s Requests and Changes tabs show how many wait on you in amber, next to how many are open. The CI tab shows how many runs are queued or running, and a red dot when the default branch’s CI fails.
A way to a runner from a waiting job. When your CI job waits because none of your runners is online, its run page links to Set up a runner if you have none, or to Your runners if you do.
A steadier change page. A change page no longer reloads its diff and comments each time a CI event arrives, so the diff stops flashing while CI runs.
Upgrading#
- The check needs git 2.40 or later on the node. The image ships 2.47. A node run without the container on an older git logs a warning once and skips the checks: no badges, and loops don’t count conflicts. See Without a container.
- The first check after the upgrade is quiet. Changes that already conflict get the badge, but no notification and no
change.basewebhook, so you don’t get one for every old conflict at once. Attempts that passed in the last seven days may still be reopened to rebase, a few at a time. - Upgrade runners. Older runners don’t fetch the commit a round should rebase onto ahead of time and don’t check for an unfinished rebase before submitting.
- On a host with several nodes, upgrade them together: a node still on an older version shows a loop that ended because a round changed a workflow as Stopped, without the files.
- Existing webhooks keep their list of events, so they don’t get
change.baseuntil you add it. Webhooks subscribed tochange.*get it now. - Anyone who can read a repository can now file requests in it. On a public repository that means anyone with an account on the node; their requests wait in triage, and each account may file 10 an hour on repositories it can’t write to (
--request-rate,MORU_REQUEST_RATE). To keep the old behaviour, set Settings → Requests to Writers only. - Triage, planning, labels, milestones, reactions and templates use a new format for the records they write in repositories, format 3. Nodes on an earlier release can’t read a repository once it has any. A repository that uses none of them stays readable by them. On a host with many nodes, upgrade every node first: until every node reads format 3, those writes are refused with a 503.
- The index is rebuilt when the node starts, as after any release that changes it.
- Agents started before the upgrade can’t use
file_request: their tokens don’t carry the newrequest:filepermission. Agents started after can. - Notifications gain the reason
triage(Triage). Webhooks gain the eventtracker.updated, and request payloads gaintriage,declined_reason,kind,priority,milestone,labelsandwhat. Existing webhooks keep their list of events.