How I Debug Electron Apps for Windows on my MacBook

How I Debug Electron Apps for Windows on my MacBook

More

Descriptions:

Web Dev Cody walks through a practical cross-platform debugging workflow for Electron applications, triggered by a Windows-specific bug in his Mission Control app that was invisible on Mac. When a Windows user reported that a panel would load and immediately close when starting a Claude Code session, the developer needed a way to reproduce and investigate the issue without physical Windows hardware.

The solution is an AWS EC2 instance running Windows Server 2025 Base, accessed via Remote Desktop using the Windows App (formerly Microsoft Remote Desktop). The video provides specific setup guidance: choose at least a large instance rather than medium (which has only 2 vCPUs and 4 GB RAM and proved too slow), provision at least 100 GB of storage to accommodate Visual Studio, Node.js, PNPM, and the full node_modules tree, and restrict the RDP security group to your own IP address only. After connecting, the developer recreated the full development environment and ran the app locally while using both Claude Code and OpenAI Codex to analyze logs and identify the failure.

The root cause was a path resolution problem: Claude Code installs at different filesystem paths on Windows versus Mac and Linux, and the application was not accounting for per-user installation path variations. The video closes with a note that VirtualBox is a local alternative for developers without an existing AWS account, and mentions that a light version of Mission Control is nearing release with the full project roadmap available at agentsystem.dev.


📺 Source: Web Dev Cody · Published May 16, 2026
🏷️ Format: Troubleshooting

1 Item

Channels

1 Item

People