What makes workbuddy-multi-device-sync notable?

2.6K downloads. Trust evidence available

How should workbuddy-multi-device-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-device-sync

Set up automatic configuration sync across multiple Macs using WorkBuddy. Use when the user wants to use WorkBuddy on two or more computers and keep identity, memory, skills, and settings synchronized. Triggers: 多台电脑同步, 双机同步, 两台 Mac 同步 WorkBuddy, sync WorkBuddy across devices, multi-device sync, 换电脑配置同步. Covers Git-based sync via GitHub, auto-sync daemon, and one-click setup for additional machines.

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: medium.

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

Install using `clawhub skill install s177t5gz1g9bqr9wzdn3k301nh8bn7wz:workbuddy-multi-device-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-device-sync before using production credentials.

Contract: missing

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

Documentation

CLAWHUB

16,809 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: workbuddy-multi-device-sync
description: "Set up automatic configuration sync across multiple Macs using WorkBuddy. Use when the user wants to use WorkBuddy on two or more computers and keep identity, memory, skills, and settings synchronized. Triggers: 多台电脑同步, 双机同步, 两台 Mac 同步 WorkBuddy, sync WorkBuddy across devices, multi-device sync, 换电脑配置同步. Covers Git-based sync via GitHub, auto-sync daemon, and one-click setup for additional machines."
agent_created: true
---

# WorkBuddy Multi-Device Sync

## Overview

Enable automatic synchronization of WorkBuddy configuration across multiple Macs
using a private GitHub repository. After setup, all machines share the same
identity (SOUL.md, IDENTITY.md, USER.md), memory (MEMORY.md), skills, and
settings — with zero manual commands. A background daemon syncs every 5 minutes.

## What Syncs vs What Doesn't

### Syncs (via Git)
- Identity files: `SOUL.md`, `IDENTITY.md`, `USER.md`
- Memory: `MEMORY.md` (user-level, NOT `memory/` daily logs)
- Skills: `skills/` directory
- Config: `mcp.json`, `settings.json`
- Setup scripts: `auto-sync.sh`, `start-sync-daemon.sh`, `wb-setup-mac-b.sh`

### Does NOT Sync (machine-specific)
- `binaries/` — 300MB+ platform-specific runtimes, each machine installs its own
- `workbuddy.db` — SQLite database (automations, runtime state), concurrent sync corrupts it
- `.mcp.json` — localhost port numbers differ per machine
- `sessions/`, `logs/`, `traces/` — runtime data, machine-specific
- `credentials/` — each machine logs in independently
- `memory/` — daily work logs, project-specific
- `connectors/`, `plugins/` — marketplace state, machine-specific

### Already Synced (server-side, no action needed)
- Conversation history
- Cloud user profile (auto-injected at session start)

## Workflow

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

#### Step 1: Initialize Git in `~/.workbuddy/`

```bash
# Set git config if not already set
git config --global user.name "$(whoami)"
git config --global user.email "$(whoami)@workbuddy.local"
git config --global init.defaultBranch main

# Initialize repo
cd ~/.workbuddy
git init
```

#### Step 2: Create `.gitignore`

Copy the template from `references/gitignore-template` to `~/.workbuddy/.gitignore`.
This excludes all machine-specific files. Review and adjust as needed.

Key exclusions:
- `binaries/` — runtimes
- `workbuddy.db` / `workbuddy.db-*` — SQLite
- `.mcp.json` — localhost ports
- `sessions/`, `logs/`, `traces/` — runtime data
- `credentials/` — auth tokens
- `memory/` — daily logs
- `.auto-sync.log`, `.sync-daemon.pid` — daemon state

#### Step 3: Create GitHub Private Repo

Two approaches:

**Approach A: GitHub Device Flow (recommended, no SSH needed)**

1. Initiate device flow to get a verification code:
```bash
curl -s -X POST "https://github.com/login/device/code" \
  -H "Accept: application/json" \
  -d "client_id=178c6fc778ccc68e1d6a&scope=repo,admin:public_key"
```
Response contains `device_code`, `user_code`, and `verifica

_meta.json

{
  "ownerId": "kn751pzj8jbknm4tygdecnwjzn8bmtyz",
  "slug": "workbuddy-multi-device-sync",
  "version": "0.1.0",
  "publishedAt": 1785566323024
}

references/sync-architecture.md

# Sync Architecture & Troubleshooting

## Three-Layer Data Model

WorkBuddy data in `~/.workbuddy/` falls into three categories:

### Layer 1: Server-Side Synced (automatic, no action needed)
- Conversation history — searchable across devices
- Cloud user profile — auto-injected at session start

### Layer 2: Git-Synced (this skill handles)
- `SOUL.md`, `IDENTITY.md`, `USER.md` — agent identity
- `MEMORY.md` — cross-project user memory
- `mcp.json` — MCP server config (NOT `.mcp.json`)
- `settings.json` — WorkBuddy settings
- `skills/` — installed skills
- `wb-setup-mac-b.sh` — Mac B setup script (stored in repo for easy download)

### Layer 3: Machine-Local (never synced)
- `binaries/` — 300MB+ runtimes, platform-specific
- `workbuddy.db` — SQLite, automations + runtime state (concurrent access corrupts)
- `.mcp.json` — localhost port mappings, differ per machine
- `sessions/`, `logs/`, `traces/` — ephemeral runtime data
- `credentials/` — auth tokens, each machine independent
- `memory/` — daily work logs, project-specific

## Sync Flow

```
Mac A changes → git commit → git push → GitHub repo
                                          ↓
Mac B ← git pull ← git rebase ← auto-sync daemon (every 5 min)
```

## Daemon Architecture

The sync daemon uses Python's `subprocess.Popen` with `start_new_session=True`
to create a truly detached process that survives terminal close.

```
.bash_profile → start-sync-daemon.sh → Python subprocess → bash loop
                                                      ↓
                                              auto-sync.sh (every 300s)
                                                      ↓
                                              git pull → commit → push
```

### Why not LaunchAgent?
On macOS 12+, `launchctl load` frequently fails with "Input/output error" under
sandbox restrictions. The Python daemon approach is more reliable and doesn't
require elevated permissions.

### Recovery After Reboot
The daemon dies on reboot but auto-restarts when:
1. User opens Terminal (`.bash_profile` calls `start-sync-daemon.sh`)
2. WorkBuddy executes any bash command (triggers `.bash_profile`)

## Common Issues

### GitHub SSH port 22 blocked
**Symptom**: `ssh -T [email protected]` hangs or times out
**Fix**: Use HTTPS + token instead of SSH
```bash
git remote set-url origin https://github.com/<user>/wb-sync.git
```

### Token expired or revoked
**Symptom**: `git push` returns 403 Forbidden
**Fix**: Generate new token at https://github.com/settings/tokens/new
```bash
echo "https://<user>:<new_token>@github.com" > ~/.git-credentials
```

### Merge conflicts during auto-sync
**Symptom**: `git pull --rebase` fails, daemon stops syncing
**Fix**: Manually resolve and push
```bash
cd ~/.workbuddy
git status              # see conflicted files
# resolve conflicts...
git add -A
git rebase --continue
git push origin main
```

### Daemon not running
**Check**:
```bash
cat ~/.workbuddy/.sync-daemon.pid
kill -0 $(cat ~/.workbuddy/.sync-daem

skill-card.md

## Description:

Sets up Git-based synchronization of WorkBuddy identity, memory, skills, scripts, and settings across multiple Macs.

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 keep WorkBuddy configuration consistent across two or more Macs. It provides setup guidance, sync scripts, a Git ignore template, and troubleshooting material for private-repository synchronization.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: A private GitHub repository becomes the control point for WorkBuddy identity, memory, skills, and settings.

Mitigation: Use a private repository, review exactly which files are synced, keep machine-specific and credential files excluded, and restrict repository access.

Risk: The skill uses persistent automatic syncing and shell scripts that can repeatedly pull, commit, and push local agent state.

Mitigation: Inspect the scripts before enabling the daemon, review sync logs and repository history, and confirm how to stop or disable the daemon.

Risk: Setup flows can involve plaintext GitHub credential storage and remote shell execution patterns.

Mitigation: Use a fine-grained short-lived token, avoid piping remote scripts directly to bash, and prefer running an inspected local copy of setup scripts.

## Reference(s):

- [Server-resolved GitHub provenance](https://github.com/lyy4916/workbuddy-multi-device-sync)
- [ClawHub skill page](https://clawhub.ai/lyy4916/skills/workbuddy-multi-device-sync)
- [Sync Architecture & Troubleshooting](references/sync-architecture.md)
- [Gitignore Template](references/gitignore-template)

## Skill Output:

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

**Output Format:** [Markdown guidance with bash command blocks and script/configuration file content]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Requires user-supplied GitHub account, repository, and token values for setup.]

## 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 2h 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.