How to uninstall Kaset on Mac

Kaset is an open-source YouTube Music client for the Mac, from github.com/sozercan/kaset. It is sandboxed, so almost everything it keeps sits in one container folder instead of loose files in ~/Library. You sign in with a Google account, and its architecture notes say it backs up the sign-in cookies to the macOS Keychain so you stay signed in across app updates. Sign out inside Kaset before you remove it, then check Keychain Access for a leftover Kaset item; the test never signed in, so whether an item remains was not tested. Removing the app does not cancel YouTube Music Premium or touch your Google account, which you manage with Google. This guide covers the disk image from the project's GitHub releases and its Homebrew cask.

Quit and remove the app

  1. Sign out inside Kaset, and note any favorites you want to keep. Its notes put favorites in a Kaset folder under Application Support, which for a sandboxed app is inside the container below; copy that folder if you want them.
  2. Quit Kaset with Command + Q. In the test it ran as 2 processes (the app and a WebKit networking process) and registered no login item or launch agent.
  3. Open Finder, go to Applications and drag Kaset.app to the Trash.
  4. Remove the container yourself if Mole could not (see below). Quit Kaset first; macOS may still refuse to trash a sandbox container unless the app doing the removal has Full Disk Access, so either grant it in System Settings › Privacy & Security › Full Disk Access or move the folder to the Trash yourself in Finder once Kaset has quit.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Location What it holds What to do
~/Library/Containers/com.sertacozercan.Kaset The sandbox: its Application Support folder (favorites), WebKit and image caches, preferences and logs Copy favorites first if you want them, then remove. Selected by default; with Full Disk Access Mole can move it, without it Mole's report asks for that permission.
~/Library/Application Scripts/com.sertacozercan.Kaset An empty scripts folder Remove. Selected by default.
The folder that getconf DARWIN_USER_CACHE_DIR prints, then com.sertacozercan.Kaset Mole's temporary cache row, 20 KB in the test Remove. Selected by default.
A Kaset item in Keychain Access (login keychain) The saved Google sign-in, according to the project's notes; not seen in the test Delete it yourself after you sign out, if one is there.

Check the result

pgrep -il kaset
ls -d /Applications/Kaset.app ~/Library/Containers/com.sertacozercan.Kaset ~/Library/Application\ Scripts/com.sertacozercan.Kaset
  • No output from pgrep means Kaset is not running. A printed line is a process still alive; quit it and run the command again.
  • For ls -d, "No such file or directory" means that path is gone. A printed Containers path means the container is still on disk, which is what the test ended with.

If you installed it with Homebrew

The project publishes its own tap, sozercan/repo.

brew uninstall --cask kaset

The tap's cask has no uninstall stanza, so this removes the app only. brew uninstall --cask --zap kaset also trashes ~/Library/Application Support/Kaset, ~/Library/Caches/com.sertacozercan.Kaset, the preferences file, Saved Application State/com.sertacozercan.Kaset.savedState and ~/Library/WebKit/com.sertacozercan.Kaset. These are plain ~/Library paths; a sandboxed app's real data is in the container, which the zap list does not name. A direct brew command does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate (unchecked or shared paths, paths outside the reviewed boundary, unknown stanzas and unsupported directives suppress it), and otherwise removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app, ~/Library/Application Scripts/com.sertacozercan.Kaset, ~/Library/Containers/com.sertacozercan.Kaset and its temporary cache row. Before removing, Mole asks Kaset to quit. The container is the one that needs Full Disk Access to move.

What this test covered

On November 9, 2026, the test downloaded Kaset 0.14.2 as a universal disk image from the project's GitHub releases, whose checksum matched the Homebrew tap's cask, copied the app to Applications without running brew install, launched it once and quit it. A source-built Mole with the review rows ticked moved the app, the scripts folder and the temporary cache row to the Trash. The container stayed because the test build ran without Full Disk Access (macOS refused with error 513), and it was the only path left afterwards. Status showed one Kaset row with 2 processes. Mole detected a Sparkle updater, and no update was run. No Google account was signed in, so cookies, the Keychain backup, favorites and playback were not tested, and neither were the Homebrew install and Mole's notarized release build.