Moru 2026.11.8
November 17, 2026
Repositories get CI: workflows in .moru/workflows/, or GitHub’s in .github/workflows/ as they are, run on every new revision, push, schedule or manual start, on the runner of the person each run is for, and a repository can require jobs to pass before a change merges.
CI. A workflow is a YAML file in
.moru/workflows/, close to GitHub Actions’ syntax but without an expression language: jobs,needs, matrices, timeouts,when:conditions on the trigger,paths:filters, and steps that are shell commands. Four triggers: a change’s new revision (optionally only for some target branches), a push to a branch or tag (merges included), a schedule, and a manual start. A file with a mistake doesn’t run: its run is refused and lists each problem with its line and column. See CI and the CI file reference.Runs on your own runners. Each run is for one person: whoever started the agent, proposed the revision, pushed, merged or started the workflow. Its jobs run only on that person’s runners, as the runner’s user, with no sandbox, in a fresh checkout of the commit, and the job’s token can only fetch the repository. A new revision cancels the unfinished jobs of the change’s earlier runs, and a new push those of the branch’s previous run, unless the workflow sets
cancel-superseded: false. Runners take CI jobs by default;--kind cimakes a CI-only runner, and--kind implement --kind reviewkeeps CI off one. See Where to run a runner.Secrets stay on the runner. A job lists the secrets it needs, and the runner’s owner puts them in the runner’s
ci.toml, scoped to repositories, refs and triggers. The node sees their names, never their values. A runner that can’t give a job every secret it lists doesn’t take the job, and the run page says which secret is missing. By default secrets aren’t given to changes’ runs or to scheduled runs. Values are redacted from logs and outputs. See CI secrets.The CI tab and run pages. A repository’s CI tab lists its runs with filters, the workflows on the default branch and any that don’t parse, and Run workflow for workflows with a manual trigger. A run’s page shows the job graph and each job’s steps with their logs, with Cancel and Re-run for people with write access. The change page shows each revision’s CI results. On a public repository anyone who can read it sees CI logs and outputs; on a private one only people with write access do. Which runner ran a job is always for people with write access.
Required CI jobs. A repository admin can require jobs, such as
checks/test, to pass before a change merges, in the repository’s settings or withmoru-node repo-policy --required-ci. A job counts when every matrix combination passed on the latest revision, on a runner whose owner had write access when the runner took the job. A required job that doesn’t run for a revision by design, because itswhen:or its workflow’spaths:leave it out, counts as passed, as on GitHub; one skipped because a job it needs failed doesn’t. See Required jobs.Signed CI results. Each finished CI job for a change’s revision becomes an attestation in the change, signed by the node, with the runner’s own signed claim inside, so results travel with the repository and verify offline.
moru-node verifyand the API’sverifylist them. See Provenance.Local runs.
moru-runner ci run checks/testruns a workflow’s job in your working tree without a node, with the same step runner and environment a runner uses.--matrix,--eventand--refpick what to run as, and--secretsgives jobs the secrets fromci.toml. See moru-runner ci run.GitHub workflows run as they are. A repository with no file in
.moru/workflows/runs the workflows in.github/workflows/, translated into the same jobs:push,pull_request(every revision of a change),scheduleandworkflow_dispatchtriggers,${{ }}expressions with GitHub’s contexts and functions, jobif,needsresults and outputs, matrices withincludeandexclude,continue-on-error,fail-fast,max-parallel, theGITHUB_*variables and command files, and reusable workflows from the same repository.ubuntu-*andmacos-*run on your Linux and macOS runners; Windows combinations of a matrix are dropped, and the rest run. Each workflow gets a compatibility report on the CI tab: runs as is, runs with notes, or refused and why. What can’t run on Moru, such asenvironment:,pull_request_targetor actions that need GitHub’s API, is refused rather than run halfway. See Running GitHub workflows.Actions. Steps can use actions, in GitHub workflows and native ones.
actions/checkout, thesetup-*actions,jdx/mise-action,dtolnay/rust-toolchain,actions/cache, the artifact actions anddorny/paths-filterare built into the runner: setup actions check that the machine has the version asked for rather than installing it. Other JavaScript and composite actions are fetched from GitHub and run with the machine’snode, and Docker actions in a container. Actions never get a job’s secrets unless the workflow passes them.Containers. Jobs can start
services:such as a database next to them, run their steps in acontainer:image, and use Docker actions anddocker://images, in GitHub workflows and native ones. The runner usesdockerorpodmanon its machine, Linux or macOS (Docker Desktop, OrbStack, colima, podman machine), and takes such jobs only while its engine answers; until one of the person’s runners can, the job waits and says so. Services are reached atMORU_SERVICE_<ID>_HOSTand_PORT_<port>, with ports published on 127.0.0.1 only. A job container sees the job’s folder at the same paths as the machine. Images are pulled each job, with the copy already on the machine as a fallback, and run by the ID that was pulled; a run’s page lists each job’s images and digests, which a change’s signed CI results carry too. Containers get none of the runner’s own environment:optionscan’t copy a variable in (-e NAME,--env-host), and thedockerorpodmancommand itself only sees what the engine needs. Everything a job starts is labelled and removed when it ends, and a runner that was killed removes what’s left when it starts again. See Containers.Locked actions.
moru-runner ci lockwrites.moru/actions.lock, the commit and content of every action your workflows use, nested ones included, and the digest of everydocker://image, and the runner checks each action and image against it. Without a lock the node looks tags up when a run starts and marks the run Unlocked actions. A repository admin can require locked actions under Merging. See Locking actions.Schedules. A
scheduletrigger runs the default branch’s workflow from cron lines, in UTC or atimezoneyou give, at most every 5 minutes. Runs are for the person a repository admin picks under Scheduled runs use in the repository’s settings; a person’s repository defaults to its owner, and an organization’s runs none until someone is picked. If that person loses write access, schedules stop and the admins get a Stopped schedules notification. See Schedules.Caches. A job’s
cache:(oractions/cache) keeps directories on the runner between runs, with GitHub’s key and restore-key rules. A change’s runs restore only from their own change, their target branch and the default branch, and don’t save.[cache] max_sizein the runner’sci.tomlsets the room they take, 10 GiB by default. See Caches.Artifacts. A job’s
artifacts:(oractions/upload-artifact) uploads zips to the node, for later jobs of the run and for download from the run’s page by anyone who may see its logs. Kept 30 days, at most 500 MiB each and 1 GiB per run. See Artifacts.Manual inputs. A manual trigger’s inputs can be strings, booleans, choices or numbers. Run workflow asks for them, the API takes them, a native step reads them as
MORU_INPUT_<NAME>, and a re-run keeps them.Named runners. A job can ask for one runner by name,
runs-on: { runner: mira-deploy-box }. A runner started with--only-namedtakes only CI jobs that name it, from pushes and manual starts, never a change’s runs, and scheduled runs only with--schedules: the place for deploy secrets. See Deploy runners.Local runs of GitHub workflows.
moru-runner ci runreads.github/workflows/too, with actions, caches and artifacts, kept in your user cache directory. Services, job containers and Docker actions run with your owndockerorpodman, and Ctrl-C removes them.Reusable workflows. A job in
.moru/workflows/can call another workflow of the same repository,uses: ./.moru/workflows/checks.yml, with inputs inwith:. The called file declares acalltrigger, and its jobs join the caller’s run under the calling job, required asci/checks/lint. See Calling a workflow.Moving to Moru’s format.
moru-runner ci importwrites.moru/workflows/from your GitHub workflows, keeping file names and job IDs so required jobs keep their names. Calls to reusable workflows of the repository stay calls;--flattencopies the called jobs into each caller instead. What has no native form gets a# TODO:comment, and a step or job condition it can’t carry over is replaced by a step that fails until someone ports it, so nothing runs that GitHub would have skipped. On the CI tab of a repository that runs GitHub workflows, Move CI to Moru’s format opens a request for the move, filled in and ready for an agent. See Moving to Moru’s format.Jobs wait for a new enough runner. Runners send their version when they ask for work, and a CI job that uses a feature older runners don’t know waits for a runner that has it; the run page names the version it needs.
One workspace per repository. A CI job checks out in
<work-dir>/<owner>/<name>on its runner, the same folder for every job of the repository, as on GitHub, so a build from one job (a nextest archive) runs in the next. A runner runs one job of a repository at a time;--work-dirsets the folder, the same on every machine for builds that cross them. See Where a job runs.Revise rounds. A single agent can now revise its own change until it’s ready: when a revision’s CI fails or its pre-reviewer requests changes, it starts another round on the same change, up to the number of rounds you pick (3 by default with a pre-review). You get the change when it passes or the rounds run out. The attempt shows each revision’s results, comments on the change steer the next round, and Stop after this round ends the loop early. Nothing merges without you. See Revise rounds.
One job and exit.
moru-runner run --oncetakes at most one job, runs it and exits, for autoscalers, Kubernetes Jobs and spot machines.Notifications, webhooks and agents. A failed or refused run notifies the person it was for (CI failures in your notification settings). Webhooks can subscribe to
ci.run.queued,ci.run.startedandci.run.finished, or to a family of events such asci.*, which includes events later versions add. Agents read their revisions’ CI results, and reviewers their candidates’, with the MCP toolget_ci_results.Discord.
/discordon every node takes you to Moru’s Discord server.Moru vs GitHub. Nodes with the landing page on serve
/compare/github: the samegit cloneagainst GitHub and Moru, what happens on each when an agent’s token leaks or you want to leave, and where GitHub is the better fit. It has its own link preview, it’s listed insitemap.xmlandllms.txt, and its questions are marked up for search engines. The landing page now names every agent a runner can run, not only Claude Code.Moru vs GitLab, Forgejo, Radicle and Tangled. Four more comparison pages, built like
/compare/github, at/compare/gitlab,/compare/forgejo(Gitea included),/compare/radicleand/compare/tangled, and/comparelists them all. Each was checked against that forge’s own documentation on the date it shows, and says where that forge is the better fit. The landing page’s footer links to/compare.Readable without scripts. With the landing page on,
/is the page itself, not an empty page the browser fills in, so search engines and AI agents read what’s on it. The node also serves/llms.txt, a list of the docs pages, and/llms-full.txt, every docs page in one Markdown file, both linking to the node’s public URL.sitemap.xmlno longer lists/explore, which shows nothing without scripts.Real 404s. An address that’s no page of the web UI, such as a docs page that doesn’t exist, is answered with a 404 status. It showed the not-found page with a 200 before, so crawlers kept it as a page.
Trying Moru with a GitHub repository. A node at
localhostcan’t register a GitHub App, so Import from GitHub now leads there with Link a repository with a token, and Create a token on GitHub opens GitHub’s token form filled in with the permissions Moru needs. The quick start goes fromdocker runto a pull request an agent wrote, and the landing page has a Try it on your laptop quick start.Disconnect a GitHub App. Site admins can disconnect an app renamed or deleted on GitHub from the GitHub page. The node forgets it and its keys. Repositories linked through it stay linked but stop syncing, say so in their bar, and move onto another connected app with Use the GitHub App. See Disconnect an app.
A runner in one command. Add a runner shows one command that installs, registers and starts the runner (
install-runner.shtakes--code,--name,--nodeand--run), and says when the runner comes online. The three separate steps are still there under Step by step. Opening the page more than five times within 15 minutes no longer locks you out: each new code retires your oldest unused one. See Add a runner.Getting started. The repository list shows a checklist until you’ve brought a repository, added a runner, asked an agent for something and shipped the result. It ticks itself off from what the node knows, and × hides it.
Claude Code only where it can sign in. A runner offers Claude Code only when its user has a Claude login or key: Claude Code’s own sign-in,
ANTHROPIC_API_KEY,CLAUDE_CODE_OAUTH_TOKENand the like. Someone who uses only Codex or Gemini CLI no longer gets jobs for the default Claude profiles sent to a runner that fails on sign-in. The runner says when it found none;--harness claudeoffers it anyway. Add a runner lists how each agent signs in. See Agents.A first request that’s quick. A repository’s first request starts on Single agent and offers small tasks to start from: tests for an untested part of the code, checking the README’s setup steps, or resolving a TODO.
Docs beside the page. Docs links in the product open the page in a panel on the right instead of leaving the screen you’re on: next to it on wide screens, over it on narrow ones. The header’s Docs button opens the docs for the screen you’re on, and the command menu’s docs results open there too. A link held with Cmd or Ctrl, or Open full page, still goes to the full docs.
Running from your own registry. The install guide shows how to copy each release’s image, both architectures, into a registry you run, or load it on a host with no registry access, so your hosts never pull from
ghcr.io. Runners installed from your node then come from your copy too. See From your own registry.Sign-in and push hardening. The five-failure sign-in lockout now holds against sign-ins sent in parallel, and reads the client’s address correctly behind a proxy that adds its own
X-Forwarded-Forline. Pushes can’t reach a protected branch or a ref the node manages by spelling its name in another case, which mattered on case-insensitive filesystems such as macOS. A push to a repository is limited to 2 GiB by default (--push-quota-mib). Webhooks refuse more addresses that lead into the node’s own network (IPv6 forms that carry an internal IPv4 address), read only the start of a receiver’s response however long it is, and give up on a delivery that can’t be sent instead of trying it forever. A runner that stops a job no longer leaves behind a process the job was starting at that moment.
Upgrading#
- A push to a repository larger than 2 GiB is now refused, on existing repositories too. Raise
--push-quota-mib(MORU_PUSH_QUOTA_MIB), or set it to0for no limit. Imports aren’t limited. - Pushes to
refs/heads/,refs/tags/,refs/for/orrefs/moru/spelled in another case, such asrefs/Heads/main, are refused. A protected branch is protected in any case: withmainprotected,Maincan be created but not moved or deleted by a push. - On a host with many nodes, upgrade the control node before the repo nodes. Until the control node runs this release, CI doesn’t run on the repo nodes: pushes and changes there start no runs, and no runner gets their jobs.
- Upgrade runners to run CI. Older runners never take CI jobs, so a run’s jobs wait until one of the person’s runners is upgraded. GitHub workflows, actions, caches, artifacts, named runners and jobs with
container:,services:or Docker actions need runners on this release. - Upgraded runners with
dockerorpodmanon their machine take container jobs, and run their images as the runner’s user can. To keep a runner off them, start it with--container-cli none(orMORU_CONTAINER_CLI=none). moru-runner ci runkeeps its fetched actions, caches and artifacts in your user cache directory by default, not in./runner-cache. Pass--cache-dirto use another.- Runners can’t be named
linux,macos,x64orarm64, the labels every runner has. Existing runners keep their names. - Repository policies gain
require_locked_actionsandschedule_as, inrepo-policies.json,PUT /api/v0/repos/{owner}/{name}/policyandmoru-node repo-policy(--require-locked-actions,--schedule-as). Older files read as off and as the default. - Scheduled runs are opt-in on runners. A
ci.tomlsecret goes to scheduled runs only when itstriggerslistschedule; the default is now push and manual. If you set up secrets with an earlier build of this release and lefttriggersout, they stop going to scheduled runs: addschedulewhere a scheduled job needs one. A runner started with--only-namedtakes scheduled runs only with--schedules. - Repositories owned by a person run their workflows’ schedules as the owner as soon as you upgrade. An organization’s repository runs none until an admin picks someone.
- When a run uses an action that
.moru/actions.lockdoesn’t list, the node looks its tag or branch up on github.com (git ls-remote) as the run starts. A node that can’t reach GitHub refuses such runs, naming the action: commit a lock. - CI artifacts are stored under
ci/artifacts/in the data directory and aren’t in backups. The node refuses uploads that would leave less than 2 GiB free. - Notifications gain the reason
ci_schedule_stopped(Stopped schedules), for repository admins. It has no webhook event; the new webhook events areci.run.queued,ci.run.startedandci.run.finished. - Upgraded runners take CI jobs by default and run the commands in a repository’s workflow files as the runner’s user. If a runner shouldn’t, start it with
--kind implement --kind review. - Existing webhooks keep their list of events, so they don’t get CI events until you add them. A webhook created without a list gets every event, the CI ones included.
- Merging checks change records. A merge is refused when the change’s latest revision names a commit or base that isn’t an object ID. Change records fetched from GitHub could carry such values, and they reached
git rebase. - Breaking (API):
PUT /api/v0/repos/{owner}/{name}/policynow changes only the fields in the body, and refuses unknown ones. A field left out keeps its value instead of being reset.