What changed
Kimi Work 3.2.27 adds background execution with forks and side chats, Intel Mac support, desktop-pet file handoff and shared plugins across Work and Chat. It also prevents projects from being stored inside the application directory, where update cleanup could delete them, and fixes case-only Windows path merging.
Why it matters
Background work removes a foreground bottleneck but creates parallel state, notification and cancellation paths. The storage and Windows fixes also close concrete file-integrity hazards that matter more than the surrounding convenience features.
What to do
Upgrade a disposable workspace, place synthetic projects near the install directory, start a long task, fork a side chat, attach a file through the desktop pet and interrupt the app during an update rehearsal. Verify project location, case-sensitive paths, alerts, task state, plugin scope and recovery before rollout.
Caveat
The release notes are Moonshot vendor evidence, not an independent reliability or security assessment. Background-task isolation, cancellation semantics, plugin sharing and the full set of affected older versions are not documented, so retain backups and test the exact operating system build.