Download Latest Version Caprock_0.107.7_x64-setup.exe (9.4 MB) Google Add to Preferred Sources
Home / v0.45.0
Name Modified Size InfoDownloads / Week
Parent folder
caprock_0.45.0_windows_amd64.zip 2026-09-02 8.8 MB
caprock_0.45.0_windows_arm64.zip 2026-09-02 8.1 MB
checksums.txt 2026-09-02 600 Bytes
caprock_0.45.0_darwin_amd64.tar.gz 2026-09-02 8.7 MB
caprock_0.45.0_darwin_arm64.tar.gz 2026-09-02 8.3 MB
caprock_0.45.0_linux_amd64.tar.gz 2026-09-02 8.6 MB
caprock_0.45.0_linux_arm64.tar.gz 2026-09-02 8.0 MB
README.md 2026-09-02 1.9 kB
v0.45.0 source code.tar.gz 2026-09-02 5.7 MB
v0.45.0 source code.zip 2026-09-02 6.0 MB
Totals: 10 Items   62.3 MB 0

Changed

  • A session stays open until its process exits. It used to close after a stretch of silence, and every number chosen for "a stretch" was wrong for somebody: twelve hours left the day's work marked live at midnight, and one hour closed a session while its owner was at lunch. Both were guesses about a person's day standing in for a fact about a process — and the fact is available. The shim now reports the pid of the Claude Code that ran it, and Caprock already knew the pid of every session it starts itself, so the sweep asks whether that process is alive instead of watching a clock.

A session you leave for a week is still there when you come back. One whose terminal you closed ends on the next sweep, without waiting for a threshold at all.

A staleness threshold still exists for sessions with no pid to ask — rows written by an older shim, and transcripts read with no live process behind them — and it is now twenty-four hours, because there is nothing to verify and the only cost of being slow is a stale row in a list.

OpenCode sessions are judged by the clock alone, never by liveness. They are read out of OpenCode's own database rather than watched, so there is no process of ours behind them and they arrive already old. The first cut of this change missed that and filled the screen with 97-day-old sessions marked live.

Fixed

  • The Now screen shows now. A session that has not made a sound in two days no longer appears there, whatever its status column says — status alone cannot tell a quiet session from somebody's history, because an observed agent's sessions arrive weeks old by definition. Two days rather than one, so a session left on Friday evening is still on screen on Monday morning. Anything actually working shows regardless of age, which is what the screen is for. Older sessions are on Lifetime and under "show ended".
Source: README.md, updated 2026-09-02