What is Synkro?A package manager for agents, with Rules for using your software.Getting startedQuickstartLet your agent set up Synkro, create your first Rule, and verify an action.Getting startedSetup checklistCheck your account, installation, repository, and first agent decision.SetupInstall and verifyInstall the CLI, sign in, and connect your agent.SetupSet up your agentConnect your agent and verify its first tool call.SetupVerify a decisionFind the recorded decision for an agent action.SetupYour first decisionRead your first agent decision and test a Rule.SetupHow Synkro worksUnderstand how Synkro applies Rules and records agent decisions.Core conceptsRules and ControlsChoose repository Rules for actions and Controls for access restrictions.Core conceptsRule outcomesUnderstand when an action continues, needs approval, or must be changed.Core conceptsRulesAdd, test, update, and remove the Rules used by your repository.GuidesEventsFind recorded agent actions and decisions with the Synkro CLI.GuidesApprove MCP toolsChoose project approvals and package defaults for MCP tools.GuidesConsentReview and approve an agent action before it runs.GuidesFeedbackReport a Synkro bug or suggest an improvement with diagnostic context.GuidesBilling and usageAdd funds and check your organization's balance and usage.GuidesGitHubConnect GitHub to discover Rules from private repositories.IntegrationsCLI commandsFind the current commands for setup, Rules, events, account, and recovery.ReferenceSupported agentsFind the installed Synkro files and the checks that apply to each agent.ReferenceTroubleshootingFix setup, sign-in, missing decisions, Rule, and approval problems.Reference
Documentation
Core concepts

Rules and Controls

Choose repository Rules for actions and Controls for access restrictions.

Rules check actions

A Rule checks an agent action. Your team keeps it in a TOML file in the repository's Rule package.

Examples:

  • Stop a command that deletes a protected directory.
  • Ask for approval before adding a dependency.
  • Flag an edit that breaks a project requirement.

Use the Rules guide to add and test one.

Controls restrict access

A Control restricts access for everyone, a user, or a group. For example, it can block calls to a named MCP server.

Controls are not Rule files. An organization owner manages them through an authorized integration; there is no general Control editor command.

MCP approvals

An MCP approval permits a server/tool coordinate under the project's published policy. Projects declare approvals or denials in synkro.toml; packages supply approve-only defaults in synkro-package.toml. Project exact entries take precedence over project wildcards, which take precedence over package defaults.

Without approval, observe mode flags the call with a notice; enforce mode blocks it. Approval removes only that check. It does not override another Rule or Control and does not grant one-action consent.

Use Approve MCP tools to review a scope, edit it with the CLI and verify the next recorded call.

One does not cancel the other

Allowing an action through a Control does not override a blocking Rule or the setting that blocks unmatched MCP calls.

If an action is refused, inspect its decision to see which check refused it:

synkro events --type verdict --limit 5 --details

Use a Rule for checks specific to a repository. Ask your organization owner about access Controls.