sync

name	sync
description	Sync agent files between local and remote server. Use when the user says "sync", "push to remote", "pull from remote", "sync agent", or runs /sync.

Remote Sync

Bidirectional rsync between local agent and remote deployment. Connection details are read from bridgey-deploy.config.json in the agent's root directory. This applies to both deployment models — it syncs the persona workspace files regardless of whether the container runs a Tier-A Channels session or a Tier-B daemon.

Setup

Read bridgey-deploy.config.json to get:

• tailscale_host — the Tailscale hostname of the remote server
• remote_path — the path on the remote server (e.g., /opt/bridgey/personas/{name})
• container_name — the Docker container name

If bridgey-deploy.config.json doesn't exist, ask the user for the Tailscale hostname and remote path.

Usage

• /sync push — local -> remote (config, skills, CLAUDE.md changes)
• /sync pull — remote -> local (memory, outputs, learnings)
• /sync — bidirectional (push then pull)

Commands

Push (local -> remote)

Push local config/skills/rules to the remote server. Excludes runtime data.

rsync -avz --delete \
  --exclude='.git/' \
  --exclude='.mcp.json' \
  --exclude='*.log' \
  --exclude='*.db' \
  --exclude='*.db-journal' \
  --exclude='user/memory/' \
  ~/.personas/{name}/ {tailscale_host}:{remote_path}/

After pushing, restart the container to pick up changes:

ssh {tailscale_host} "cd /opt/bridgey && docker compose restart {container_name}"

Pull (remote -> local)

Pull memory and outputs from the remote server. Only syncs user/memory/.

rsync -avz \
  {tailscale_host}:{remote_path}/user/memory/ \
  ~/.personas/{name}/user/memory/

Bidirectional

Run push then pull in sequence.

Important

• .mcp.json is NEVER synced (contains API keys, differs per environment)
• .git/ is never synced
• Push excludes user/memory/ (remote writes there, local pulls it)
• After push, container restart is needed for the agent to see changes