Uninstalling

loadout uninstall          # lists everything, removes nothing
loadout uninstall --yes    # do it

The default is a dry run. It prints the complete inventory — directories, managed binaries, scripts, and every keychain entry — and removes nothing.

Why not just delete the directory

Deleting ~/.config/loadout by hand leaves every keychain entry behind, and leaves them unfindable: your configuration was the only record of what they are called. They sit in your keychain indefinitely under names you no longer have a list of.

loadout uninstall enumerates them by name first, including any the configuration has forgotten about, and asks for a separate confirmation before deleting a secret.

Keeping some of it

loadout uninstall --yes --keep-config        # keep ~/.config/loadout
loadout uninstall --yes --keep-credentials   # leave the keychain alone entirely

--keep-config is for a reinstall: your configuration survives, so the new install picks up where you left off. --keep-credentials skips both the deletion and the prompt.

Two things it will not do

It will not edit your shell configuration. It never wrote that line, so it does not remove it. It prints the exact line to delete:

source ~/.config/loadout/init.zsh

Remove that from ~/.zshrc (and the eval "$(loadout env --quiet)" line, if you added one). Until you do, your shell will report a missing file on every start.

It will not delete its own binary. A process removing the file it is executing is avoidable awkwardness, and which command is correct depends on how you installed it:

Installed with	Remove with
The install script	rm ~/.local/bin/loadout
Homebrew	brew uninstall loadout
go install	rm $(go env GOPATH)/bin/loadout

It prints the right one for your install.

What gets removed

	Removed	Kept with
~/.config/loadout/	Yes	--keep-config
~/.local/share/loadout/	Yes	—
Managed binaries and scripts	Yes	—
Keychain entries	Yes, after a separate confirmation	--keep-credentials
The line in your shell config	No — printed for you	—
The loadout binary	No — command printed	—

Your configuration repository, if you set up sync, is untouched. It is a git repository you own on a host loadout has no access to.