CC Babysitter 0.9.1

• Fixed: after Claude Code updated itself, it replaced a background session's process on the old version with one on the new version, and CC Babysitter took a babysat session that was gone for that moment for one that had gone down. Its resume raced Claude Code, made a copy, and had to stop and remove it. A babysat background session that goes away on an older version than the one installed is now left to Claude Code for a minute, and Activity says why, such as "Claude Code updated from 2.1.295 to 2.1.296". A session still gone after that is brought back with that reason (#113).
• Fixed: after a restart of a Linux machine, every command could say "CC Babysitter is not running" while it ran, and the checks that refuse to act beside a running copy, such as ccbabysitter reset's, could be fooled the same way. When the clock is synced after boot, Linux can report a process's start a second later or earlier, and the check of the copy that holds the lock allowed only a tenth of a second (#112).
• Fixed: a session started with New session or ccbabysitter start was logged as "adopted ... (automatic: server auto-babysit)", as if CC Babysitter had acted on its own. Activity now says it is babysitting the new session it started (#116).
• Fixed: Not running listed conversations with nothing in them, such as an empty file left by an earlier Claude Code run, as rows with no name or folder that could not be resumed. They are left out now (#117).
• Fixed: the ssh command a server prints to reach its page forwarded port 47391 on your computer, which CC Babysitter there may already use. ssh then quietly forwarded only part of it, and the browser showed your own computer's page instead of the server's. The command now uses port 47392 on your side when the server uses 47391, and the address to open uses it too. It listens on 127.0.0.1 alone and stops with an error when it cannot take that port, and it ends a connection that stopped answering. On a server, ccbabysitter status prints the command and the address again (#114).
• Changed: when a server's page loses its ssh connection, it says the connection to the server was lost and to run the ssh command again, instead of "Not running. Start CC Babysitter to reconnect.", since CC Babysitter is usually still running there. The server guide says plainly that the page works only while that connection is open (#115).

CC Babysitter 0.9.0

• New: on a machine with no display, New session on the page and ccbabysitter start PATH start a babysat background session with Remote Control in a project folder. When Claude Code does not trust the folder yet, the page asks first and start wants --trust. Then CC Babysitter answers Claude Code's own question whether to trust the folder, and Claude Code records the trust itself (#87).
• Fixed: a session's model no longer shows as <synthetic> after it is resumed. Claude Code marks messages it writes itself that way, and the model shown is now the last one a model wrote (#98).
• New: a babysat background session that froze, busy waiting on the model for 20 minutes with no output, no change and no CPU use, is stopped with claude stop, which keeps the conversation, and started again in the background, and Activity says why. A session running a tool, waiting out a usage limit or a retry, or waiting on a question is never taken for frozen. Three freezes in two hours make it stuck, and Try again then stops the copy, while it is still frozen, so it is started again. A copy claude stop cannot stop is left as it is, and Activity says how to stop it by hand. A frozen session in a terminal or an app is left as it is, and its card, show and list say it is not responding (#94).
• Fixed: a background session's uptime counts from when the session started, not from when Claude Code started its process ahead of time, which could be hours earlier (#97).
• Fixed: ccbabysitter retry on a babysat session that is not stuck is refused and says so, with what the session is doing, instead of answering that it is babysitting it again and writing to Activity while nothing happened (#95).
• New: ccbabysitter list shows the page's Not running conversations last, under their own heading, and show and activity find them, with the command that starts one again. A word that names a running or babysat session still means that one (#96).
• Fixed: the page's note that Claude Code is not logged in now shows when it is not. The CLI exits with an error when nobody is logged in, which was read as no answer (#103).
• Changed: New session and ccbabysitter start start nothing while Claude Code is not logged in, and say so: such a session could reach neither the model nor Remote Control (#103).
• New: documentation at https://ccbabysitter.dev/docs/: a tutorial, how-to guides, every command made from the help pages, How it works made from the README, a troubleshooting entry for every warning and Activity error, and search. The README and ccbabysitter help point to it (#35).

CC Babysitter 0.8.0

• Changed: on the In background card of a session that came from a terminal, or from no app it can go back to, the main button attaches to the background copy, which keeps running with Remote Control on: Open in Terminal where CC Babysitter can open a terminal, and Copy attach command where it cannot, such as on a server. End background copy, which ends the copy and gives the command to resume the session in any terminal, moves to the card's menu (#79).
• Fixed: the In background card's main button no longer waits for the browser to stretch its column to fill it, which could leave it the width of its label for a moment when its menu opened (#78).

CC Babysitter 0.7.0

• Changed: Activity says why a babysat session went down, when CC Babysitter can tell, instead of "host process exited": Claude Desktop closed, closed and updated, or restarted for an update, with both versions; the session ended while Claude Desktop kept running; the computer restarted; VS Code, the session's terminal or its SSH connection closed; or the background copy ended. The Claude Desktop reasons need macOS or Windows. When several sessions went down together, one line says so as the first is brought back. Where nothing tells, the reason is "the process running it exited". The In background card gives the same reason, for example "At 22:11, Claude Desktop restarted for an update." (#68).
• Changed: the In background card's way back is one split button, such as Back to Desktop, with a menu for Open on claude.ai, Open in Terminal and Copy attach command that works with the keyboard and screen readers. The card and the Back to Desktop dialog say that Claude Desktop shows "Claude Code crashed" for the session while its background copy runs, and that Try again in Desktop picks it up after Back to Desktop (#50).
• Changed: ccbabysitter uninstall removes CC Babysitter completely, after saying what goes and asking: start at login, a copy still running, the state folder, the program, and on Windows its folder in the user Path. Babysat sessions keep running. --yes asks nothing, and --keep-files only removes start at login, as uninstall did before (#59).
• Changed: keep-awake stops idle sleep only, and a laptop set to sleep when its lid closes still sleeps then. Where closing the lid would put the computer to sleep, as macOS, Windows' power plan or Linux's logind says, the Babysit dialog, ccbabysitter status and the page's keep-awake pill now say it is kept awake while its lid is open, and the README explains it. When the computer slept while sessions were babysat, Activity says so once it is awake, with the time they could not be reached, for example "The computer slept because its lid was closed. Babysat sessions could not be reached from 08:52 to 09:04." The cause comes from macOS's power log; elsewhere the line names the sleep alone (#38).
• New: an About panel on the page, beside Settings. It has the version details to copy into a bug report, the update command for the system, and the ways to report a problem: by email to hello@ccbabysitter.dev, as a GitHub issue, or privately for a security problem. ccbabysitter help version and the README say the same (#54).

CC Babysitter 0.6.1

• Changed: when Claude Code's daemon stops a background session that sat idle and CC Babysitter brings it back, Activity now gives the reason as "Claude Code stopped it after 8 hours idle" instead of "host process exited", which read like a crash (#49).
• Fixed: the Claude Code plugin could ask whether you had installed CC Babysitter without ever showing the install command, and after quitting CC Babysitter it offered a settings change that cannot work once it has quit. It now shows every command in the reply before asking, and offers ccbabysitter uninstall to stop CC Babysitter for good (#58).
• Fixed: after Back to Desktop, the next rescue of that session first passed --remote-control, which made the CLI fork a copy; CC Babysitter stopped and removed the copy and retried without flags, but Activity showed "resume forked a copy", and a copy that lived long enough left an empty Remote Control entry in Claude Desktop under Other. A session the CLI keeps a background job record for is now resumed without flags from the first try (#55).
• Fixed: the Back to Desktop dialog said Remote Control stays off until you switch it on in Desktop, but Desktop turns it back on by itself when it was on for that session before. The dialog now says so (#52).
• Fixed: on a machine without the claude CLI, Activity got "agents --json did not answer:" every minute with nothing after the colon. It now says once that the Claude Code CLI is not installed, and says it again only after the CLI has worked in between; when the CLI answers with nothing, the line gives its error (#40).

CC Babysitter 0.6.0

• New: ccbabysitter open opens the page in your browser and prints no key, so an AI agent can run it. On a machine with no display it says how to connect instead.
• New: ccbabysitter version --json also says headless, true on a machine with no display.
• New: a Claude Code plugin. Install it with /plugin install ccbabysitter --marketplace pejmanebrahimi/ccbabysitter and say "babysit this session"; it also opens the page and answers questions about CC Babysitter.

CC Babysitter 0.5.2

• Fixed: runs of a Claude Desktop scheduled task were listed as ordinary sessions, with a Babysit button, and could be babysat, though Desktop starts the task again on its schedule and a copy brought back could repeat its work. A run is now never babysat: the page lists runs apart, in a folded Scheduled task runs section with no Babysit button, ccbabysitter list prints them last under their own heading, list --json and show --json carry scheduledTask, and ccbabysitter babysit refuses one with the reason.

CC Babysitter 0.5.1

• Fixed: the warning that a session would not come back showed for a session in a git worktree whose folder the claude CLI trusts through a folder above it, and could not be cleared. A worktree takes its trust from any folder above it; only a repository with a .git folder stops at its own folder.
• Fixed: on a Mac, the install script started CC Babysitter again after you had quit it, without opening the page. It now restarts it only when it runs in the background, as on Linux and Windows, and otherwise says how to start it.
• Fixed: after replacing an earlier version's login item, such as the Startup folder script on Windows, Activity said "Start at login was turned on outside CC Babysitter." It now says "Start at login kept on: CC Babysitter rewrote its login entry."

CC Babysitter 0.5.0

CC Babysitter now runs in the background on Linux, macOS and Windows and starts again when you log in, so you can close the terminal you started it from.

• New: ccbabysitter quit and a Quit button in the page's settings stop CC Babysitter. Babysat sessions keep running, but nothing brings them back until you run ccbabysitter again. Activity says "asked to quit", followed by ", from the command line" when the command asked.
• Changed: on Linux, desktop and server alike, ccbabysitter starts CC Babysitter in the background through the systemd user manager and gives the terminal back. Start at login is turned on the first time, also for anyone upgrading, and stays off once you turn it off. Run ccbabysitter --foreground to keep it in the terminal instead. --port now only applies with --foreground.
• Changed: running ccbabysitter while it already runs in the background prints the start information again and opens the page.
• Changed: on a Linux desktop, CC Babysitter starts with the graphical session, so it sees the desktop. Turning start at login off keeps the systemd unit, so ccbabysitter can still start it; ccbabysitter uninstall removes it.
• Changed: the install script restarts a background copy that is already running on a Linux desktop, so it runs the new version.
• Changed: on macOS, ccbabysitter starts CC Babysitter in the background as a user LaunchAgent and gives the terminal back. Start at login is turned on the first time, also for anyone upgrading. Logging in no longer opens the page, and CC Babysitter starts again if it crashes. ccbabysitter uninstall now works on macOS: it stops the LaunchAgent and removes its plist. The install script restarts a LaunchAgent that is already running, so it runs the new version, and a login started by an earlier version's LaunchAgent runs the new binary as the background copy.
• Changed: on Windows, ccbabysitter starts ccbabysitter-background.exe, a copy of the program built to show no console window, which runs in the background, and gives the terminal back. Start at login is turned on the first time, also for anyone upgrading, as a per-user Run value that starts it with no window; it replaces the Startup folder script earlier versions wrote. The install script installs both programs, asks a running copy to quit before replacing them, and starts it again afterwards. ccbabysitter uninstall now works on Windows. Releases carry ccbabysitter-background-windows-<arch>.exe beside each Windows program.
• Changed: ccbabysitter uninstall forgets that start at login was turned on, so a later ccbabysitter turns it on again, as on a machine that never had CC Babysitter.
• Changed: when launchd or systemd starts CC Babysitter again after it stopped unexpectedly, Activity says "Started again by the system after CC Babysitter stopped unexpectedly." instead of "Started at login."
• Changed: on Windows, when the app CC Babysitter is started from keeps its programs in a job that forbids leaving it, the background copy is started through Explorer, so closing that app no longer ends it.
• Changed: a page that lost its key, such as the one ccbabysitter opened before CC Babysitter restarted, says to run ccbabysitter to open it again. When CC Babysitter is not running, every command says "Start it with: ccbabysitter", on a server too, where it named a systemctl command that fails after ccbabysitter uninstall.
• Fixed: the warning that a session could not be brought back missed folders inside a git repository whose trust came from a folder above it. The desktop app accepts that, but the Claude Code CLI, which brings sessions back, does not. The warning now follows the CLI and says what is at stake and the exact command to run: "Won't come back if its app closes. Claude Code needs a one-time OK to run on its own in this folder. In a terminal, run cd <folder> && claude, answer Yes, then exit."

CC Babysitter 0.4.2

• Fixed: on a server, Activity said "Start at login was turned on outside CC Babysitter." right after installing, although CC Babysitter set up its own service. It now says "Set up as a service that starts at boot.", and a service turned off by hand is described as the service, not as start at login.
• Fixed: when a stray copy of a session could not be cleaned up, the page and Activity gave claude stop X && claude rm X, which Windows PowerShell 5.1 cannot run. They now give the two commands one after the other.