dsh-agent-sync

✨ Features

📸 Screenshots

MCP/Skills 管理	MCP/Skills 同步	添加技能

🚀 Quick start

Prerequisites

• A running DSH (desktop or headless) with Node.js ≥ 22.5
• The agents you want to sync must be installed on the same machine (nothing is shipped with the plugin)

Install

Option A — as a profile bundle (recommended)

Add dsh-agent-sync to your profile's dsh.profile.bundles and install it:

cd "$DSH_HOME/profiles/<name>"
pnpm add dsh-agent-sync        # or: pnpm add github:kuaiyukuaikuai/dsh-agent-sync

Restart DSH. The bundled cordis.patch.yml mounts the plugin automatically.

Option B — manual row

Place the package where your profile can resolve it, then append to
$DSH_HOME/profiles/<name>/cordis.patch.yml:

- insert:
    - id: dsh-agent-sync
      name: 'dsh-agent-sync'

Restart DSH.

📖 Usage

GUI panel

Settings → MCP/Skills (main page MCP/Skills 管理)

• Manage (main page) — a centered MCP / Skills switch; card grid where each card has a toggle switch (enable/disable in one control) and a remove button with a 3-second inline confirm; disabled items are greyed with a badge. Skills are grouped by scope: global (~/.dsh/skills) and per-workspace (<workspace>/.dsh/skills) with workspace tabs + a search box + skill-group filter chips.
• Toolbar (right of the switch) — ⇄ 迁移技能 (migrate/copy skills between scopes) and ＋ 添加 MCP / ＋ 添加 Skill (manual add).
• MCP/Skills同步 → — a button that opens the sync page: per-source tabs (common agents + "More ▾"), select-all, sync buttons (choose global or a workspace as the skill target), custom sources.
• ＋ 添加 Skill dialog — pick a folder (bundle), a single .md, or a .zip — or drag & drop any of those onto the dialog; choose the target scope (global / workspace).
• ⚙️ 设置 dialog — Skill 同步方式 (copy / link=junction) and MCP 同步目标 (all / desktop / web profiles).

UI implementation — no component library. The panel is vanilla React (React.createElement) styled with DSH's theme tokens (--dsw-alias-*), capsule tabs/buttons, and a small custom CSS toggle switch.

Model tools

agent_sync_scan        # list what can be synced (env values are hidden, keys only)
agent_sync_do          # mcp/skills: ["all"] or names; scope: global or a workspace path
agent_sync_config      # get/set { skillSyncMode: copy|link, syncProfiles: all|desktop|web }
agent_sync_add_skill   # add a skill from a local directory (SKILL.md) or .md file, scope optional
agent_sync_toggle      # enable/disable a synced mcp/skill ({type, name, enabled})
agent_sync_status      # current DSH-side state + sync bookkeeping (incl. disabled items)
agent_sync_remove      # remove a synced mcp/skill
agent_sync_sources     # manage custom sources (list / add / delete)

📦 Supported agents

All paths are home-relative → works on any machine where those agents are installed
(Windows / macOS / Linux). Configs in JSON, YAML-ish, and TOML shapes are parsed.

🔧 How it works

other agents' configs ──► scan ──► sync ──► DSH
  ~/.codex/...                     │
  ~/.claude.json                   ├─ MCP   → profiles/*/cordis.patch.yml (dsh-mcp-client rows)
  ~/.cc-switch/cc-switch.db        │
  ~/.workbuddy/.mcp.json           └─ Skills → $DSH_HOME/skills/<name>/SKILL.md
  ...

• MCP is written into each profile's cordis.patch.yml (a managed # --- dsh-agent-sync managed --- section, repaired if the file was invalid). The desktop GUI shell composes once at boot, so MCP activates on the next DSH restart; the dsh CLI / headless boot hot-applies profile patches via HMR.
• Skills are copied (default) or linked via junction (skillSyncMode: link) into $DSH_HOME/skills (global) or <workspace>/.dsh/skills (per-workspace), and discovered by sessions whose agent preset mounts the skill-filesystem provider. In link mode, disabling a skill removes the junction (never touches the source); enabling recreates it.

⚠️ Security notes

• Syncing MCP copies env values verbatim (DB passwords, API keys, …) into cordis.patch.yml and $DSH_HOME/agent-sync/state.json — same plaintext exposure as the source configs already have.
• Scan output only lists env key names, never values.
• Treat state.json / patch files as secrets; consider a token with an expiry and prefer environment-variable references where possible.

❓ FAQ

Why don't I see any MCP/Skills?
Nothing is installed on the machine yet, or that agent stores its config elsewhere. The custom source lets you point at any JSON/TOML/skills directory.

Do I need to restart DSH after syncing MCP?
Yes — the desktop GUI shell composes its profile once at boot. The dsh CLI/headless path hot-applies profile patches.

Can I remove something?
Yes — the GUI's MCP/Skills 管理 page has remove buttons (with a 3-second inline confirm), or use agent_sync_remove.

🧑‍💻 Development

pnpm install
pnpm test          # node --test

index.mjs        Host plugin: scanners, sync, HTTP routes (in-process, Node built-ins only)
client.js        Browser panel (lazy-CJS, zero build) — registers Settings → MCP/Skills同步
cordis.patch.yml Bundle patch that mounts the plugin row
plugin-market.json  DSH plugin market submission entry

🛒 DSH Plugin Market

Listed in the awesome-dsh-plugin community curated list — find it in DSH → Settings → Plugin Market, on awesome-dsh-plugin.com, or install directly:

dsh plugin --profile web add github:kuaiyukuaikuai/dsh-agent-sync

📄 License

MIT