How-to guide
Stop babysitting or remove CC Babysitter
You can stop babysitting one session, quit CC Babysitter until you need it again, or remove it from the computer. Unbabysitting, quitting and uninstalling leave your sessions running where they are.
Stop babysitting one session
On the page, press Unbabysit on the session's card. The session keeps running in its app, and CC Babysitter no longer brings it back if that app closes. From a terminal, give the session's name or short id:
On a computer with a display, a session that CC Babysitter brought back in the background has no Unbabysit button. Stopping its background copy ends the babysitting instead. For a session from Claude Desktop or VS Code, that is the card's Back to Desktop or Back to VS Code button. For one from a terminal, choose End background copy from the menu under the arrow beside the card's main button. From a terminal, the same is:
On a server, background sessions have Unbabysit, since there is no other app to go back to. A stuck session has Try again and Stop watching; Stop watching is the one that ends the babysitting.
Quit CC Babysitter for now
Open Settings on the page and press Quit CC Babysitter, then Quit. Or run:
Babysat sessions keep running, but nothing brings them back if their app closes, and the computer may sleep. Run ccbabysitter to start it again. If start at login is on, it also starts again the next time you log in, or at boot on a server.
Stop it and keep its files
To stop the background copy and keep it from starting at login, while keeping the program and its settings, run:
It asks nothing. On Linux it also turns lingering off, if CC Babysitter turned it on. A later plain ccbabysitter starts it again and turns start at login back on, as on a computer that never had it.
Remove it completely
Run:
It lists what it will remove and asks first. Then it removes everything CC Babysitter put on the computer:
- start at login;
- a copy still running, which it asks to quit;
- its state folder, with the settings, the babysat sessions and the activity log;
- the program itself. On macOS and Linux that is one file, and its folder stays. On Windows it is the folder
%LOCALAPPDATA%\Programs\CCBabysitter, which also comes out of your Path, and Windows deletes it a moment after the command ends.
On Linux, it also turns lingering off, but only if CC Babysitter turned it on. If another ccbabysitter is still on your PATH, such as one from go install, it names it at the end for you to delete. In a script with no terminal to ask in, add --yes to skip the question.
If you added the Claude Code plugin, remove it in Claude Code with /plugin uninstall ccbabysitter.
To keep the program but start over from empty settings, quit CC Babysitter and run ccbabysitter reset. It shows which state folder it will delete and asks first.