First-party app · Rsync Sync
rsync-sync
Sync PersonalClaw state between your machines with rsync over ssh. Any host you can already log into works — a home server, a NAS, a VPS. No object store, no credentials beyond your existing ssh key. Shards are encrypted end-to-end by default, and secrets are excluded upstream so they never reach the host.
Before you install
A first-party app of PersonalClaw v0.3.9
No scan on record before install
PersonalClaw publishes no scan of its own apps before you install one.
PersonalClaw runs its own scan of the actual code of every app it installs: this one is rescanned when you install, and that scan is what can stop an install.
Its row on Compare: install rescan
- Compatibility
- Works with PersonalClaw v0.3.9
What it gets
- Permissions
- network: true
- Its own network permission
- On. Its own network permission is a declaration, not a fence.
What it starts
The programs on this machine it starts, as install consent names them.
rsync: rsync copies your PersonalClaw data to the folder or host you set, and reads it back from there.ssh: rsync starts ssh to reach the host you set, when you set one.It runs with your own ssh sign-in and settings.
What it reaches
- Hosts it names
- Not declared in this release's manifest
Its own code has no host list at this release: any hosts it names are for the programs, servers and sources it starts or fetches, not everything it can reach. Its own network permission is a declaration, not a fence.
Secrets you would enter
- Settings marked secret
- Not declared in this release's manifest
What installing it gives and runs
The manifest's own declarations, under the names install consent shows them by and in its order. The Store adds, at install, which of them run as you.
- Permissions it is granted
{ "network": true }- Programs on this machine it starts
[ { "program": "rsync", "why": "rsync copies your PersonalClaw data to the folder or host you set, and reads it back from there." }, { "program": "ssh", "why": "rsync starts ssh to reach the host you set, when you set one.", "inherits": [ "sign-in", "settings" ] } ]- Provider modules the gateway loads
[ { "type": "sync", "implementation": "rsync_sync_transport:create_provider" } ]- What it runs for personalclaw setup
"app_cli:setup"
- What it runs for personalclaw doctor
"app_cli:doctor"
Not declared in this release's manifest:
- Scheduled jobs
- Python packages installed for it
- Engine packages it can install
- What it needs that PersonalClaw does not install
- npm packages installed for it
- Places outside its folder it writes
- Pages it adds to the dashboard
- Components it adds to the dashboard
- A server process of its own
- The sandbox tier its server runs in
- Command run after install
- Command run after an update
- Command run when it is switched on
- Command run when it is switched off
- Command run before it is removed
- Connector sources it parses
- MCP servers it adds
- Skills it installs
Where it comes from
- Publisher
- PersonalClaw
- License
- MIT
- Pinned commit
- 169cbc4f8fc59cd42a65a6a3546235bc49ab3b22
- Signer
- Not declared in this release's manifest
From review to enable
- Held and scanned. An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.Its row on Compare: install rescan
- A dangerous verdict ends it. A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.Its row on Compare: dangerous verdict
- You review and consent. The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.Its row on Compare: consent
- Its setup runs, then you switch it on. Nothing it declares runs before your consent; an app already installed is offered as an update instead.
To install it and switch it on
- In PersonalClaw, open the Store.
- Find rsync-sync.
- Review what it gets and runs, and consent.
- Install it, then switch it on.
Evidence
rsync-sync/app.json at the pinned commit, as written, with the blob hash git lists for it: 3295d5b5dc3745e70b7a434f1901f27c9b15b66f
{
"name": "rsync-sync",
"version": "0.1.10",
"displayName": "Rsync Sync",
"description": "Sync PersonalClaw state between your machines with rsync over ssh. Any host you can already log into works — a home server, a NAS, a VPS. No object store, no credentials beyond your existing ssh key. Shards are encrypted end-to-end by default, and secrets are excluded upstream so they never reach the host.",
"icon": "Server",
"author": "PersonalClaw",
"license": "MIT",
"tags": [
"sync",
"bundled"
],
"permissions": {
"network": true
},
"launches": [
{
"program": "rsync",
"why": "rsync copies your PersonalClaw data to the folder or host you set, and reads it back from there."
},
{
"program": "ssh",
"why": "rsync starts ssh to reach the host you set, when you set one.",
"inherits": [
"sign-in",
"settings"
]
}
],
"cli": {
"setup": "app_cli:setup",
"doctor": "app_cli:doctor"
},
"provider": {
"id": "sync",
"label": "Sync with rsync over ssh",
"type": "sync",
"implementation": "rsync_sync_transport:create_provider",
"capabilities": [
"sync"
],
"settingsSchema": {
"type": "object",
"properties": {
"host": {
"type": "string",
"default": "",
"x-meta": {
"label": "SSH host",
"help": "The ssh destination, optionally with a user — e.g. nas.local or backup@nas.local. Leave empty to rsync to a local or mounted path instead (then only the path below is used). Only letters, digits, dot, dash and underscore are accepted."
}
},
"path": {
"type": "string",
"default": "",
"x-meta": {
"label": "Sync root path",
"help": "Absolute path to the sync root ON THE TARGET (e.g. /srv/personalclaw-sync), or a local absolute path when no host is set. Supports ~ and $VARS for local paths. The folder must already exist, and personalclaw setup --app rsync-sync marks it as the sync root before the first sync. Leave empty to configure later — the transport stays idle until set."
}
},
"port": {
"type": "integer",
"default": 22,
"x-meta": {
"label": "SSH port",
"help": "Port for the ssh connection. Ignored when no host is set.",
"tags": [
"advanced"
]
}
},
"ssh_key": {
"type": "string",
"default": "",
"x-meta": {
"label": "SSH identity file",
"help": "Optional path to a private key to use for this host. Leave empty to let ssh pick from your agent and ~/.ssh/config. The key itself is never read by PersonalClaw — only handed to ssh by path.",
"tags": [
"advanced"
]
}
},
"staging_dir": {
"type": "string",
"default": "",
"x-meta": {
"label": "Local working directory",
"help": "Where the local mirror and staging trees live on this machine. Leave empty to keep them in PersonalClaw's home, under sync/rsync-sync. The mirror is what makes pulls incremental — rsync only transfers what changed.",
"tags": [
"advanced"
]
}
},
"timeout_secs": {
"type": "integer",
"default": 300,
"x-meta": {
"label": "Command timeout",
"help": "Maximum seconds any single rsync invocation may run before it is killed and the cycle reports a retryable failure. Prevents a hung transfer from wedging the sync job.",
"tags": [
"advanced"
]
}
}
}
}
}
}
- Scan verdict
- No scan on record before install
- Scan time
- No scan is published before install
- Blocking findings
- No scan is published before install
- Scanner version
- No scan is published before install
PersonalClaw publishes no scan of its own apps before you install one.
Every app is scanned again when you install it, whatever its listing says.
An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.
apps/app_manager.py at v0.3.9A dangerous scan verdict stops the install, and nothing overrides it.
A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.
apps/app_manager.py at v0.3.9Consent covers exactly what you reviewed, and an app that changed asks again.
The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.
apps/app_manager.py at v0.3.9A setting an app marks secret is kept in the credential store and never shown back.
The app's settings file holds only a reference, the value lives in the credential store, and every route that shows settings masks it. The app's own code receives the value when it runs.
apps/secret_fields.py at v0.3.9
PersonalClaw/PersonalClawApps @ 169cbc4f8fc5 · rsync-sync/app.json