Disable and uninstall

Pause Coskey back to stock behaviour, and what to do with adopted sessions before removing it.

1. Pausing

Turn off the global switch in Settings, or:

coskey disable    # keep everything installed; the wrapper becomes a passthrough (restart the app)
coskey enable     # turn it back on

Use this when troubleshooting or when you want official models for a while: nothing about your configuration or keys changes.

2. Uninstalling

The app has an uninstall action that removes the login injection (macOS LaunchAgent / Windows user environment variable), the wrapper and its runtime state. Configuration and keychain entries are kept by default, so reinstalling needs no re-entry of providers or API keys; an option deletes config and logs along with them if you want a clean slate.

After uninstalling, ChatGPT.app returns to stock behaviour on its next restart and the system is back to normal.

3. What happens to adopted sessions

Adopted sessions store coskey as their provider. Remove Coskey outright and those sessions will not open in ChatGPT.app. The uninstall flow asks what to do:

  • Keep as is (default) — right if you plan to reinstall, since adoption resumes automatically;
  • Restore the pre-adoption provider — writes the provider each session had before adoption back, handing the sessions over to native opening.

You can also hand sessions over first and uninstall later: use the Sessions page, or coskey hand-over to do it in bulk. See Sessions, status and settings.

4. About writes to ~/.codex

Coskey does not write to ~/.codex by default. The only two exceptions are explicit user actions, and both back up first and guard against stale values:

  1. handing sessions over (coskey hand-over);
  2. choosing “restore the pre-adoption provider” during uninstall.

Both require ChatGPT.app to be closed (thread write locks are checked), and both report a summary before and after writing.

PreviousFAQ