What makes workbuddy-multi-machine-sync notable?

2.6K downloads. Trust evidence available

How should workbuddy-multi-machine-sync be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

workbuddy-multi-machine-sync

Set up WorkBuddy config sync across 3+ Macs with machine naming, conflict resolution, and status tracking. Supports GitHub or iCloud as backend. Triggers: 多机同步, 三台电脑同步, 多台 Mac 同步 WorkBuddy, multi-machine sync, 3+ devices sync, 多台电脑配置同步, team sync WorkBuddy. Includes machine registry, per-machine commit tagging, stale lock detection, and a status command to see which machines are active.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.6k

Updated

Oct 9, 2026

Version

0.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.6K downloadsadoption · observed Oct 9, 2026
Latest release: 0.1.0release · observed Aug 1, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s177t5gz1g9bqr9wzdn3k301nh8bn7wz:workbuddy-multi-machine-sync

Install using `clawhub skill install s177t5gz1g9bqr9wzdn3k301nh8bn7wz:workbuddy-multi-machine-sync` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/lyy4916/workbuddy-multi-machine-sync before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-lyy4916-workbuddy-multi-machine-sync/snapshot"

Documentation

CLAWHUB

18,826 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: workbuddy-multi-machine-sync
description: "Set up WorkBuddy config sync across 3+ Macs with machine naming, conflict resolution, and status tracking. Supports GitHub or iCloud as backend. Triggers: 多机同步, 三台电脑同步, 多台 Mac 同步 WorkBuddy, multi-machine sync, 3+ devices sync, 多台电脑配置同步, team sync WorkBuddy. Includes machine registry, per-machine commit tagging, stale lock detection, and a status command to see which machines are active."
agent_created: true
---

# WorkBuddy Multi-Machine Sync (3+ Devices)

## Overview

Extend WorkBuddy config sync to **three or more Macs**. Built on top of the
two-machine sync skill, this adds:

- **Machine naming** — each Mac gets a human-readable label (e.g. `studio`,
  `laptop`, `office`) for easy identification in commit logs
- **Machine registry** — a `machines.json` file tracks all registered machines
  and their last-sync timestamps
- **Conflict-aware sync** — more aggressive rebase + auto-resolve strategy for
  the higher conflict probability with 3+ machines
- **Status command** — `wbstatus` shows which machines are registered, when
  they last synced, and which is currently active
- **Backend agnostic** — works with GitHub or iCloud

## When to Use This vs Two-Machine Sync

| Factor | Two-Machine Sync | Multi-Machine Sync |
|--------|------------------|---------------------|
| Machine count | 2 | 3+ |
| Machine naming | Not needed | Yes (human-readable labels) |
| Machine registry | Not needed | `machines.json` |
| Conflict probability | Low | Higher (more concurrent edits) |
| Status tracking | Manual | `wbstatus` command |
| Backend | GitHub or iCloud | GitHub or iCloud |

If you only have 2 machines, use `workbuddy-multi-device-sync` (simpler).
Upgrade to this skill when adding a 3rd machine.

## What Syncs vs What Doesn't

Same as the two-machine skill. Additionally:

### Syncs (new)
- `.machine-name` — this machine's label
- `machines.json` — registry of all machines

### Does NOT Sync (same as before)
- `binaries/`, `workbuddy.db`, `.mcp.json`, `sessions/`, `logs/`, `traces/`,
  `credentials/`, `memory/`, daemon state files

## Workflow

### Phase 1: Set Up Machine 1 (Primary)

Follow the two-machine skill (`workbuddy-multi-device-sync`) for Mac A setup,
then add multi-machine enhancements:

#### Step 1: Register Machine Name

```bash
# Set a human-readable name for this machine
echo "studio" > ~/.workbuddy/.machine-name
```

Choose short, descriptive names: `studio`, `laptop`, `office`, `home`, etc.

#### Step 2: Initialize Machine Registry

```bash
# Create machines.json with this machine registered
MACHINE_NAME=$(cat ~/.workbuddy/.machine-name)
HOSTNAME=$(hostname)
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")

cat > ~/.workbuddy/machines.json << EOF
{
  "machines": [
    {
      "name": "$MACHINE_NAME",
      "hostname": "$HOSTNAME",
      "registered": "$TIMESTAMP",
      "last_sync": "$TIMESTAMP",
      "status": "active"
    }
  ]
}
EOF
```

#### Step 3: Install Multi-Machine Auto-Sync

1. C

_meta.json

{
  "ownerId": "kn751pzj8jbknm4tygdecnwjzn8bmtyz",
  "slug": "workbuddy-multi-machine-sync",
  "version": "0.1.0",
  "publishedAt": 1785566310078
}

references/multi-machine-architecture.md

# Multi-Machine Sync Architecture

## Overview

Extends the two-machine sync to support 3+ Macs with machine naming,
registry tracking, and enhanced conflict handling.

## Architecture

```
                 GitHub / iCloud
                      ↕
    ┌─────────────────┼─────────────────┐
    ↓                 ↓                 ↓
 Machine A         Machine B         Machine C
 (studio)          (laptop)          (office)
    ↕                 ↕                 ↕
 auto-sync.sh     auto-sync.sh     auto-sync.sh
 (every 5 min)    (every 5 min)    (every 5 min)
    ↕                 ↕                 ↕
 machines.json ←──→ machines.json ←──→ machines.json
```

Each machine:
1. Pulls remote changes (rebase)
2. Updates its own entry in `machines.json` (last_sync timestamp)
3. Commits local changes (tagged with machine name)
4. Pushes to remote

## Machine Naming

Each machine has a `.machine-name` file containing a short label:
- `studio`, `laptop`, `office`, `home`, etc.
- Must be unique across all machines
- No spaces (use hyphens)

This name appears in:
- Git commit messages: `auto-sync 2026-08-01 12:30 from studio`
- `machines.json` registry
- `wbstatus` output

## Machine Registry (`machines.json`)

A shared JSON file (synced via git) that tracks all registered machines:

```json
{
  "machines": [
    {
      "name": "studio",
      "hostname": "pascalliu-mac-studio",
      "registered": "2026-08-01T00:00:00Z",
      "last_sync": "2026-08-01T12:30:15Z",
      "status": "active"
    }
  ]
}
```

Each machine updates ONLY its own entry. Stale/offline status is computed
dynamically based on `last_sync` age:
- **active**: < 30 minutes since last sync
- **stale**: 30 min - 24 hours
- **offline**: > 24 hours

## Conflict Handling

With 3+ machines, the probability of concurrent edits increases.

### Auto-Sync Conflict Strategy

1. `git pull --rebase` — replay local commits on top of remote
2. If rebase fails (same file modified):
   - `git rebase --abort`
   - `git stash` — save local changes
   - `git pull` — accept remote (no rebase)
   - `git stash pop` — attempt to reapply local changes
   - If stash pop fails: keep remote, log to `.sync-conflicts.log`
3. Conflicts are logged (not silently lost) for manual review

### When to Resolve Manually

```bash
cd ~/.workbuddy
git status                    # see conflicts
# edit files...
git add -A
git rebase --continue
git push origin main
```

Check conflict log:
```bash
cat ~/.workbuddy/.sync-conflicts.log
```

## Status Command (`wbstatus`)

Run `wbstatus` in terminal to see:

```
  WorkBuddy Multi-Machine Sync Status
  ====================================
  This machine: studio (pascalliu-mac-studio)
  Daemon: RUNNING (PID 10034)
  Last sync: [2026-08-01 12:30:15] synced (studio)
  Conflicts: none

  Machine    Hostname               Status   Last Sync
  ----------------------------------------------------------
  laptop     pascalliu-mbp          active   2026-08-01 12:28 UTC
  office     pascalliu-imac

skill-card.md

## Description:

Set up WorkBuddy configuration sync across three or more Macs with machine naming, conflict handling, registry tracking, and status reporting for GitHub or iCloud-backed sync.

This skill is ready for commercial/non-commercial use.

## Publisher:

[lyy4916](https://clawhub.ai/user/lyy4916)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and WorkBuddy users use this skill to configure multi-machine synchronization for three or more Macs. It helps register machine names, install sync scripts, maintain a shared machine registry, and inspect sync status.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The setup flow can run remotely sourced shell commands during installation.

Mitigation: Inspect and pin setup scripts before execution; avoid piping remote content directly into a shell.

Risk: GitHub token handling can expose credentials if plaintext git credential storage is used.

Mitigation: Prefer SSH or an operating-system keychain credential helper; avoid embedding live tokens in setup scripts.

Risk: Anyone with write access to the sync repository can affect code and configuration that run on every synced machine.

Mitigation: Limit repository write access, review changes before sync, and keep backups of ~/.workbuddy before installation.

Risk: Automatic conflict handling can keep remote changes and may lose local edits.

Mitigation: Review conflict logs and resolve important conflicts manually instead of relying on automatic remote-wins resolution.

## Reference(s):

- [Server-resolved source repository](https://github.com/lyy4916/workbuddy-multi-machine-sync)
- [ClawHub skill page](https://clawhub.ai/lyy4916/skills/workbuddy-multi-machine-sync)
- [Multi-Machine Sync Architecture](references/multi-machine-architecture.md)
- [Gitignore Template](references/gitignore-template)

## Skill Output:

**Output Type(s):** [guidance, markdown, shell commands, configuration, code]

**Output Format:** [Markdown guidance with inline shell commands and script templates]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces setup steps, sync commands, status checks, and configuration file guidance for local WorkBuddy sync.]

## Skill Version(s):

0.1.0 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 4h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.