Dave Plummer, the original developer of Windows Task Manager, is building a lookalike utility for macOS—but his plan to release it through the Mac App Store has hit a wall. Apple’s App Sandbox rules, mandatory for App Store distribution, explicitly prohibit an app from terminating other processes, which is the one function every Task Manager user expects to work.

Plummer, who created the iconic Windows XP-era Task Manager as a side project that Microsoft eventually shipped with the OS, has been sharing development updates for a Mac version written from scratch in Swift. As first reported by Club386 on July 30, 2026, the prototype already mirrors Windows 11’s Task Manager with per-core CPU activity graphs and 60 Hz system sampling. The project immediately attracted attention from Windows power users who split time between platforms, as Apple’s built-in Activity Monitor, while capable, lacks the densely packed performance dashboard and startup-service controls many have relied on for decades.

But enthusiasm cooled when Plummer discovered that a fully functional Task Manager can’t legally land in the App Store. The conflict is simple: sandboxed apps are forbidden from calling terminate() on other processes, which neuters the utility’s raison d’être. Plummer had considered a free beta release through the store for convenience; instead, he now faces the choice of distributing outside Apple’s walled garden or stripping his tool of its most basic capability.

What Plummer is Actually Building

The project is not a port of Windows code. Although Microsoft supplied Plummer with the original XP Task Manager source and permission to demonstrate it on his YouTube channel, the Mac tool is a fresh Swift application. Club386 shared screenshots showing a window that closely tracks the Windows 11 design language: a left navigation rail for Processes, Performance, App History, Startup, and Services tabs, and a right pane with live charts. Early visuals confirm per-core CPU graphing—a detail Activity Monitor buries under a single composite view—and Plummer noted he’s sampling system statistics at 60 Hz, though he may throttle to 30 Hz or 15 Hz for stability.

The prototype doesn’t just duplicate Windows chrome; it reimagines Task Manager’s data density for a Mac audience that often uses only Apple’s lightweight Activity Monitor. Activity Monitor provides similar process-level inspection, memory pressure, and energy impact, but it lacks a comprehensive GPU utilization graph, integrated startup program management, and the kind of at-a-glance service oversight Windows users take for granted. Plummer’s tool, should it ship, would wrap those features in a familiar interface that reduces the learning curve for anyone who administers both Windows and macOS machines.

The App Store’s Sandbox: A Hard Stop

The technical hurdle is unequivocal. Apple’s App Sandbox, required for all apps distributed through the Mac App Store, explicitly omits the ability to interact with other processes in ways that would allow termination. The entitlement com.apple.security.temporary-exception.process-info can grant read-only access to process information, but there is no carve-out for sending a kill signal. Apple’s documentation confirms that sandboxed apps “cannot send events to other apps, post keyboard events, or otherwise control other apps”—the exact behavior a Task Manager replacement needs.

For Plummer, this means a straight-to-App-Store route is impossible unless he cripples the tool. Removing the “End Task” button would surrender the signature feature that distinguishes his utility from Activity Monitor. An app that can only view processes but never stop a hung one is a dashboard, not a task manager.

Distribution outside the App Store would bypass the sandbox requirement entirely. A direct-download version, signed with a Developer ID and notarized by Apple, could retain full process-control abilities. That path imposes its own friction: users must manually install and trust the app, and automatic updates require a separate mechanism like Sparkle. But for a utility aimed squarely at power users—the kind willing to seek out a third-party process monitor—the extra steps are unlikely to deter adoption.

What This Means for Mac Users

The practical impact splits along audience lines:

Everyday Mac users who never think about killing processes beyond the Force Quit window won’t notice the gap. macOS already allows them to force-quit unresponsive apps via the Apple menu, and Activity Monitor handles the rest. They gain nothing from a Windows-style interface they’ve never used.

Windows switchers and dual-platform admins stand to benefit immediately. Many of these users rely on Task Manager’s performance graphs to diagnose CPU spikes, memory leaks, and disk activity at a glance. Plummer’s tool could provide that same fast triage without forcing them to learn Activity Monitor’s sparse layout. For IT professionals who manage Mac fleets alongside Windows machines, having a consistent monitoring tool across OSes reduces cognitive overhead during troubleshooting.

Developers and power users already familiar with Terminal tools like top or htop may see Plummer’s app as a welcome GUI alternative that surfaces data more visually. The per-core CPU graph alone—drawn as a small tile per core, not a single percentage—lets them instantly spot a single-threaded process pegging one core while the rest sit idle.

Until and unless Plummer releases a build, these groups must stick with what’s available. Activity Monitor can force-quit processes, albeit through a multi-step right-click workflow. Third-party utilities like iStat Menus offer a richer menu-bar dashboard, and the open-source htop (available via Homebrew) provides a terminal-based process browser with kill capabilities. None replicate the exact Windows Task Manager workflow Plummer is chasing, but they cover the essential needs.

How We Got Here: From XP to Swift

Dave Plummer’s relationship with Task Manager goes back to the mid-1990s. While at Microsoft, he wrote a small tool called “Task Manager” as a personal project to monitor system resources; it was included in Windows NT 4.0 and evolved into the utility bundled with every consumer release since. Plummer later left Microsoft but remained an active developer and YouTuber, often sharing detailed coding walkthroughs.

Earlier this year, Plummer confirmed that Microsoft had provided the original XP Task Manager source code and granted permission to present it on his channel—an unusual gesture that sparked speculation about a Mac port. He then surprised followers by revealing he was building a macOS-native version entirely in Swift, not by porting the C++ Windows code.

The timeline, pieced together from Club386’s report and Plummer’s own posts:

  • Pre-2026: Plummer receives XP Task Manager source from Microsoft for educational use.
  • Mid-2026 (estimated): Development begins on a Swift-based macOS equivalent.
  • Late July 2026: Plummer shares first screenshots on X, showing a near-complete prototype. He discusses sampling rates and teases a potential free App Store beta.
  • Same period: He learns that App Sandbox rules prevent process termination, putting the App Store distribution in doubt.
  • July 30, 2026: Club386 publishes the first detailed report, bringing the story to a wider audience.

Throughout, Plummer has been transparent that the project is “experimental” and not a guaranteed product. He floated the possibility of open-sourcing the code if he loses momentum—a common fate for side projects that run into platform friction.

Your Move: What to Do While You Wait

If Plummer’s macOS Task Manager sounds useful, you have zero immediate action to take—no download exists. But there are steps to prepare or fill the gap now:

  • Follow the project. Monitor Plummer’s X account or YouTube channel for release announcements. Given his history, any beta would likely appear there first.
  • Get comfortable with Activity Monitor. It’s already installed and can force-quit apps, show CPU/memory/energy, and display a GPU history window (View > GPU History). The interface is less dense, but it’s fully functional.
  • Try third-party dashboards. iStat Menus (paid) puts performance graphs in your menu bar with process-level detail. MenuMeters (free, open-source) is a leaner alternative. Both give you always-visible CPU cores, network, and disk activity.
  • Learn Terminal basics. htop (install via brew install htop) provides a color-coded, mouse-friendly process list where you can kill tasks with a keypress. It’s the closest you’ll get to Task Manager’s power without a dedicated GUI.
  • Manage startup items through System Settings. Go to General > Login Items & Extensions to see and remove launch agents. It’s not as granular as Windows’ Startup tab, but covers the most common offenders.

When—and this is a big “when”—Plummer releases a binary outside the App Store, you’ll need to allow it in Gatekeeper. The standard drill: download, right-click > Open, confirm the security prompt. If the app is notarized, macOS won’t block it outright. Given Plummer’s reputation, a notarized build is a safe bet.

What’s Next for the Project

The decisive fork in the road is distribution. If Plummer chooses direct download, the tool could ship within weeks; he’d simply wrap the prototype, add a Sparkle updater, host it on a website, and let word spread. That path offers full functionality and fast iteration, but it demands ongoing maintenance and support—a heavy lift for a side project.

Alternatively, he could pare the app down to a read-only performance monitor, stripping process termination to meet sandbox rules and submitting it to the App Store. That version would likely disappoint power users but could reach a broader, less technical audience.

The most likely outcome, based on his public hedging, is that he’ll release the source code and step back. In that scenario, the community—already interested in a Windows-like monitor—could fork the project, add features, and keep it alive via GitHub releases. Plummer’s habit of open-sourcing older projects makes this outcome plausible.

Either way, don’t wait for the App Store. Apple’s sandbox philosophy won’t change to accommodate a single utility, no matter how nostalgic. The Task Manager for Mac will either arrive through a direct channel or become another “what could have been” footnote. For now, the code exists and the desire is real; the only missing piece is a release button that Plummer feels comfortable pushing.