shipper auto-ship clear-dispatch
shipper auto-ship clear-dispatch
Section titled “shipper auto-ship clear-dispatch”Usage: shipper auto-ship clear-dispatch [options]
Clear the current repository’s dispatch ownership
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —force | - | - | false | clear the exact dispatch ownership shown by the preview | - |
Examples
Section titled “Examples”Inspect held dispatch ownership without changing it.
shipper auto-ship clear-dispatchClear only the exact dispatch ownership shown by the command preview.
shipper auto-ship clear-dispatch --forceDispatch ownership recovery
Section titled “Dispatch ownership recovery”This command applies only to the current checkout’s canonical repository identity. It first makes a read-only preview and reports the repository, holder surface and PID, acquisition time, liveness, and Last refresh (diagnostic context only). Desktop, daemon, Terminal, and unrecognized holders use the same public facts. Running and could-not-determine holders both require deliberate confirmation.
While dispatch ownership is held, any other scheduler on this machine stands down rather than dispatching for this repository.
The preview result is confirmation-required. Without --force, held ownership is left unchanged
and the command prints the exact retry
shipper auto-ship clear-dispatch --force. The forced invocation performs a new preview and sends
its opaque confirmation token directly to the guarded clear operation. The token is not a CLI flag
and is never accepted from the operator.
Discarding dispatch ownership held by a genuinely running holder means two schedulers will dispatch for this repository concurrently.
The cleared result confirms deletion. If ownership disappeared, nothing-to-clear reports a
successful no-op. An unavailable inspection or changed holder exits nonzero, states that nothing
was cleared, and requires inspection and a fresh retry.
Exit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The shown ownership is cleared, or nothing holds ownership. |
| 1 | Confirmation is required, inspection fails, or ownership changes. |
Constraints
Section titled “Constraints”- The operation is scoped to the current checkout repository and never enumerates or changes ownership for another repository.
- Preview and successful clear report the exact public holder facts: repository, surface and PID, acquisition timestamp, liveness, and diagnostic-only last refresh.
- The command does not enable, disable, halt, resume, or otherwise rewrite Auto-ship desired state.
- Dispatch ownership has no timeout or expiry, and this command makes no time-based decision.
- A changed confirmation target is never deleted; run a fresh tokenless preview before deciding again.