Skip to content

Uninstall & reset

Everything Overwire writes lives in the locations mapped on Directory layout — removal is a handful of deletions, with one step first.

  1. Deactivate your license (Pro only) so the machine stops using an activation slot:

    Terminal window
    overwire license deactivate

    Or Settings → License → Deactivate in the app. Skipping this wastes a slot until you deactivate from another device.

  2. Quit the app and remove it: drag Overwire.app out of Applications.

  3. Remove machine state (all rebuildable or now-unused):

    Terminal window
    rm -rf ~/.cache/overwire # run store, action/tool caches, lock files
    rm -rf ~/Library/Application\ Support/Overwire # app state: layout, recent projects, theme
    rm -f ~/.config/overwire/license.json # license state (deactivate first!)
  4. Remove the CLI, if you installed it:

    Terminal window
    npm uninstall -g overwire
  5. Project config (.overwire/ in your repositories) is yours — committable scenario files, not app state. Delete per repo if you no longer want it; .overwire/state/ and .overwire/cache/ are the only run-written parts.

Live-run leftovers: Overwire manages its own runner containers, but the pulled overwireio/runner image stays in your container engine — remove it there (docker rmi overwireio/runner) if you want the space back.

To get a fresh slate but keep Overwire installed, delete the run-derived state only:

Terminal window
rm -rf ~/.cache/overwire # run history, caches — rebuilt on demand

Per project, delete .overwire/state/ and .overwire/cache/ (both git-ignored). overwire cache can inspect and clear the action/tool caches without manual deletion.

  1. Deactivate your license (Pro only) so the machine stops using an activation slot:

    Terminal window
    overwire license deactivate

    Or Settings → License → Deactivate in the app. Skipping this wastes a slot until you deactivate from another device.

  2. Uninstall the app: Settings → Apps → Installed apps → Overwire → Uninstall (asks for administrator approval). This removes C:\Program Files\Overwire and the shortcuts.

  3. Remove machine state (all rebuildable or now-unused), in PowerShell:

    Terminal window
    Remove-Item -Recurse -Force "$env:USERPROFILE\.cache\overwire" # run store, action/tool caches, lock files
    Remove-Item -Recurse -Force "$env:APPDATA\Overwire" # app state and license.json (deactivate first!)

    App state and the license file share one folder on Windows — see Directory layout.

  4. Remove the CLI, if you installed it:

    Terminal window
    npm uninstall -g overwire
  5. Project config (.overwire/ in your repositories) is yours — committable scenario files, not app state. Delete per repo if you no longer want it; .overwire/state/ and .overwire/cache/ are the only run-written parts.

The pulled overwireio/runner image stays in your container engine — remove it there (docker rmi overwireio/runner) if you want the space back.

overwire.io Privacy Terms

Overwire is not affiliated with, endorsed by, or sponsored by GitHub, Inc. “GitHub” and “GitHub Actions” are trademarks of GitHub, Inc.