shipper settings check
shipper settings check
Section titled “shipper settings check”Usage: shipper settings check [options]
Verify every stored effective agent, model, and reasoning effort
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —json | - | - | false | output the verification report as JSON | - |
Examples
Section titled “Examples”Probe every stored effective agent, model, and reasoning-effort combination.
shipper settings checkPrint stage-by-stage verification results with supplying-file provenance.
shipper settings check --jsonExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | Every combination passes or only unconfirmed efforts are reported. |
| 1 | Any combination is rejected or verification cannot run. |
Constraints
Section titled “Constraints”- Distinct primitive agent/model/effort tuples are probed concurrently through real agent invocations.
- The complete check has one 30-second deadline across command preparation and probes.
- The check inspects stored settings, including the default target, and saves no edits.
- Rejected values identify the stage, agent, offending value, supplying settings file, and agent diagnostic.
- Claude and OpenCode efforts that cannot be confirmed are warnings and do not fail the check; Codex, Copilot, and Grok Build report definitive effort rejections.
- The check runs only when explicitly requested; list, get, and bare settings inspection do not probe agents.