Skip to content
Shipper

shipper auto-ship

shipper auto-ship

Section titled “shipper auto-ship”

shipper auto-ship includes enable, disable, auto-merge on|off, drain, clear-halt, retry-observation, resume, and clear-dispatch. The state controls write durable local runtime state without loading settings, accepting another repository target, controlling worker count, or starting a supervisor. drain additionally performs one read-only daemon inspection to report represented runtime evidence; the other state controls do not contact a daemon. Enable requests dispatch and registers the checkout. The three stop states are distinct: drain records a persistent operator halt that preserves enablement and worker settings and ends only through clear-halt; disable turns enablement off and drains automatic work until Auto-ship is enabled again; and the automatic safety stop has its own durable latch cleared only by resume. Enabled means requested rather than dispatching whenever a halt or safety stop is in effect, and explicit manual work stays available throughout. Use shipper auto-ship clear-dispatch to preview held ownership, then repeat it with --force only after reviewing the holder facts and concurrent-schedulers warning; clearing ownership does not change Auto-ship desired state. Future-schema and valid foreign-identity control records are retained unchanged and refused; corrupt records remain recoverable and known older records migrate losslessly. During an automatic drain, review readiness at PR Open parks as a serializable neutral outcome that releases the issue lock and worker slot. Both sequential and parallel runners can advance other work, probe the current pull-request head, and redispatch a fresh run when ready. A changed head resets readiness deadlines; shutdown, drain, or safety-stop abandonment leaves the issue at PR Open without agent launch, failure, advancement, or safety accounting.