Goguma

What it does

goguma wakes your machine shortly before each scheduled job, keeps it awake while the job runs, and lets it sleep again as soon as the job is done.

goguma doesn't run your jobs; it makes sure the laptop is awake when they fire.

A sleeping machine doesn't queue the jobs it missed and catch up later. It misses them outright. Nothing fails, nothing retries, and no error is written anywhere, because as far as the scheduler is concerned nothing went wrong. You find out weeks later, when you notice the digest you set up has been arriving on some days and not others.

There is a second version of the same problem, and it is newer. Work that has no schedule at all still takes as long as it takes: a coding agent chewing through a refactor, a long build, a big sync. Close the lid and the machine sleeps underneath it, and you come back to a session that stopped halfway.

goguma run -- claude -p "refactor the auth module"

Sleep is held off for exactly as long as that command runs, lid closed included, then released. For an agent inside an editor, where there is no command to wrap, goguma sets that up and keeps it that way: Claude Code, Codex, Cursor and Gemini CLI report when they are working, and the machine stays awake until they stop. It is a setting, so one switch turns it off again.

goguma fixes both. It lives in the