Skip to main content
About two minutes, once per machine. You need a Synapse login in your organization.
1

Install the CLI

macOS builds are signed and notarized by Apple. If synheart isn’t found afterwards, see Add to PATH.
2

Sign in

A browser window opens. Sign in with your work account.
3

Join your team and add the hook

Run synheart, open Synapse → Set up guard. Or from the command line:
team join fetches your organization’s rules. install --write adds the guard hook to ~/.claude/settings.json, keeping your other settings and hooks and saving a backup first. Add --project to install it for the current repository only (.claude/settings.local.json).
4

Restart Claude Code

Restart it, or run /hooks inside it. From now on, each shell command and file edit is checked before it runs.

​
Check it works

check runs nothing. It shows what the guard would decide for a command in the current directory. In the TUI, Synapse → Guard status shows whether the hook is installed, which team policy version you have, and when it last synced.

​
What happens when a rule fires

  • deny — the agent is told no, with the rule’s own words, and tries another way.
  • ask — Claude Code asks you before the action runs.
  • Nothing matches — the agent’s own permission settings decide, as before.

​
Letting something through

When a rule is right in general but wrong right now, grant yourself a scoped exception. Only you can, from your own terminal; an agent can’t.
  • --for defaults to 1h; the maximum is 168h (a week).
  • --repo, --branch and --path narrow where it applies.
  • synheart guard rules lists the rules in force here and your active exceptions.

​
Your own numbers

It shows how many actions were checked, stopped, asked about and let through, per rule, for the last 7 days (--since 720h for 30). The same totals appear under Agents → Mine at synapse.synheart.ai. Only rule ids and counts leave your machine: never a command, a file path or a prompt.

​
Commands

​
Troubleshooting