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

workspace-command-failed

An advisory by default: it explains, and blocks nothing, on a command the workspace's rule could not judge, so only the built-in rules graded it.

What it catches

A command the workspace's rule could not judge, so only the built-in rules graded it.

Why

A workspace command rule that fails to load or errors judges nothing, and a command reaching a verdict without it must say so rather than read as fully judged. The first notice in a session names each failing side and its error; a repeat is one line naming what applied. It stands alone only when the built-in rules passed the command; on any other verdict the note is appended to that verdict. Standing alone, the one line is said once per caller: like every advisory not held by its own marker, the same text is not repeated to the same caller in a session. A workspace cannot set it: magus\guard.builtins refuses the name, since the notice is how the workspace learns its own rule judged nothing.

Default and override

This rule always takes the decision advise. A workspace cannot set it: naming it in magus\guard.builtins fails to load, because the rule is how a workspace learns that a rule of its own judged nothing.

Seeing it

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

advise [workspace-command-failed]: ...

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

See also

ReferencePages in this section. compat-marker: a leased worker adding a marker that keeps code for older data or callersAn advisory by default: it explains, and blocks nothing, on a leased worker adding a marker that keeps code for older data or callers. guard-unfinished: guard checks that never finished, so no rule judged their callsAn advisory by default: it explains, and blocks nothing, on guard checks that never finished, so no rule judged their calls. instruction-write: a write to a cross-host instruction file, which every session loads wholeAn advisory by default: it explains, and blocks nothing, on a write to a cross-host instruction file, which every session loads whole.
guardrulesworkspace-command-failedadvise
Last updated (29d8b3de)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. Workspace 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.

Advisor

One read-only check from the advice suite: it reads the changeset through magus and writes one titled section of findings. The same advisors run as a pull request comment in CI and inside magus diff --impact locally. Advisor in full.

Conventions

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