Caprock

Caprock

See what your Claude Code is actually doing.


*Real capture, 46 seconds. One session working; the bars advance as the minutes roll over and the cost ticks with them.*

[](https://github.com/dspv/caprock/releases) [](LICENSE) [](https://github.com/dspv/caprock/actions/workflows/ci.yml) 

# macOS / Linux
brew install dspv/tap/caprock

# Windows
scoop bucket add dspv https://github.com/dspv/scoop-bucket
scoop install caprock

caprock up        # opens localhost:4173; offers to set up hooks + plan-limit status line

Have Go? `go install github.com/dspv/caprock/cmd/caprock@latest` — the dashboard is embedded, so it works with no Node build. No package manager? Grab a binary from [Releases](https://github.com/dspv/caprock/releases).

Or let Claude Code install it — paste one prompt into a fresh Claude Code message.

It picks the right command for your machine, so there is nothing to choose. The `--yes` is load-bearing: consent for the hook is refused rather than assumed when stdin is not a terminal, which is what an agent's shell gives it, so without the flag you would get a dashboard that never sees a session.

The wording was tested against five agents given no other context. An earlier draft was refused outright by one of them, and the two lines it objected to were both ours meaning well: "do not start or type into any claude session" (our Rule 7, which reads as *do not tell the user*) and "show me the error instead of trying another source" (meant to stop a lookalike package being installed, which reads as *stop verify