shipper settings unset

shipper settings unset

Usage: shipper settings unset [options]

Remove one setting from an explicitly selected scope

Arguments

Argument	Required	Description	Choices
	yes	settings key	-

Flags

Long	Short	Value	Default	Description	Choices
—json	-	-	false	output the result as JSON	-
—user	-	-	-	write user-global settings	-
—repo	-	-	-	write repository settings	-
—personal	-	-	-	write personal repository settings	-
—skip-agent-verification	-	-	-	force the write past rejected or unavailable agent verification	-

Examples

Remove only the personal command-model override.

shipper settings unset commands.implement.model --personal

Reveal the committed repository value or auto-detection and print the result as JSON.

shipper settings unset defaultBaseBranch --personal --json

Remove an explicit axis and return to dependency-based inference.

shipper settings unset reviewDelivery --repo

Reveal the committed strategy or the default rebase behavior.

shipper settings unset baseIntegration --personal

Exit Codes

Code	When
0	The selected raw value is removed and the result is printed.
1	Scope selection, key validation, repository setup prerequisite, repository policy, personal identity, or writing fails.

Constraints

• Exactly one of --user, --repo, or --personal is required.
• Only the selected scope is changed; the next applicable layer or default becomes effective.
• cliVersion, mirrorMode, transport, pullRequests, and reviewDelivery require --repo.
• defaultBaseBranch accepts --repo or --personal and rejects --user.
• baseIntegration accepts --repo or --personal and rejects --user; clearing a personal value reveals the committed strategy or the rebase default.
• The complete candidate settings resolution, including inferred values and cross-setting dependency rules, is validated before atomic replacement; a correcting repository edit remains available when committed policy is already invalid.
• Repository-scoped changes require shipper setup --repo to have created .shipper/settings.json; otherwise the change is not applied and may be retried after setup.
• An absent user-global or personal unset is idempotent and creates the selected file; an absent repository layer is refused until repository setup is complete.
• Changes to effective agent, model, or reasoning effort tuples are verified before writing; rejected and unavailable outcomes leave the file unchanged.
• --skip-agent-verification explicitly stores changed agent settings without a passing probe and reports the bypass.
• After repository setup creates .shipper/settings.json, repository mutations do not require GitHub authentication or linkage. Repository-target setup supports either a GitHub-backed repository or a committed fully local repository with no transport; a non-GitHub origin remains unsupported. Personal scope requires a resolvable personal settings identity.