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

MGS3042: a job fork past the workspace's limits

magus job fork and magus\job.put refused a job because forking it would pass a limit the jobs section of magus.yaml sets:

[MGS3042] wave/a/b/c would sit 3 level(s) below its root job wave, and
  jobs.max_depth in magus.yaml allows 2: fork it under a shallower parent

Nothing was written to the job store.

What fires it

  • A fork more levels below its root job than jobs.max_depth.
  • A fork that would leave more live jobs under its root job than jobs.max_live.

A zero limit is unlimited.

What to do

  • For depth, fork the job under a parent higher in the tree.
  • For live jobs, end one first (magus job exit <job>), then fork again. Repeating the fork unchanged succeeds once a job under the root ends.
  • If the limit is wrong for this workspace, change it in magus.yaml.

See also

  • Leases: forking and the job tree.
Sandbox diagnosticsLanding page for the sandbox that confines magus spells to the workspace, plus its MGS2xxx diagnostics for denied reads, writes, execs, and env leaks. MGS3037: a job record field fails its shapeFires when a job record carries a field magus cannot read as declared, such as an id that is not a lease id, a relative checkout or a path outside the workspace. The record is refused; fix each field the problem names. MGS3040: a job check its worker cannot runFires when a job record's check names an unknown project or target, a command the guard denies, a check only a person may run, or a run that skips the tests of the packages the job writes. The record is refused; name a check the worker can run to a passing record. MGS3043: a job write path that claims too muchFires when a job write path spans more projects or files than the workspace's breadth thresholds allow, or opens with a leading `**`. The record is refused unless it narrows the path or waives the problem with a reason.
MGS3042jobsleasesforkagentslimitsvalidation
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.

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.

Job

The unit of delegated work, and one row of the job store: what an orchestrating agent handed out, with its goal, the checkpoint it was cut against, the paths it may write or must not touch, and the one check it runs. A job's holder is either a session, for work an orchestrator handed out, or the daemon, for its own maintenance. The store records; the agent guard is what reads those facts back when grading a write. Job in full.

Lease

The grant a holder takes on a job: the write and read paths that job declared, enforced in the checkout that took it with magus job exec. A job is the piece of work; a lease is permission over it. Lease in full.

Conventions

Placeholders

Angle brackets mark a value you replace with your own; never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.