Install an agent integration
Open Provider settings
- Expand the provider's card. Hooks exist for Claude Code, Codex, Antigravity CLI, Pi, OpenCode, and GitHub Copilot CLI.
- Review the note describing what Saggar will add to the provider's configuration file. The button appears once the provider's CLI is installed.
- Choose Install hooks.
The hooks report provider events using the SAGGAR_SESSION identifier already
present in Saggar terminals. They improve prompt detection and, where the
provider supports it, exact session resume.
Installation is opt-in. Remove hooks deletes only entries owned by Saggar and leaves the rest of your provider configuration alone. The provider continues to work without hooks; Saggar falls back to process and screen recognition.
How the entries land depends on the provider. Claude Code, Codex, and Antigravity CLI get Saggar's entries added to a configuration file they already read. GitHub Copilot CLI, Pi, and OpenCode get one Saggar-owned file in a directory the CLI scans, so if a file by that name already exists and Saggar didn't write it, the install refuses and asks you to move it aside rather than merging into it.
From a terminal
saggar hooks does the same work without opening Settings, which is useful when
you are setting up a Mac from a shell:
saggar hooks
saggar hooks install claude
saggar hooks remove codex
A bare saggar hooks only reads: one row per provider — installed,
not-installed, or no-cli — with the configuration file an install would
edit, and anything still blocking a hook underneath. install refuses when the
provider's own CLI isn't on this Mac and names the command that installs it.
See the saggar CLI reference for the flags.
See Providers for the provider-by-provider behavior.