Monitor AI workflows running on your Mac.

Those tools help you access your Mac. Runwhile helps you supervise it. Instead of constantly checking on long-running work, Runwhile monitors progress, sends notifications when attention is needed, and gives you remote access only when intervention becomes necessary.

Yes. Like any remote access or monitoring solution, your Mac must remain powered on to receive notifications, provide screenshots, accept remote connections, or transfer files. Runwhile includes Keep Awake features to help prevent sleep during long-running workflows. Once your work is complete, you can remotely put your Mac to sleep directly from Runwhile.

Yes. Runwhile can securely search your Mac and create a direct peer-to-peer (P2P) transfer session for files you request. Files are only discovered and transferred when you explicitly initiate a search or download. Runwhile does not store your files and only relays encrypted data when required to establish the connection. macOS permissions apply, so you'll need to grant Runwhile access to specific folders before they can be searched or downloaded remotely. You can review or revoke these permissions at any time.

Traditional monitoring tools focus on servers and infrastructure. Runwhile focuses on the Mac you actively work from. It combines workflow awareness, screenshots, notifications, and instant remote intervention in a single tool.

Yes. Runwhile was designed specifically for long-running developer workflows, including Claude Code, Cursor, local AI agents, builds, renders, imports, and terminal jobs.

No. Runwhile only captures screenshots when a feature explicitly requests them, such as workflow supervision, manual screenshot requests, or remote access sessions. Screenshots are not continuously recorded, and they are never stored on Runwhile servers. macOS also provides a visual privacy indicator when screen recording is active, allowing you to see when Runwhile is accessing screen content.

Yes. Runwhile was designed specifically for long-running developer workflows, including Claude Code, Cursor, local AI agents, builds, renders, imports, and terminal jobs.

Yes. Runwhile is designed for remote access over the internet. Whether you're at home, traveling, or away from your desk, you can receive notifications, view screenshots, download files, and remotely control your Mac from anywhere.

Runwhile uses secure authentication and direct WebRTC peer-to-peer (P2P) connections whenever possible. When a direct connection isn't available, Runwhile acts only as an end-to-end encrypted relay. Your screen, files, screenshots, clipboard history, workflow supervision data, and other device data are never stored on Runwhile servers. They remain on your Mac and are transmitted only when requested. To support remote access and supervision features, some data may be stored locally on your Mac. You can clear this local data at any time from the Runwhile app, but doing so may limit or disable certain remote functionality until the data is rebuilt. You remain in control at all times. Access can be revoked instantly, and all communication is encrypted in transit.

Yes, with a standard macOS architectural caveat. Runwhile’s core engine—background workflow monitoring, thermal/battery alerts, Keep Awake, and P2P file search—works flawlessly on completely headless machines. However, because macOS natively suspends its graphics rendering when no display is detected, visual features like Screenshots and WebRTC Remote Control require an active monitor or a cheap HDMI/USB-C dummy plug to function.