[Feature Request] ZCode: Cloud sync for config, skills, plugins and settings across machines

Feature Request: Cloud Sync for ZCode Configuration

Add cloud synchronization so users can sync settings, skills, plugins, subagent configs, model providers across multiple machines.

---

Problem

When installing ZCode on new machine:

• Must manually reconfigure everything
• Skills must be reinstalled/recreated
• Plugins must be reconfigured
• Model provider API keys re-entered
• Subagent settings recreated from scratch

"I got tired of constantly duplicating my settings on two machines manually." — DCCCXIX

---

What Should Be Synced:

• Skills (custom skills created/imported)
• Plugins (installed + plugin settings)
• Subagent configurations
• Model providers (API keys, endpoints, settings)
• App preferences (theme, editor, keybindings, layout)
• Memory/context settings
• Custom prompts/templates

---

Proposed Solutions

Option A: Full Cloud Sync (Recommended)

Automatic sync via Z.ai account:

• Background auto-sync
• Conflict resolution (merge or choose)
• Device management (see all synced devices)
• E2E encryption for API keys
• Selective sync per category
• Sync history / rollback

Option B: Manual Export/Import (Simpler)

Settings menu with Export/Import:

• Export all to file (.zcode-config)
• Import with merge or replace options
• Good for offline backup

Option C: Hybrid (Best UX)

• Primary: Cloud auto-sync
• Fallback: Export/import file for backup

---

Security Considerations

Data Type	Requirement
API Keys	E2E encrypted, decrypt on device only
Auth tokens	OAuth refresh, not plain text
Settings	Encrypted at rest

---

User Benefits

• Time savings - no more hours of manual setup
• Consistency - same experience across machines
• Backup safety - settings in cloud
• Multi-device - seamless work/home switching
• Migration - easy OS/machine upgrades

Competitors have this: VS Code Settings Sync, JetBrains Sync, Cursor Sync

---

Implementation Phases

1. Phase 1 (MVP): Export/Import to file
2. Phase 2: Basic cloud sync with Z.ai account
3. Phase 3: Advanced - multi-device dashboard, team sharing, rollback

---

Reporter Info

• Source: Discord
• Reporter: DCCCXIX (OP)
• Timestamp: 1:29 PM

---

Priority: Medium-High

• User Demand: High (common pain point)
• Competitive necessity (VS Code, Cursor, JetBrains all have this)
• Retention value: High (locks users into ecosystem)

Labels Suggested:

feature-request, zcode, cloud-sync, settings, multi-device, backup

---

Submitted by:
Regards,
Roman (Discord: bignavi_x)

• Z.ai Volunteer Ambassador
• Tech resources channel: https://t.me/VibeCodePrompterSystem
• Tech Blog: http://claw.rommark.dev/blog

No repository files, tests, or entry points are identified. Start by narrowing the proposal to one implementation phase and defining its scope, security requirements, conflict behavior, and completion criteria before locating the affected code.