Your agent is still working. Your Mac shouldn't clock out.

Those keep your Mac awake for as long as you leave them switched on. The decision is yours, and the classic failure mode is forgetting to flip it off, then finding a hot, flat laptop at the bottom of your bag. HoldMyCode ties the wake lock to the agent instead. The hold exists only while a watched agent is in the middle of a task, and it ends by itself when the work does. Nothing to toggle, nothing to forget.

caffeinate is built into macOS and fine while the lid is open: caffeinate -i claude keeps the Mac up for as long as that process runs. Two catches. It holds for the whole session, including the hours an agent sits idle at a prompt, and it does nothing about the lid: close it and the Mac sleeps anyway. HoldMyCode holds only while a task is running, and handles the lid as well. More in keeping Claude Code running with the lid closed.

Yes. A plain sleep assertion isn't enough for a lid close, so HoldMyCode installs a small privileged helper that disables lid sleep while a hold is active and turns it back on the moment the hold ends. No external display, keyboard, or dongle required. macOS asks you to allow it once, in System Settings under Login Items.

No. It never reads your code or your prompts, and nothing about your sessions leaves your Mac. Hooks record only whether a session is working, in a small file on your Mac. The usage card counts turns and estimates cost from Claude Code's own local files and asks Claude Code itself for your limit figures; that runs on your Mac and sends nothing anywhere. The app has no account and no analytics inside it. It talks to exactly two servers: GitHub, to check for and download a new version, and, if you leave local currency switched on, a public exchange rate feed once a day, which is sent nothing about you. The only other part that talks to a server is this website, which keeps an anonymous download count and the name you give before downloading.

Claude Code, Codex, Gemini CLI, Cursor and Cline through their lifecycle hooks. Since 2.0 those install themselves: every supported agent found on your Mac is hooked up at launch and kept up to date, and so is one you install later. Cline is the exception, because its config sits in ~/Documents behind a macOS permission prompt, so it asks first. Claude Cowork works out of the box from the Claude app's task logs. You can still remove hooks in Settings › Agents, and nothing puts them back.

A threshold you pick. Below it, the hold releases and a notification tells you why. You can also restrict holds to times when you're on power, and HoldMyCode won't override Low Power Mode. Thermal pressure ends a hold too, rather than cooking the machine in a bag.

Free. No licence key, no trial timer, no surprise paid tier waiting in the wings. It's a small utility that does one job, and charging for it isn't the plan. The app is closed source, so that's a promise rather than something you can audit, but there's no account to create and nothing to cancel.