Microsoft's PowerToys 0.103 preview lands with command-line Workspaces and a Command Palette overhaul
The first development preview of the 0.103 cycle pushes the release train forward while adding a Workspaces CLI and a reworked Command Palette dock.
Microsoft has published the very first PowerToys preview of its 0.103 development cycle, and it showed up before much of the community had finished working through the 0.102 feature release. The build is v0.103.3006.0, posted October 28 by Boliang Zhang, the person GitHub knows as LegendaryBlair and the project's lead maintainer.
It's a development preview from the main branch, which means it's aimed at testers, not everyone. Per Microsoft's own description, it contains "changes since" the v0.102.3001 hotfix and is "intended for testing ahead of the next stable release." Two headline features sit front and center: a command-line interface for Workspaces, and a dedicated flyout for browsing Command Palette extension pages.
Both are for the people PowerToys was built for in the first place. The tool has steadily pushed toward scriptability, and 0.102 already gave command-line control to Advanced Paste, Light Switch, Peek and PowerDisplay. Workspaces is just the newest module joining that group.
Workspaces gets a command line and Command Palette gets a new dock
Workspaces is the utility that snapshots which apps are open and where your windows sit across monitors, then restores that layout with one click. Until now you could only create, edit and launch it from the graphical interface. This preview closes that gap.
The new command line adds two operations. There's a read-only list command that enumerates saved workspaces by name or ID. Then there's a synchronous launch command that returns per-application results so a script can see what actually started, and what failed. Exit codes distinguish a full success (completed), partial progress (partial) and outright failure (failed), plus a few edge cases like persistence-verification hiccups.
Both emit JSON output, and that's the part that matters for automation. You can wire Workspaces into shell scripts, task schedulers or CI pipelines without building a parallel GUI automation layer on top.
The implementation is unusually fussy about process boundaries, which reads as a good sign. A single native execution core is shared between the GUI launcher and the new CLI shim, so list and launch behave identically no matter how you invoke them. Non-elevated callers run in their own process. Only elevated callers spin up a verified "Medium host" process and hand results back over a private named pipe. Each launched application gets its own console, so firing a workspace from inside a shell doesn't hijack your terminal.
Microsoft was pointed about privacy here. There is exactly one telemetry event, Workspaces_CLICommand, and it captures nothing sensitive: no workspace names, IDs, paths, arguments or error text.
The review cycle was grueling. Over about three weeks, GitHub Copilot's automated reviewer flagged several high-severity issues, including a console type-ahead race that could accept stale approval input and a risk of stale metadata overwriting live GUI edits. The author addressed each with targeted commits, and reportedly passed 34 of 34 UI tests across Windows 10 x64, Windows 11 x64 and Windows 11 ARM64. It deliberately skips capture/create/CRUD operations, sticking to list and launch only, which is a real limitation if you wanted full scriptable control of the feature.
The second story lives in Command Palette, the module that moves fastest. The biggest single contribution here is PR #51092, a dedicated dock flyout for browsing extension pages. Mike Griese (zadjii-msft) authored it, and at 77 commits it dwarfed everything else in this preview. It's Part 4 of a larger dock refactor spanning issue #45861.
Griese was candid about the process. He'd started the refactor when the dock first shipped, found it too large to finish early on, and leaned on AI to help "bring it over the finish line." The result gives extension pages their own navigation, search, details pane and command controls, routed through a shared page-owner abstraction instead of reusing the generic context-menu control.
Also landing in Command Palette is PR #51470, which adds Mica and Mica Alt materials to the dock. The main window already supported Mica, but the dock, usually unfocused, only had Acrylic and Transparent. The new code renders Mica and Mica Alt with live switching, independent of the main window's choice, and falls back to Acrylic then Transparent on systems that don't support Mica.
There was a genuine technical snag during review: zadjii had earlier found that Mica "disables itself and becomes opaque" once Command Palette loses focus, which would have made it useless in a dock that's rarely focused. Contributor Denis Mahmutovic (iamDeenko) found the workaround, the dock keeps IsInputActive = true even when another window takes focus, so Mica stays correct. zadjii's verdict captured the relief: "Well, I love it. Glad to see that this Just Works! Thanks for the contribution."
One more Command Palette change is worth flagging. PR #51598 adds an option to launch Command Palette with the Windows key alone, inspired by Raycast's behavior and closing the long-pending issue literally titled "Replace windows start menu with command palette." It's off by default, and you'd need to set the environment variable CMDPAL_ENABLE_WIN_HOTKEY=1 before launching, then enable the option in settings. Grabbing the Windows key globally can collide with the OS start menu, so the deliberate friction makes sense.
Fixes, housekeeping and what makes this different
Beyond the headline features, there's a fix for a hang that has annoyed users for a while. PR #51433 addresses PowerToys remaining running after you quit. The root cause was that module shutdown wasn't fully completed before runtime teardown. It's a welcome correction for anyone who's spotted the tray icon gone but the process still alive in Task Manager.
The preview also bundles smaller polish. Performance Monitor history was running at double speed in some cases, command invocation could get stuck after an extension stopped, and search ranking favored matching extension names over relevant apps. There's a policy change too: PR #51457 now requires human-written PR descriptions, confining AI-generated summaries to labeled, collapsed sections. On an open-source project that leans heavily on automated tooling, that's a clear stance on authorship.
Mouse Without Borders (#51041) got pairing and reconnect improvements, plus a guard so older settings snapshots don't clobber newer ones. Settings (#50738) improved persisted collection handling to cut the chance of corrupted saved data.
Here's the thing that separates this build from an ordinary preview. Two pull requests did most of the structural heavy lifting. PR #51603 advanced the main-branch release train to 0.103. PR #51582 standardized preview tagging on three-component tags, which is why the release page reads v0.103.3006 even though the installers still carry the four-part version 0.103.3006.0.
Because it's a preview-channel build, it only reaches users who opt in through the Preview update channel or install manually from GitHub. That's by design. The release notes are also unusually transparent about branch differences: PowerDisplay's "Copy monitor diagnostics" feature shows up here even though stable removed it, and Microsoft flags it explicitly as a branch difference rather than a new feature. Seven "baseline-only" commits should not be read as confirmed feature removals, per the release owner.
For context, the 0.102 milestone this preview sits on top of was itself a big one. Mouse Button Lock, CursorHide, a quick-access shelf for Command Palette, snip dictation in ZoomIt and the WinUI 3 migration of Color Picker and Text Extractor all shipped there. Microsoft's own announcement credited a large roster of community contributors, which is the whole point of the open-development model.
It's also worth remembering that PowerToys itself has a long, somewhat unusual history. The original PowerToys shipped in 1996 for Windows 95, offering Tweak UI and Quick Res, before disappearing entirely through the Vista to Windows 8 generations. Microsoft relaunched it as open source in 2019, and a build that's mostly about plumbing and version numbers is about as on-brand for the project as it gets.
Reaction to this specific preview has been muted, which is normal for a prerelease aimed at insiders. The dev blog comment section on the 0.102 post even ran a skeptic who wrote, "It still doesn't convince me to install PowerToys." But the thumbs-up and rocket reactions on this release show the preview is doing its job for the community that lives in these PRs.
Head here to the GitHub release page for more information.
