Files
openclaw-control-plane/sync/README.md
wangzhendong b5acead1e1 Add polling sync communication layer
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-15 11:11:18 +08:00

52 lines
1.2 KiB
Markdown

# Sync Layer
This is the MVP communication layer for PC and VPS agents.
It uses polling-based Git synchronization. Git is the durable source of truth and audit log, while these scripts reduce manual `pull` and `push` work.
## PC
Run from `D:\openclaw-control-plane`:
```powershell
.\sync\sync-agent.ps1
```
Run one cycle only:
```powershell
.\sync\sync-agent.ps1 -Once
```
## VPS
Run from `/home/ubuntu/openclaw-control-plane`:
```bash
bash sync/sync-agent.sh
```
Run one cycle only:
```bash
bash sync/sync-agent.sh --once
```
## Rules
- Scripts only stage known control-plane paths.
- Agents should avoid editing the same file concurrently.
- `AGENT_BOARD.md` is owned by ORCHESTRATOR.
- Each role owns its own `handoff/*.md` file.
- Evidence files should be append-only by unique filename.
- On conflict or sync failure, stop the script and resolve manually.
## Future Upgrade
This polling layer should be replaced or supplemented when conditions are mature:
- Gitea webhook triggers for pull notifications.
- Gitea Issues as the task queue.
- OpenClaw Gateway events for cross-device command triggers.
- Cursor SDK based coordinator for creating, resuming, and supervising agents.