synclisted
Install: claude install-skill x-mesh/xm
<Purpose>
Sync .xm/ project state (traces, plans, build data) across multiple machines via a lightweight Bun HTTP server backed by SQLite.
</Purpose>
<Use_When>
- User says "sync", "push", "pull", "sync server", "동기화"
- User wants to share .xm/ state between machines
- User wants to start/stop the sync server
</Use_When>
<Do_Not_Use_When>
- Git push/pull (use git directly)
- File sync unrelated to .xm/ state (use rsync, etc.)
</Do_Not_Use_When>
# x-sync — Multi-Machine .xm/ Sync
Syncs .xm/ project state across machines. Server stores data in SQLite; clients push/pull via HTTP.
Pull is incremental by a monotonic server **cursor** (id), so same-millisecond pushes never get skipped. Push sends a **full snapshot**, so the server propagates local deletions as tombstones — clients then remove only the machine-namespaced copies they pulled earlier (never your local working files).
## Model Routing
| Subcommand | Model | Reason |
|------------|-------|--------|
| `status`, `server status` | **haiku** (Agent tool) | Read-only check |
| `push`, `pull`, `push-all`, `pull-all` | **haiku** (Agent tool) | Script execution, no reasoning |
| `server start`, `server stop` | **haiku** (Agent tool) | Simple process management |
| `setup` (interactive) | **sonnet** | Requires AskUserQuestion |
## CLI Invocation
> **⚠ Call `xm sync <command>` directly. Claude Code's Bash tool starts a fresh shell on every invocation — shell functions (`xms()`) defined in one call do NOT persist to the ne