What is Synkro?A package manager for agents, with Rules for using your software.Getting startedQuickstartInstall Synkro, connect your agent, and verify a decision.Getting startedSet 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.GuidesActivity and statsSummarize recorded actions, decisions, matched Rules and agent activity.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.GuidesEstimate your costGet a free cost projection from your agents' session history and project Rules.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
Guides

Activity and stats

See how often Synkro checks actions, which Rules match, and where your agents are working.

Use synkro stats for a summary of your recorded Synkro activity. It shows tool attempts, sessions, decisions, matched Rules, projects, agents and approval statuses. Use Events to inspect the individual actions behind those numbers.

See your activity

synkro stats

The default window is the past seven days. A human's signed-in CLI sees the organization's activity. When your connected agent runs the command, it sees activity from its own connection and installation.

The report starts with total tool attempts and sessions, followed by outcomes and per-agent activity bars. Tables stack into labeled rows in narrow terminals. Set NO_COLOR=1 for uncolored output, or use --json for structured results.

SectionWhat it tells you
Recorded tool attemptsHow many tool requests Synkro recorded in the selected period. A retry is another attempt.
SessionsHow many agent sessions had recorded tool attempts.
Outcome and semantic checkHow many attempts received each decision and semantic-check status.
HarnessesWhich agents, such as Codex or Claude Code, produced those attempts.
ProjectsThe recorded working directories where those attempts happened.
Rules matchedHow many distinct attempts matched each Rule.
Current consent statusThe current approval status of requests associated with those attempts.

One action can match several Rules. It counts once in the total, and once under each matched Rule. Approval statuses are current, not a count of every status change during the period.

An allow decision does not necessarily mean a semantic check completed. Read the semantic-check status alongside the decision. NULL means a value is unavailable, including an attempt without a recorded verdict; it does not mean Allow or zero.

Choose a period, project or agent

synkro stats --from 2026-10-01 --to 2026-10-21
synkro stats --project /work/payments
synkro stats --project /work/payments --harness codex

--project matches the exact recorded working directory, not a project name or path prefix. Run the unfiltered command first to find that value. --harness matches the recorded agent name, such as codex or claude_code. Without these filters, the report includes all activity you can access.

Dates include the entire final day and use your configured events_timezone (local time by default). For an exact interval, use RFC3339 timestamps with an offset. See time formats.

Use the results with your agent

synkro stats --from 2026-10-01 --to 2026-10-21 --json

Ask your agent to summarize the most frequently matched Rules, compare projects, or explain the balance of allowed, flagged, approval-required and blocked attempts. JSON includes the applied window, as_of, scope, tool_attempts, sessions, and the grouped results. Ranked lists can be shortened; ranked_lists_truncated tells you when that happens. Totals and outcome counts still cover the whole selected window.

To inspect the actual decisions in the same period:

synkro events --type verdict --from 2026-10-01 --to 2026-10-21 --details

Follow Events to read the related prompts, tool inputs, Rule checks and results. Stats counts recorded tool attempts, not every message or task your agent worked on. For current enforcement health, use synkro status. For charges, use Billing and usage; for a cost projection, use Estimate your cost.

No activity yet?

Check the account and organization with synkro whoami, then run synkro status. Try a wider date range and remove the project or harness filter. To record your first governed action, follow Verify a decision.