GenerateSaaSUninstall
Remove a single pairing, stop the daemon driving one CLI, or wipe OpenCompanion entirely - what each command removes and what it leaves in place.
There are three levels of removal, from narrowest to complete. Pick the one that matches what you want gone.
Stop driving one CLI
opencompanion disconnect claude-codeStops the daemon driving that coding CLI. The CLI stays installed and signed in - you just take it out of OpenCompanion's rotation. Re-add it later with opencompanion connect claude-code.
Remove one app's pairing
opencompanion unpair --url https://your-app.example/apiDrops that pairing and deletes its stored session from this machine. A running daemon stops serving that app within one reconcile (about 15 seconds); no restart is needed. Your other pairings and the daemon itself are untouched. See Pairing.
Remove OpenCompanion entirely
opencompanion uninstallThis is the full teardown. It:
- removes the always-on service (the launchd agent, systemd user service, or Windows logon task),
- drops every pairing and deletes their stored sessions, and
- deletes all OpenCompanion data - its config, secrets, work folders, and logs.
Every unpair is written to the audit log before the data directory is removed.
uninstall deletes the local audit log along with the rest of OpenCompanion's data. If you want to keep the record of what ran, copy the audit directory somewhere safe first.
What it leaves behind
uninstall removes OpenCompanion, not the tools it drove. Your coding CLIs stay installed and signed in (Claude Code, Codex, opencode, Hermes) - they are your own subscriptions, and OpenCompanion never owned them. The opencompanion launcher directory may remain on your PATH; remove it by hand if you want it gone.