Team sync
proWhat grith pro sync pulls down, what it pushes up, and what stays on the machine no matter what.
grith pro sync is an on-demand pull of team-shared state, plus one push. It runs when you run
it - there is no sync interval to configure.
$ grith pro syncWithout credentials it stops with Not logged in. Run: grith pro login; on a Community licence
it stops with Sync requires an active Pro license. Run: grith pro activate.
What moves
| What | Direction | Lands at | Used by |
|---|---|---|---|
| Team policy | pull | ~/.config/grith/policies/<name>.json | The policy views - see Centralised policies. |
| Shared configs | pull | ~/.config/grith/configs/*.json | Merged into team-config.toml when you apply them from the dashboard. |
| Provider keys | pull | ~/.config/grith/provider-keys/<provider>.json | Model calls from grith run and the REPL. Encrypted at rest - see Encrypted key management. |
| Team learned rules | pull | ~/.config/grith/team_learned_rules.json | Merged into every new session's allowlist for the matching profile. |
| Reputation | push | grith.ai | The team reputation view. Only entries with three or more observations, in batches of 400. |
Each pulled provider key that no longer exists on the team is deleted locally in the same pass, so revoking a key in the dashboard removes it from every machine that syncs afterwards.
Reputation is push-only. Nothing overwrites your local learned table.
What happens without running the command
- Provider keys refresh from the daemon at most once every 24 hours.
- Team learned rules refresh at the start of every supervised session, so a rule an admin
adds is live on the next
grith execrather than the next manual sync. - Analytics sync themselves from the daemon every 30 seconds. That is a separate worker with a separate consent gate - see Analytics.
What never syncs
Audit records. The raw audit log stays on the machine that wrote it, full stop. Nothing uploads it, and the team dashboard has no view of it - what the team sees is a security-event timeline built from the analytics projection, which carries counts and summaries rather than records.
The digest queue, the local learned-rules file and your config.toml are also local-only.