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

MGS3041: a job checkpoint this checkout cannot place

magus job fork, magus job apply and magus\job.put refused a job record whose checkpoint this checkout cannot start from:

[MGS3041] checkpoint "abc123" is not HEAD or an ancestor of it in this checkout:
  fork the job where that revision is checked out, or name `magus vcs checkpoint -o name`

Nothing was written to the job store.

What fires it

  • A checkpoint revision this checkout's history does not hold below HEAD.
  • A checkpoint digest that does not match the working state it names.

What to do

Fork the job in a checkout at that checkpoint, or replace the checkpoint with the one this checkout prints:

magus vcs checkpoint -o name

See also

MGS3041jobsleasesforkapplyagentscheckpointvalidation
Last updated (29d8b3de)
Glossary

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

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