cc-cream 0.1.13 → 0.1.15

package/CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to cc-cream are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.15] — 2026-05-29
+
+### Fixed
+- **An orphaned status line no longer crashes on every render after `/plugin uninstall`.** If you ran `/plugin uninstall cc-cream` without first running `/cc-cream:uninstall`, the `statusLine` entry stayed in `settings.json` while the plugin cache was deleted. The cache-glob then matched nothing, the baked command collapsed to a bare relative `src/cc-cream.js`, and Claude Code hit `MODULE_NOT_FOUND` (exit 1) on every render — and `/cc-cream:uninstall` was gone, so the only fix was hand-editing `settings.json`. The auto-update command now captures the resolved version dir in `$d` and short-circuits with `[ -z "$d" ] && exit 0`, so an orphaned status line is inert (silent, exit 0) instead of a recurring error. "Degrade, never crash." New installs/auto-wires get the guarded command; existing users pick it up on their next `/cc-cream:setup`.
+
+## [0.1.14] — 2026-05-29
+
+### Changed
+- **The status bar now turns itself on — no manual `/cc-cream:setup` for fresh installs** (CREAM-nywsljfq). Claude Code can't let a plugin contribute the main status line natively (only `agent`/`subagentStatusLine` are plugin-settable — verified by probe), so the bar still needs a write to `settings.json`. Instead of making you run `/cc-cream:setup`, the `SessionStart` hook (`hooks/auto-setup.js`, renamed from `setup-reminder.js`) now **auto-wires** cc-cream's `statusLine` on the first session after install — but **only when no status line is configured**. It never clobbers a status line you set for something else (that still routes through the interactive `/cc-cream:setup`), and a one-shot marker means it never re-adds the bar after you remove it with `/cc-cream:uninstall`. The nudge to run `/cc-cream:setup` now appears only in the foreign-status-line case. Output stays a single `systemMessage` (zero model tokens). You may need to restart/trust the workspace for the bar to appear.
+
 ## [0.1.13] — 2026-05-29
 
 ### Fixed
@@ -119,6 +129,7 @@ line and prints a colored ≤3-row bar — zero tokens, the model never sees it.
 - Supports **macOS and Linux**; Windows is a planned fast-follow.
 - Requires Claude Code **2.1.132+** (`effort` / `thinking` need 2.1.145+).
 
+[0.1.15]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.14...v0.1.15
 [0.1.6]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.5...v0.1.6
 [0.1.5]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.4...v0.1.5
 [0.1.4]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.3...v0.1.4

package/README.md

@@ -66,16 +66,21 @@ To use the self-hosted marketplace directly:
 /plugin install cc-cream
 ```
 
-Then wire it into your settings in one step:
+That's usually all you need: on the first session after install, cc-cream
+**auto-wires** its `statusLine` into `~/.claude/settings.json` (you may need to
+restart or trust the workspace for the bar to appear). It only does this when no
+status line is configured — it never overwrites one you set for something else,
+and it never re-adds the bar after you remove it.
+
+If you already have a status line and want to replace it with cc-cream's, run:
 ```
 /cc-cream:setup
 ```
 
 The `/cc-cream:setup` command runs the consent installer, which writes the
-`statusLine` block to `~/.claude/settings.json`. Until you run it, cc-cream
-prints a one-line reminder at the start of each session (it stops once the bar
-is wired). Updates are automatic: when `/plugin update` drops a new version into
-the cache, the next render picks it up without any further action.
+`statusLine` block to `~/.claude/settings.json`. Updates are automatic: when
+`/plugin update` drops a new version into the cache, the next render picks it up
+without any further action.
 
 ### Option 2 — npm
 
@@ -113,13 +118,24 @@ and you may need to **restart** it for the bar to appear.
 
 ### Uninstall
 
-Plugin users — two steps (Claude Code can't clean `settings.json` when a plugin
-is removed, so the wiring is cleared separately from the cache):
+Plugin users — two steps, **in this order** (Claude Code can't clean
+`settings.json` when a plugin is removed, so the wiring is cleared separately
+from the cache):
 ```
-/cc-cream:uninstall          # removes the statusLine wiring
-/plugin uninstall cc-cream   # drops the plugin from the cache
+/cc-cream:uninstall          # 1. removes the statusLine wiring (run this FIRST)
+/plugin uninstall cc-cream   # 2. drops the plugin from the cache
 ```
 
+> **Order matters.** `/cc-cream:uninstall` lives inside the plugin, so once you
+> run `/plugin uninstall` it's gone. The status line itself degrades to nothing
+> if the cache is missing (it won't error), but the now-inert `statusLine` block
+> lingers in `settings.json`. To clear it after the plugin is already gone, run
+> the npm bin (no global install needed):
+> ```bash
+> npx -y -p cc-cream cc-cream-setup --uninstall
+> ```
+> or remove the `statusLine` key from `~/.claude/settings.json` by hand.
+
 npm / manual users:
 ```bash
 cc-cream-setup --uninstall                 # npm (add --purge to also remove runtime + config)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-cream",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "description": "Claude Code cache/context/cost status-line tool",
   "directories": {
     "doc": "docs"

package/src/install.js

@@ -28,8 +28,16 @@ const TRUST_NOTE =
 // it, a non-numeric cache dir (a git-sha install like `c83650b6360f/`) sorts
 // last and pins the bar to whatever version that happens to be, defeating
 // auto-update. With it, `/plugin update` is applied live with no re-run of setup.
+//
+// The resolved dir is captured in `$d` and GUARDED with `[ -z "$d" ] && exit 0`:
+// when the glob matches nothing — the state left behind if a user runs
+// `/plugin uninstall cc-cream` WITHOUT first running `/cc-cream:uninstall`, so a
+// stale statusLine outlives the deleted cache — the command degrades to a silent
+// exit 0 instead of running a bare relative `src/cc-cream.js` that crashes with
+// MODULE_NOT_FOUND on every render. "Degrade, never crash" (CLAUDE.md). `exec`
+// replaces the shell so stdin/stdout pass straight through to the renderer.
 export function autoUpdateCommand(nodePath) {
-  return `${nodePath} "$(ls -1d "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/*/cc-cream/*/ 2>/dev/null | grep -E '/[0-9]+(\\.[0-9]+)+/$' | sort -V | tail -1)src/cc-cream.js"`;
+  return `d="$(ls -1d "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/*/cc-cream/*/ 2>/dev/null | grep -E '/[0-9]+(\\.[0-9]+)+/$' | sort -V | tail -1)"; [ -z "$d" ] && exit 0; exec ${nodePath} "\${d}src/cc-cream.js"`;
 }
 
 // `desired` is considered already installed if it matches the planned command
@@ -49,7 +57,7 @@ function isInstalled(existing, command) {
 // (dev repo, copied home runtime, or the plugin cache-glob) — every command
 // references the cc-cream entrypoint. Used by uninstall so we never touch a
 // statusLine the user wired for something else.
-function isCcCreamStatusLine(existing) {
+export function isCcCreamStatusLine(existing) {
   return (
     !!existing &&
     typeof existing === 'object' &&
@@ -187,7 +195,7 @@ function copyRuntimeFiles(sourceFile, destDir) {
 // PATH, so a bare `node` is unsafe. We prefer the shell's `command -v node`
 // (the path the user's interactive shell would pick), falling back to
 // process.execPath (the node currently running setup) if that fails.
-function resolveNodePath() {
+export function resolveNodePath() {
   try {
     const found = execSync('command -v node', { encoding: 'utf8' }).trim();
     if (found) return found;