The problem
I use QoderWork on two Macs — a MacBook Pro at the office and a Mac Studio at home — signed into the same account. Task history, however, does not follow the account. The Quick Start doc states it explicitly: “历史任务保存在本地设备，不会跨设备同步” (historical tasks are saved locally and never sync across devices).
The result is a fragmented experience: half of my task history lives on each machine, the awareness/memory each instance builds up is separate, and I cannot start a task at the office and pick it up at home — I can’t even check a task’s status remotely. For a personal office agent, cross-device continuity is not a nice-to-have; it is the core promise.
Why this matters
Assistant-native apps have already set the expectation that history is account-level: Claude (desktop/web/mobile) syncs conversations, OpenAI Codex runs tasks in the cloud where any entry point can view and resume them, and Kimi syncs sessions across its app and web versions. In this exact category, Tencent’s WorkBuddy has also just shipped multi-device sync for tasks and deliverables (per public reports). QoderWork’s local-first storage is a legitimate differentiator — privacy, speed, no cloud dependency — but as the only option it makes multi-machine users feel like second-class users.
Suggested solution (tiered)
- Minimum viable: opt-in account-level sync of the task list + conversation history, so any device can view and search past tasks and their summaries.
- Full sync: make a task session resumable from another device — context, awareness memory, and workspace metadata travel with the account; deliverables either live in an optional cloud workspace or hand off cleanly between local folders.
- Keep local-first as a choice: sync should be opt-in per device with a clear indicator of what is synced, so users who want purely local operation lose nothing.
Workarounds I’m using today (for context): Markdown export of conversations + manual copy, pointing the workspace folder at a synced drive so deliverables flow between machines, and an IM channel to send jobs to my always-on Mac Studio remotely. They work, but they’re duct tape around the #1 friction point in an otherwise excellent product.
Environment: QoderWork CN 0.9.17, macOS (Apple Silicon).