.agents / sync
Unified multi-device cloud synchronizer for the entire ~/.agents ecosystem.
Zero heavy client dependencies. Standalone sync engine decoupling and replacing legacy memory-only sync.
Synchronized Domains
| Domain | Path | Sync Strategy |
|---|---|---|
| Memory | ~/.agents/memory/ |
3-way markdown merge with bullet-level tombstone tracking (.tombstones.json). |
| Skills | ~/.agents/skills/ |
Mirror active agent workflows and skills across all workstations. |
| Docs | ~/.agents/docs/ |
Mirror technical platform documentation and reference sheets. |
| Rules | ~/.agents/rules/ |
Sync global agent rule definitions. |
| Identity | ~/.agents/identity.json |
Deterministic merge for user, session, and alias mappings. |
| Traces | ~/.agents/traces/ |
Append-only chronological event stream merging with timestamp deduplication. |
| Known DIDs | ~/.agents/known-dids.jsonl |
Append-only public keys of verified peers and agents. |
Security & Key Isolation
Quickstart
1. Installation
Install the client (zero external dependencies, pure Python standard library):
pip install agents-sync
2. Connect to Cloud Vault
# Connect to your remote vault server
agents-sync connect https://vps.example.com:8765 --token YOUR_SECRET_TOKEN
# Check connection health and status
agents-sync status
3. Synchronize State
# Bi-directional sync (push local changes + pull remote changes)
agents-sync sync
# Or selectively push / pull specific domains:
agents-sync push --domains memory,skills
agents-sync pull --domains memory,skills
# Disconnect and remove local credentials:
agents-sync disconnect
Cloud Server Deployment
Run a private cloud vault server on your VPS, server, or Coolify instance:
pip install "agents-sync[server]"
# Token is provided via environment variable:
export AGENTS_SYNC_TOKEN="your-secure-bearer-token"
export AGENTS_SYNC_VAULT_DIR="/var/lib/agents-sync-vault"
agents-sync serve 8765
Docker / Coolify
docker run -d \
--name agents-sync \
-p 8765:8765 \
-e AGENTS_SYNC_TOKEN="your-secure-bearer-token" \
-v agents_sync_vault:/root/.agents-sync-vault \
ghcr.io/lolaplex/agents-sync:latest
Wire Protocol & Path Independence
Project memories and repository facts are keyed strictly by abstract slug (projects/<slug>/), never by absolute host paths (C:\Users\... or /home/...). Each local node independently resolves slugs to its own local checkouts via its configured inventory scan roots.
Metadata
Release files for agents-sync 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agents_sync-0.1.0.tar.gz | 19.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agents_sync-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / agents_sync-0.1.0.tar.gz
| Download URL | agents_sync-0.1.0.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
424505d4329bbb24ff5da005f5021f6326bec4136769d538cd26bb3d022e4bcd
|
|
BLAKE2b-256 checksum How to use checksums |
1e06c54e367a8d76ae55496a9ab2220d67487b86a1ec34464a063fac90424b81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.6
|
Release files / agents_sync-0.1.0-py3-none-any.whl
| Download URL | agents_sync-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6ed349a60b432aac9b1d540552e99682103c3d242af35347d063b702ce0b658
|
|
BLAKE2b-256 checksum How to use checksums |
6c38d7a2cf816a0fdff06bd41a74ab2de62dc09ff74394d2c79882db47503e38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.6
|
Security for agents-sync 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.