Moru 2026.11.6
November 11, 2026
Every runner has an owner, agents run directly on the runner’s machine without a sandbox, and runners run Codex, Gemini CLI or an agent of your own as well as Claude Code.
Any agent. Runners run Codex and Gemini CLI as well as Claude Code, using the logins already on the machine, and offer each one whenever it’s on the runner’s
PATH. Any other agent you can start from a command line goes in the runner’sagents.toml: its command, how it takes a model, and which jobs it takes. A profile’sharnessnames the agent, and new nodes come withcodexandgeminiprofiles. Their output reads in the job log as Claude Code’s does: messages, commands, edits and tool calls. Usage limits send Codex and Gemini jobs back to the queue as they do for Claude Code, and your own agent says so by exiting with 75. Only Claude Code can be pinned to a version, so a repository that requires pinned runs doesn’t merge the others’ changes. See Agents.Your own profiles. Settings → Agent profiles lets anyone make agent profiles of their own: an agent, a model, a description and runner labels. They’re named after you (
mira/codex-high), only you can pick them, and they run on your runners. Any agent can now be picked as a reviewer, not only Claude Code. See Agent profiles.Every runner has an owner. A runner runs only the jobs of the person it belongs to. The shared pool is gone: Settings → Runners offers only your own registration code, and
moru-node create-runner-tokenneeds--owner. A team that pays with an API key gives it to each person’s runner. Site admins still see everyone’s runners, and runners without an owner in a tab of their own. See Runners.No sandbox. The runner runs agents as its own OS user, in a working copy under its cache directory, with the machine’s tools, network and files. Repos build and test the way they do in your terminal, with no image to build, no
--read-pathand no egress allowlist. In return, an agent can reach everything the runner’s user can. Run the runner on a machine or account you’re happy for an agent to use, or in a VM or container you set up. See Where to run a runner.Credentials from the machine. Agents use the runner user’s Claude Code login, or
ANTHROPIC_API_KEYorCLAUDE_CODE_OAUTH_TOKENfrom the runner’s environment. Setting both no longer stops the runner from starting.Setup is one binary. Install,
moru-runner register,moru-runner run. No Docker, no sandbox check, no AppArmor profile on Ubuntu. Runners can now run on Fly.io, Railway, Render and Kubernetes.Pinning means the Claude Code version.
--require-pinnedasks only for a pinned Claude Code version. The Evidence panel says “no sandbox (macOS)” or “no sandbox (Linux)” for new runs; older runs keep showing the sandbox and image they ran with, and their attestations still verify.Bake-offs no longer have the “Shared runners don’t review their own work” option, since every runner reviews only its owner’s work.
separate_reviewersin the API is ignored.Requests read as one thread. The request page shows every attempt in order: a Bake-off, the revisions that followed it, and, at the end, Your call to approve and merge the latest revision or revise it again. The request’s comments sit in the thread where they were made. Each attempt folds to a summary you can unfold, and a Bake-off shows its candidates at the revision its reviewers ranked, with where each one was continued. Each attempt has its own address,
…/requests/<id>/attempts/<n>, and a new attempt starts at…/attempts/new; older links still work.Diffs with many files. Every diff can list its files, fold each one, and expand or collapse them all. With more than 8 files, or a file over 400 changed lines, they start folded. A Bake-off’s Diff between candidates adds a grid of which files each candidate changed, with line counts; click a cell to open that file.
Smaller pages. The node compresses the UI, the docs and API responses with Brotli or gzip for browsers that accept them. Git traffic, the live event stream and runner downloads are sent as before.
Fixed: when a request’s change merged after its Bake-off was replaced by a revision, the other candidates stayed open and kept asking for review. A request’s other open changes now close as Not picked once one of its changes merges, and the node tidies up requests that merged before this release on its own. A closed change can’t be approved until it’s reopened (status
open), and its page no longer offers Approve or Merge.Fixed: an agent revising a change couldn’t fetch the revision or push its work to the node.
Upgrading#
- Breaking: runners without an owner stop getting work.
moru-node list-runnersshows them withowner=none (can't lease), and Settings → Runners under “No owner”. Give each one an owner withmoru-node create-runner-token <name> --key <DID> --owner <user>and restart it with the new token, or revoke it. - Breaking:
moru-runnerno longer takes--sandbox,--read-path,--image,--sandbox-node-urlor--egress, and thesandbox-checkandsandbox-execcommands are gone. Scripts and service files that pass them fail: drop the flags and start the runner again. - Breaking:
moru-node pin-imageis gone, and profiles no longer have animagefield. - Breaking: agents run without a sandbox. Before you start an upgraded runner, check that its machine and user are ones you’re happy for an agent to use. See Where to run a runner.
- Breaking (API): runners in
GET /api/v0/runnersno longer havedocker,sandboxorcredential. A runner registration code no longer takesshared. - Runners no longer need Docker or the agent image. You can remove the
moru-agentimages andubuntu/squid. - Existing nodes keep their
profiles.jsonas it is. To offer Codex and Gemini CLI, add{ "name": "codex", "harness": "codex" }and{ "name": "gemini", "harness": "gemini" }to it. See Agent profiles. moru-runner run --harnessnames agents now, and its default is every agent the runner has rather thanclaudeandfake. A runner on a machine withcodexorgeminiinstalled starts offering them.