How to uninstall Orca on Mac
This guide covers Stably's Orca coding environment, not Plotly's same-named app. Save code and check repositories and worktrees before removal. In the current official hook documentation, turning off Settings > Agents > Agent status hooks removes Orca-managed hooks and stops reinstalling them. If your version provides this control, turn it off before quitting; keep unrelated agent configuration and conversation archives.
Remove Orca and review its local state
Quit Orca, then copy wanted contents from ~/Library/Application Support/orca and ~/.orca to a checked backup before removing the actual Orca app from Applications. The recorded ~/.orca/agent-hooks contains generated hook scripts. Removing its directory does not edit hooks already written into other agents' settings. Keep those settings intact unless the entries are confirmed to belong to Orca and their version-specific removal is understood.
The Homebrew cask named orca describes Plotly's chart exporter and different identity; it is not the uninstall command for this IDE.
ls -ld "$HOME/Library/Application Support/orca"
ls -ld "$HOME/.orca/agent-hooks"
Printed paths remain. A missing-path error applies only to that location; permission errors leave it unknown. Absence of these folders does not establish removal of every configured hook, worktree or agent session.
What Mole lists
The selected app is checked by default. The display-name support folder and the exact ~/.orca user-data rule for this product are reviewed and unchecked by default. Remove data and settings with apps is off by default; eligible reviewed data may be included when enabled, so keep repositories, wanted state and shared agent archives unselected. Mole does not rewrite other agents' configuration files.
What this test covered
The official Stably Orca app and selected support and temporary data were removed with source-built Mole on September 23, 2026. The generated hook directory was not collected in that run; the test machine's Orca-owned configuration entries and directory were handled manually afterward. The later exact user-data rule was not retested in the official app. Populated project recovery and the current vendor hook-disable flow were not tested.
