Skip to main content
Agents, at synapse.synheart.ai, shows what the guard did with your coding agents’ actions: what it stopped, what it asked a person about, and what an exception let through. It’s built from counts only. No command, file path or prompt is ever sent or shown. The guard and its rules are explained in Writing rules. To set it up on a machine, see Set up as a developer.

​
The top of the page

  • Team or Mine. Mine shows your own agents. Team shows everyone’s, added up, and is for Synapse Leads and Admins. Members see Mine only.
  • Period. 7 days or 30 days.
  • Refresh reloads the figures.

​
Summary

​
Rules

Agent actions by rule lists each rule that did something in the period: Search by rule, or use the chips to show only rules that Blocked, Asked or ran in Shadow. When a rule was asked about at least five times and approved every time, a note under the table names it and says it may no longer need a person. That’s a candidate to relax, so developers are interrupted less. See When rules are too strict.
Before turning a new rule on for everyone, add shadow: true and watch its Shadow count for a week. If it would fire on work you’re happy with, adjust it before it starts stopping anyone.

​
By coding agent

When more than one coding agent reports, such as Claude Code and another agent, By coding agent shows the same counts for each. See Connect your agent.

​
When nothing shows

If no machine has reported yet, the page says No agent activity reported yet and offers the setup commands to copy:
Then restart Claude Code. Activity appears after the next agent session. The steps are explained in Set up as a developer.

​
Team decisions

On Team, What Synapse advised the team’s agents shows what Synapse told agents when they asked it for context. Team totals only. First-pass acceptance and Correction cycles come only from explicit verdicts: developers running synheart feedback accept or reject, or choosing accept or reject on Agent checks. Below them:
  • Most common reasons the agents were asked or stopped.
  • Decisions cited most, the team decisions agents leaned on.
  • Intent check, when your organization uses it: how often the agent stopped to ask or flag, and whether the developer Accepted, Edited or Overrode it.

​
Your Claude Code usage

At the bottom, everyone sees their own Claude Code usage for the last 7 days: Sessions, Input tokens, Output tokens and Cache tokens (read and written). API-equivalent value estimates what those tokens would cost at API prices. It isn’t money spent. Only you see this section.

​
Team rules

Team rules shows the rules every developer’s agent follows, and their version, such as v4. Open it to read them as YAML. Everyone can read them. Only Synapse Admins can change them. Each save is a new version. Developers’ machines pick it up within 15 minutes. For the format and an example to start from, see A team example.

​
Who can see what