Cold Brew v1.5.2

• A closed MacBook on a monitor no longer sleeps (and locks) while you're using it. When the agents finished, keep switched off and, seeing the lid shut, put the Mac to sleep, even in clamshell mode with a monitor and keyboard plugged in. Working at a desk with the lid closed, that meant logging back in every few minutes. Now it sleeps only with no monitor plugged in; with one, macOS keeps the Mac awake as it always does in clamshell mode.

Cold Brew v1.5.1

• The GitHub repo is now liam-machine/cold-brew, to match the app. Updates and downloads use the new address; the old one redirects, so earlier versions still find updates.

Cold Brew v1.5.0

• Lid Agents is now Cold Brew. Same app, same cup, same settings, new name: the menu bar, notifications, Spotlight, the installer and agents all say Cold Brew. Updating replaces "Lid Agents.app" with "Cold Brew.app" in the same folder, a copy left in the other Applications folder is removed, and Open at Login moves over. The agents command, its settings and ~/.cache/lid-agents are unchanged.
• The download is now ColdBrew.dmg. Links to LidAgents.dmg still work.

Lid Agents v1.4.2

• The installer's last message matches how keep works now. It said to click the cup to keep agents running; keep has switched on by itself since 1.4.0. It now says so, and how to go back to switching it on yourself (agents auto off). With auto keep off, it says to click the cup, as before.

Lid Agents v1.4.1

• Slowed apps stay slowed while the lid is closed. They were put back at full speed after a minute, then slowed again a minute later, over and over: once slowed, an app looked as if something else had already put it in the background, so it was handed back.
• The screen still sleeps if the monitor check is wrong when the lid closes. In the second after the lid closes, the display list could report a monitor that wasn't there and leave the screen on. It's checked again a minute later.

Lid Agents v1.4.0

• Keep switches on by itself when an agent starts. You no longer have to remember the hotkey before closing the lid: as soon as an agent starts working, the cup fills, and it empties once they've all finished, as before. Routine switches are quiet: you're told once the first time, and after that the cup shows it. The battery floor and an unanswered prompt still notify.
• Pausing means "not this time". Press ⌃0, click Sleep (normal) or run agents pause while agents work and keep stays off for them. Once they've all finished, working or waiting on you, the next agent to start switches it on again. The battery floor and an unanswered prompt work the same way, so keep never switches straight back on after them.
• No 8-hour cap. Keep runs for as long as agents work; the battery floor (15%) is the limit. agents keep 4h still sets one if you want it, and Keep running for 3 hours is unchanged.
• Prefer it the old way? Turn off the cup → Settings → Keep running whenever an agent starts, or run agents auto off. Keep then runs only when you switch it on.
• What the agent uses keeps running; everything else is slowed. With the lid closed and keep on, apps no agent is using drop to background priority (they keep running, just with the lowest CPU and disk priority) and are back at full speed as soon as the lid opens. Never slowed: the app an agent runs in (VS Code, cmux, Terminal…), anything an agent started (a simulator, a browser it drives), apps busy with a call or audio, and the Keep at Full Speed list (Simulator, Xcode, Docker, OrbStack and the common browsers to start with). Change it under the cup → Settings, or with agents apps. System processes and command-line tools are never touched.
• The screen sleeps and the Mac locks when you close the lid. Before, an app holding the display awake (a Chrome tab capturing, a video) could leave a closed Mac with its display on and unlocked for as long as keep ran. Now the display goes to sleep as soon as the lid closes, unless a monitor is plugged in.
• agents status shows whether auto keep is on, and whether it's off for the agents running now, and which apps are slowed.

Lid Agents v1.3.1

What's Changed

• Remote Control reaches the settings file Claude Code reads by @liam-machine in #6

Full Changelog: v1.3.0...v1.3.1

Lid Agents v1.3.0

• Answer agents from your phone. Lid Agents turns on Claude Code's own Remote Control for new sessions, so with the lid closed you can answer a Claude session from claude.ai/code or the Claude app, which gets a push when it needs you. After setup, Lid Agents asks once whether to turn it on, explaining what it does (unless you've already chosen in Claude Code's /config). Turn it on or off any time under the cup → Settings → Connect new Claude sessions to your phone, or with agents remote on|off. agents integrate turns it on unless you've already chosen. It sets remoteControlAtStartup and, unless you've chosen otherwise, inputNeededNotifEnabled in ~/.claude/settings.json.
• Busy sessions your phone can't reach are named. Claude Code only connects a session that's already running from inside it, so when you switch keep on, the notification lists any busy Claude session that isn't on Remote Control, and so do the cup's menu, agents and agents remote. Run /remote-control in each before you close the lid.
• Click an agent to go to it. In the cup's Agents list, or agents focus <pid>. It brings up the app the agent runs in, whichever terminal or editor that is, found from its processes, and the agent's own tab where the app allows: cmux, Terminal and iTerm2 (macOS asks once to allow it), tmux (its pane, then the terminal that used it last), WezTerm and kitty.
• A clearer menu. Top to bottom: what's happening, When the lid closes (Sleep (normal), Keep running while agents work, Keep running for 3 hours, with a tick on the one in use), the Agents that are running (each working or needs you, in full colour, with a phone in front of a Claude session on Remote Control and ⚠ in front of one that isn't), then Settings for the wait time, Remote Control, the hotkey, Open at Login, updates and the log. It opens faster too: one look at the processes instead of three.

Lid Agents v1.2.1

What's Changed

• Tests for detection, agents mark and the hooks merge, run in CI by @karan-ssj3 in #4

Full Changelog: v1.2.0...v1.2.1

Lid Agents v1.2.0

• Lid Agents knows when an agent needs you. An agent stopped on a permission prompt or a question shows as needs input in agents busy and the cup's Busy agents menu (after busy agents). Run agents integrate to set it up:
  • Claude Code and Codex get hooks (in ~/.claude/settings.json and each Codex home's hooks.json) that run when the agent stops on a prompt and when it moves on. They're tagged, print nothing and always succeed; your other hooks stay as they are, and a .lid-agents.bak copy is kept before the first change. Codex asks you to review new hooks once (/hooks).
  • OpenCode: the plugin does the same on its permission and question events, per request, and only while no other session is still working.
• Choose how long to wait for you. With the lid closed, a closed Mac stays awake 3 minutes by default for an agent that needs your answer (enough to answer from your phone), then sleeps. Change it under the cup → When an agent needs you (3, 10, 30 or 60 minutes) or with agents wait <minutes>. With the lid open, an agent waiting on you counts as busy, so keep doesn't switch off while you read.
• An approved command that runs for 10 seconds or more means the agent is working again, even before its next hook fires, so a closed Mac never sleeps partway through an approved task.
• Settings files are edited safely: an unreadable or invalid file is left alone, an unchanged file isn't rewritten (the app checks at every launch), and permissions are kept. Hooks installed under a custom CLAUDE_CONFIG_DIR are found again on upgrade and uninstall.
• agents uninstall removes the hooks too.