Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk

What this means for teams

Teams can now plan around:

browser delivery with retained client versions
installable desktop packaging
stronger release identity through versioned build outputs

Usage references

Installation
Local setup

Build example

npm run build:client
npm run build:desktop

Screenshot

MdWrk home surface that introduces the packaged client experience

Why this milestone matters

Deployment flexibility matters for teams that want browser-first use, desktop packaging, or self-managed hosting. April 12 shows MdWrk growing into a platform that can support all three with one codebase.

Frequently Asked Questions

What does this MdWrk update cover?

MdWrk introduces retained client version delivery and a desktop shell track, giving teams more control over rollout pacing, install shape, and long-lived workspace adoption.

What should readers take away from this update?

This article explains the MdWrk product change, the workflow it affects, and where readers can continue in the related documentation.