Monitor a lid-closed Mac without fooling yourself

“Online” is not the same as “working”

A successful ping or remote login answers one question: some path to the Mac is available. It does not prove the coding agent is still running, making useful progress, or able to continue without input. Monitoring gets more reliable when each signal has one clear meaning.

For lid-closed agent work, separate at least four states: the Mac is reachable, the process is alive, the task is advancing, and the machine is physically safe. StillOn helps with the power transition behind the first state. It does not supply the other evidence.

Choose a task-specific progress signal

The best progress signal comes from the work itself. For a build, that can be a changing log followed by a verified artifact. For a coding agent, use its own remote session or transcript and look for new tool calls, file changes, test output, or a clear request for input. For a download, compare transferred bytes or the final checksum.

Avoid using fan noise, an illuminated network indicator, or elapsed time as proof. They can correlate with work while saying nothing about whether the intended task advanced.

• Reachability: can the trusted remote path contact the Mac?
• Liveness: does the expected process still exist?
• Progress: did a task-owned output change?
• Completion: did the expected artifact or success check pass?
• Safety: is power, battery, and physical placement still acceptable?

Test the remote path before closing

Configure remote access while you can still use the keyboard and display. Use the agent vendor’s remote feature, macOS Screen Sharing, or SSH only if you understand and secure that option. Confirm the connection from the device and network you will actually use.

Then begin a harmless, short task and observe it once with the lid open. Arm StillOn, close the lid, reconnect, and look for a new task-owned event. This sequence distinguishes a power problem from a remote-access or agent problem.

Do not expose a management service directly to the public internet merely to make this test convenient. Prefer a trusted private network or the product’s documented remote-access mechanism.

Plan for loss of visibility

Decide in advance what you will do if the connection disappears. A safe default is to treat an unknown state as unknown, return to the Mac, and open the lid. Automatically restarting a process can make matters worse if it was waiting on a destructive confirmation or had already partially completed an operation.

Keep the first closed run short. Increase duration only after the same setup has behaved predictably, and repeat the short test after a major macOS, agent, VPN, or remote-access update.

Physical safety remains local

StillOn reads battery temperature and macOS thermal pressure so it can stop a closed-lid session. Those signals do not certify a workload or reveal obstructed airflow. Keep the Mac on a hard, open surface and avoid sustained heavy work in a hot environment.

Never leave a running notebook inside a bag. If the machine feels unusually hot, smells unusual, shows battery swelling, or behaves unpredictably, stop the task, disconnect power if safe, and follow Apple’s service guidance.

A five-minute rehearsal

The reliable workflow is intentionally uneventful: start a reversible test, verify it remotely with the lid open, arm StillOn, close the lid, verify one new progress event, reopen, and confirm normal sleep behaviour returns. Only then use the same path for work that matters.

That rehearsal gives each component one job. The agent runs the task. The remote tool exposes status. StillOn keeps the Mac available. You remain responsible for the physical setup and for deciding whether the evidence is strong enough to leave it running.