Synapse

Synapse is the layer between your engineering team and the AI coding tools it uses. It does three things:

Agents follow your rules

Team rules are checked before an agent pushes, merges, deletes or edits. A rule can stop the action or ask a person first.

Any MCP agent can recall what your organization decided and why, from repositories, Notion, Drive and Slack.

What you pay for GitHub Copilot and Claude Code, which seats go unused, and what agents were stopped from doing.

Role	Does	Guide
Admin (CTO, platform lead)	Connects GitHub and AI vendors, writes the team rules, turns on the weekly summary	Set up your team
Developer	Installs the CLI once; their coding agent then follows the team rules	Developer setup

Synapse reports on teams, not people.

Agent rules. Each developer’s machine sends day totals per rule: how many times it stopped an action, asked, or was let through. Never the command, the file, the prompt or the repository.
Team views have a floor. The team report and per-team rows appear only when enough people contribute (your organization’s cohort floor). Below it, totals are withheld rather than shown, so a total can’t describe one person.
AI spend. Vendor data is reduced to counts and totals as it’s read: seats, active users, sessions, estimated cost. No login, email or per-person usage is stored.
Organization knowledge. Only sources an admin designates are indexed, and source permissions still apply when content is recalled.

A Synapse organization at synapse.synheart.ai.
Coding agents: rules are enforced in Claude Code. Organization knowledge works in any MCP client (Claude Code, Cursor, Claude Desktop).
The Synheart CLI 0.18.0 or later on each developer’s machine (macOS, Linux or Windows).