cc-cream 0.1.8 → 0.1.10

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.10] — 2026-05-29
+
+### Added
+- **Setup reminder after plugin install** (CREAM-cpcwjkxi). Installing the plugin makes the commands available but can't wire the status bar (Claude Code has no install hook to write `settings.json`), so users saw no bar and didn't know to run `/cc-cream:setup`. A `SessionStart` hook (`hooks/hooks.json`, auto-discovered) now emits a one-line `systemMessage` nudging the user to run `/cc-cream:setup` — but **only while cc-cream's statusLine is absent**, so it self-silences once setup runs. `systemMessage` is shown to the user and adds **nothing** to the model context (zero tokens). Degrades safely: missing `settings.json` → nudge; malformed → silent; always exits 0. Biome now also lints `hooks/`.
+
+## [0.1.9] — 2026-05-29
+
+### Fixed
+- **`/cc-cream:setup` and `/cc-cream:uninstall` no longer hang on a y/N prompt** (CREAM-vxbbrypj). The slash commands run `install.js` via Claude Code's bang execution, which has no interactive TTY, so install.js's readline prompts blocked forever — the uninstaller's "delete runtime/state?" prompt was the dead end. install.js now detects a missing TTY and resolves prompts non-interactively: uninstall removes the `statusLine` and **keeps** the runtime/state artifacts (re-run in a terminal or pass `--purge` to delete them); setup overwrites an existing *cc-cream* `statusLine` but never clobbers a foreign one without a terminal or the new `--force`/`--yes` flag. Interactive terminals are unchanged. (Plugin removal still takes two steps — `/cc-cream:uninstall` then `/plugin uninstall cc-cream` — because Claude Code has no plugin-uninstall hook to clean `settings.json` automatically.)
+
 ## [0.1.8] — 2026-05-29
 
 ### Added

package/README.md

@@ -72,9 +72,10 @@ Then wire it into your settings in one step:
 ```
 
 The `/cc-cream:setup` command runs the consent installer, which writes the
-`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.
+`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.
 
 ### Option 2 — npm
 
@@ -112,23 +113,29 @@ and you may need to **restart** it for the bar to appear.
 
 ### Uninstall
 
-Plugin users:
+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):
 ```
-/cc-cream:uninstall
-/plugin uninstall cc-cream
+/cc-cream:uninstall          # removes the statusLine wiring
+/plugin uninstall cc-cream   # drops the plugin from the cache
 ```
 
 npm / manual users:
 ```bash
-cc-cream-setup --uninstall                 # npm (add --purge to also remove config)
+cc-cream-setup --uninstall                 # npm (add --purge to also remove runtime + config)
 node cc-cream/src/install.js --uninstall   # manual clone
 ```
 
 Uninstall removes the `statusLine` block **only if it is cc-cream's** — a
-statusLine you wired for something else is left untouched. It then offers to
-delete the copied runtime and session-state files, and **keeps your
-`~/.claude/cc-cream.json` config** unless you add `--purge`. Restart Claude Code
-to clear the bar.
+statusLine you wired for something else is left untouched. In a terminal it asks
+before deleting the copied runtime and session-state files; run **non-interactively**
+(as the `/cc-cream:uninstall` slash command does) it leaves those artifacts in
+place — pass `--purge` to remove them and your `~/.claude/cc-cream.json` config.
+Restart Claude Code to clear the bar.
+
+Likewise, `cc-cream-setup` run non-interactively will overwrite an existing
+*cc-cream* statusLine but never a foreign one — pass `--force` to replace
+regardless.
 
 ## Configuration
 

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "cc-cream",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Claude Code cache/context/cost status-line tool",
   "directories": {
     "doc": "docs"
   },
   "scripts": {
-    "lint": "biome lint src/",
+    "lint": "biome lint src/ hooks/",
     "knip": "knip",
     "validate": "command -v claude >/dev/null 2>&1 && claude plugin validate . || echo 'cc-cream: claude CLI not found — skipping plugin validation'",
     "pretest": "npm run lint && npm run knip && npm run validate",

package/src/install.js

@@ -223,12 +223,22 @@ async function uninstall({ purge }) {
 
   const artifacts = [runtimeDir, stateFile].filter((p) => fs.existsSync(p));
   if (artifacts.length) {
-    const remove = purge || (await ask(`Also delete the copied runtime and session state?\n  ${artifacts.join('\n  ')}`));
+    let remove = purge;
+    if (!remove && process.stdin.isTTY) {
+      remove = await ask(`Also delete the copied runtime and session state?\n  ${artifacts.join('\n  ')}`);
+    }
     if (remove) {
       for (const p of artifacts) fs.rmSync(p, { recursive: true, force: true });
       console.log('Removed runtime and state files.');
-    } else {
+    } else if (process.stdin.isTTY) {
       console.log('Left runtime and state files in place.');
+    } else {
+      // Non-interactive (e.g. run via the /cc-cream:uninstall slash command, which
+      // has no TTY): never block on a prompt. The statusLine — the thing that
+      // matters — is already removed; keep the artifacts (deletion is destructive)
+      // and say how to remove them.
+      console.log(`Left runtime and session state in place — no terminal to confirm deletion:\n  ${artifacts.join('\n  ')}`);
+      console.log('Re-run in a terminal, or pass --purge, to remove them.');
     }
   }
   if (purge && fs.existsSync(configFile)) {
@@ -248,6 +258,7 @@ async function main() {
     return;
   }
   const plugin = args.includes('--plugin');
+  const force = args.includes('--force') || args.includes('--yes');
   // First non-flag arg is an optional local source path (manual mode only).
   const positional = args.filter((a) => !a.startsWith('--'));
 
@@ -284,7 +295,19 @@ async function main() {
   // If a replace needs consent, ask now and re-plan with the answer.
   if (!result.changed && result.needsConsent) {
     for (const m of result.messages) console.log(m);
-    const yes = await ask('Replace it with cc-cream?');
+    let yes;
+    if (process.stdin.isTTY) {
+      yes = await ask('Replace it with cc-cream?');
+    } else {
+      // Non-interactive (e.g. run via the /cc-cream:setup slash command, which has
+      // no TTY): never block on a prompt. Safe to overwrite our OWN wiring (an
+      // older/other-strategy cc-cream statusLine); never clobber a FOREIGN
+      // statusLine without a terminal or an explicit --force.
+      yes = force || isCcCreamStatusLine(settings.statusLine);
+      console.log(yes
+        ? 'Non-interactive: replacing the existing cc-cream statusLine.'
+        : 'Non-interactive: left your existing statusLine unchanged. Re-run in a terminal, or pass --force, to replace it.');
+    }
     result = plan(settings, { ...planOpts, consent: yes });
   }