magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
1 min read

root-repeat

Off by default: once a workspace turns it on, it reports a main thread running the same delegable command again with no write since.

What it catches

A main thread running the same delegable command again with no write since.

Why

An identical search, read, diff, run or fetch with no file written since returns what the context already holds. At standard and strict the second run is advised once, and a file write starts the count over. It never refuses, and it skips a session that hands out work: there every repeat is groundwork, which orchestrator-groundwork judges. A calls parameter replaces the level's count.

Default and override

By default this rule takes the decision off. A workspace sets it by name, in its root magusfile, to advise or off:

magus\guard.builtins({"root-repeat": "advise"})

A loosening takes effect once it is committed; a tightening applies at once.

Seeing it

A verdict names its rule in brackets, which is how you got here:

advise [root-repeat]: ...

magus describe rule root-repeat prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

ReferencePages in this section. root-context-budget: a session's main thread whose context has grown past its level's sizeOff by default: once a workspace turns it on, it reports a session's main thread whose context has grown past its level's size. root-heavy-command: a main thread running delegable commands one after another without spawningOff by default: once a workspace turns it on, it reports a main thread running delegable commands one after another without spawning. spawn-names-model: a main thread spawning a subagent without naming the model it runs onOff by default: once a workspace turns it on, it reports a main thread spawning a subagent without naming the model it runs on.
guardrulesroot-repeatoff
Last updated (29d8b3de)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. Workspace in full.

Magusfile

The magusfile.buzz that declares a project's targets (as export funs) and binds its spells. Magusfile in full.

Buzz

The language magusfiles are written in (the .buzz engine). Buzz in full.

CI

An ordinary target you compose yourself with ctx.needs; magus does not hardcode its stages. It is the anchor magus affected ci keys off, and ci strips the rw charm. CI in full.

Agent

A model working through an agent host such as Claude Code, Codex, Cursor or OpenCode. magus treats an agent as one more caller of its CLI, MCP tools and console, held to the same checks as a person. Agent in full.

Session

An agent host's conversation, by the id the host delivers to its hooks. magus never mints one: a record with no session is unattributed, and the OS user it carries says whose account ran it. Session in full.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate. Run in full.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.