How to uninstall Alma on Mac
Alma is an AI chat app and agent client for Mac, Windows, Linux and phones from alma.now (bundle ID com.yetone.alma). Its docs describe chat threads, memories and skills that stay on your Mac; the vendor's installation page says deleting ~/Library/Application Support/alma resets its data. Two folders deserve a look before you remove anything: ~/.config/alma/skills/ holds your personal skills (skills docs), and Alma also reads ~/.claude/skills/, which is Claude Code's folder and which this guide never touches. If you entered API keys for model providers, revoke them in the provider's console when you stop using them; removing the app does not do that. This guide covers the Apple silicon disk image from alma.now and the Homebrew cask alma.
Quit and remove the app
- Copy out anything you want from
~/.config/alma/skills/and any chat or memory content you want to keep. Alma's memory page lets you review stored memories before you delete them. - Quit Alma with Command + Q. It starts a bundled server (
alma-server) and a helper app named Alma Computer Use inside the app bundle; in the test the whole group, 6 processes, showed as one Alma row in Mole's Status page. Alma also has an Auto-Start option under its General settings; the test registered no login item or launch agent. - Open Finder, go to Applications and drag Alma to the Trash.
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/Application Support/alma |
Alma's data folder (9.7 MB in the test, with a logs folder inside) |
Copy what you need, then remove. Mole lists it for review and selects it by default when eligible; its logs folder is selected by default. |
~/Library/Application Support/alma-native |
A small folder named like the native app's update product (8 KB) | Remove. Mole lists it for review and selects it by default when eligible. |
~/.alma |
Not described in Alma's docs; 100 KB in the test | Open it, then remove if you recognise nothing you need. Mole lists it for review and selects it by default when eligible. |
~/.config/alma |
Your personal skills in skills/, per the docs, plus other settings |
Copy out first, then remove. Mole lists it for review and does not select it. |
~/.cache/alma |
Cache, empty in the test | Remove. Mole lists it for review and does not select it. |
~/.local/bin/alma |
A 171-byte file Mole lists as Alma's helper tool | Open it to confirm it is Alma's, then remove. Mole lists it for review and selects it by default when eligible. |
The folder getconf DARWIN_USER_CACHE_DIR prints, then com.yetone.alma |
Temporary cache, 926 KB in the test | Remove. Selected by default. |
~/.claude/skills |
Claude Code's skills, shared with Alma | Keep. Mole does not list it. |
Check the result
pgrep -il 'alma|AlmaComputerUse'
ls -d /Applications/Alma.app "$HOME/Library/Application Support/alma" "$HOME/Library/Application Support/alma-native" "$HOME/.alma" "$HOME/.config/alma" "$HOME/.cache/alma" "$HOME/.local/bin/alma"
launchctl list | grep -i alma
- No output from
pgrepmeans Alma and its server are not running.almaalso matches unrelated names, so read what is printed; a line namingalma-serveris Alma's own server still alive. - For
ls -d,No such file or directorymeans that path is gone. A printed path is still on disk. A surviving~/.config/almais expected if you kept your skills. - No output from
launchctlmeans no Alma job is loaded for your user.
If you installed it with Homebrew
brew uninstall --cask alma
The cask quits Alma and removes the app, nothing else. Its zap list trashes ~/.alma, ~/.cache/alma, ~/.config/alma (your personal skills), ~/Library/Application Support/alma and the updater, ShipIt, HTTP storage and preferences entries in ~/Library. A direct brew uninstall --cask --zap alma runs that whole list and 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 or unsupported directives suppress it), and here the list reaches outside ~/Library, so Mole removes the rows you selected itself. The Homebrew install was not tested.
What Mole lists
Mole selects the app, ~/Library/Application Support/alma/logs and the temporary cache row. It lists ~/Library/Application Support/alma, ~/Library/Application Support/alma-native, ~/.alma and ~/.local/bin/alma for review and selects them by default when eligible, and lists ~/.config/alma and ~/.cache/alma for review without selecting them. Status shows Alma as one row, and Mole found no update channel for it: Alma carries its own app-update.yml feed, which Mole does not read as a Sparkle or Electron updater.
What this test covered
On November 9, 2026, alma-0.4.534-mac-arm64.dmg from alma.now, whose checksum matched the Homebrew cask, was copied to Applications on a test Mac without running brew install and opened once. It was removed with a source-built Mole with every review row ticked. Mole asked Alma and its Computer Use helper to quit and moved the app and 8 rows to the Trash with no failures; a rescan then found nothing left. No account or API key was entered and no chat, memory or skill was created, so what those hold was not tested, nor were the Homebrew install and Mole's notarized release build.
