Uninstall Code Config

One command removes Code Config from a Mac or a Linux computer: the desktop app, the csc command, the settings they keep, and the keys Code Config stored here. Your projects stay where they are, and nothing is edited out of your shell startup files.

The keys you added to your toolkits live only on this computer. Removing Code Config removes them too, and the preview says so. To remove Code Config and keep the keys, run the command in the next section with --keep-keys; you can then delete them yourself later from Keychain Access (on a Mac) or your keyring, where they are the entries named dev.configurator.csc, dev.configurator.csc.accounts and dev.configurator.csc.secrets. Keys Code Config kept in a file instead live in ~/.code-shared-config/broker.

See what it will remove

Run this first. It prints what it found and changes nothing:

curl -fsSL https://dl.code-config.com/uninstall | bash

The list names each folder and file, any package installed for everyone on this computer, and the keys stored here. On a Linux computer with no keyring tool, it says so rather than looking. Read the list, then decide.

Remove Code Config

curl -fsSL https://dl.code-config.com/uninstall | bash -s -- --yes

It closes Code Config and removes what the list showed, keys included. On Linux, a package that was installed for everyone on the computer asks for your password.

It also tells your account this computer is gone, so it stops appearing under Settings → Computers in the web app. A computer that cannot reach the internet when you remove Code Config stays on that list, and you can remove it there yourself.

Keep the keys

curl -fsSL https://dl.code-config.com/uninstall | bash -s -- --yes --keep-keys

Everything else goes. Keys in your login keychain or keyring stay where they are, and keys Code Config kept in its own folder stay in ~/.code-shared-config/broker, which is left in place for them.

When it finishes, it reports either that nothing of Code Config is left on this computer, or a short list of what is still here. The report also names what it kept on purpose: the file in ~/.local/bin that other developer tools share, and your projects.

Common problems

Code Config is still open: the command closes it for you. If a window is still on screen after the command finishes, quit Code Config and run the command again.

csc is not found after you install Code Config again: open a new terminal. The one already open settled which folders it searches before the install ran.

The Linux app is still on this computer: the command looks for the .AppImage file in ~/Applications. If you saved yours somewhere else, delete that file yourself.

Next

Install Code Config.