context-carwash 0.1.6 → 0.1.7

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.1.7
+
+- `carwash doctor` checks that the Node Carwash runs with is still there, and says how to fix it if not. Removing that Node, for example an old version in nvm, stops the meter and `/wash` until install is run again. The installer now says which Node that is.
+- Clearer wording on when Carwash goes online, and a reminder to look over `doctor` output before posting it in a public issue.
+
 ## 0.1.6
 
 - Update notices: once a day, a new session checks npm in the background. A line under the meter says when a newer version is out, or when the version you have carries a warning. `CARWASH_NO_UPDATE_CHECK=1` turns it off.

package/README.md

@@ -5,7 +5,7 @@ A small, local-first utility for Claude Code.
 - **Meter:** a quiet estimate of the active context window in the status line.
 - **Wash:** when you ask, Claude writes a short handoff brief, and your next `/clear` starts a fresh session that begins with it.
 
-Nothing happens automatically, and nothing about you is ever sent. Carwash goes online in two ways: once a day it reads its own public page on npm to see if a newer version is out (you can turn that off), and `carwash stats --share` sends anonymous totals if you run it and say yes.
+Nothing happens automatically, and nothing about you is ever sent. Carwash goes online only for these: once a day it reads its own public page on npm to see if a newer version is out (you can turn that off); `install` and `doctor` read the same page when you run them, and `install` downloads the newer version if there is one; and `carwash stats --share` sends anonymous totals if you run it and say yes.
 
 **Status:** pre-release. The meter and the typed `/wash` command work today. Clickable links in the status line and the one-step restart are not built yet. See [plan-3.md](plan-3.md) for the design.
 
@@ -30,6 +30,8 @@ The installer copies itself to `~/.carwash/app` and makes three changes to Claud
 
 Start a new Claude Code session afterwards. The first one explains the meter and `/wash` in a short note, shown once.
 
+The status line and hooks run with the Node you installed with. If you later remove that Node, for example an old version in nvm, they stop working until you run install again. `carwash doctor` points this out.
+
 ## The meter
 
 ```text
@@ -114,7 +116,7 @@ This shows every field it would send, and sends only if you say yes. It sends to
 npx context-carwash doctor
 ```
 
-This checks that the status line, hooks and `/wash` command are still in place, and shows your Carwash, Node, Claude Code and operating system versions, the newest version on npm, and the last few errors. Paste it into a [new issue](https://github.com/Spobi/context-carwash/issues/new).
+This checks that the status line, hooks and `/wash` command are still in place and that the Node they run with is still there, and shows your Carwash, Node, Claude Code and operating system versions, the newest version on npm, and the last few errors. Paste it into a [new issue](https://github.com/Spobi/context-carwash/issues/new). Issues are public, so look it over first: error details can include folder names.
 
 If a hook fails, the status line shows `Carwash hit an error` until you run `doctor`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-carwash",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "A quiet context meter and deliberate fresh-session handoff for Claude Code.",
   "license": "MIT",
   "repository": {

package/src/install/doctor.mjs

@@ -6,7 +6,7 @@ import { readJson } from '../files.mjs';
 import { errorLogPath, errorsSeenPath, installRecordPath, settingsPath, skillDir } from '../paths.mjs';
 import { refreshLedger, totals } from '../stats/ledger.mjs';
 import { readyRecords } from '../wash/store.mjs';
-import { isCarwashCommand, isCarwashHook } from './install.mjs';
+import { commandProgram, isCarwashCommand, isCarwashHook } from './install.mjs';
 import { UPDATE_COMMAND } from './notice.mjs';
 import { readSettings, resolveSettingsFile } from './settings.mjs';
 import { isNewer } from './update.mjs';
@@ -59,7 +59,19 @@ function settingsCheck(env) {
   }
   const groups = (event) => (Array.isArray(data?.hooks?.[event]) ? data.hooks[event] : []);
   const hooks = Object.fromEntries(HOOK_EVENTS.map((event) => [event, groups(event).some((group) => Array.isArray(group?.hooks) && group.hooks.some((hook) => isCarwashHook(hook?.command)))]));
-  return { readable: true, statusLine: isCarwashCommand(data?.statusLine?.command), hooks };
+  const hookCommands = HOOK_EVENTS.flatMap((event) => groups(event).flatMap((group) => (Array.isArray(group?.hooks) ? group.hooks.map((hook) => hook?.command) : [])));
+  const ours = [data?.statusLine?.command, ...hookCommands].filter((command) => isCarwashCommand(command) || isCarwashHook(command));
+  return { readable: true, statusLine: isCarwashCommand(data?.statusLine?.command), hooks, nodes: [...new Set(ours.map(commandProgram).filter(Boolean))] };
+}
+
+// The Node that Carwash's commands start. Install writes its path into the
+// settings, so if that Node is removed later (version managers such as nvm
+// keep one folder per version), nothing of Carwash runs, not even the part
+// that would log an error. Plain `node` (Windows) is looked up on PATH.
+function nodeRow(nodes) {
+  const missing = nodes.find((node) => /[\\/]/.test(node) && !existsSync(node));
+  if (missing) return `MISSING: ${tilde(missing)} · to fix: ${UPDATE_COMMAND}`;
+  return nodes.length ? `ok (${nodes.map(tilde).join(', ')})` : null;
 }
 
 const date = (iso) => {
@@ -100,6 +112,8 @@ export function doctorReport({ env = process.env, now = Date.now(), running, new
     } else {
       out.push(row('Status line', yes(check.statusLine)));
       out.push(row('Hooks', HOOK_EVENTS.map((event) => `${event} ${yes(check.hooks[event])}`).join(' · ')));
+      const node = nodeRow(check.nodes);
+      if (node) out.push(row('Node for Carwash', node));
     }
     out.push(row('/wash command', yes(existsSync(join(skillDir(env), 'SKILL.md')))));
     let waiting = '?';
@@ -123,6 +137,7 @@ export function doctorReport({ env = process.env, now = Date.now(), running, new
   if (!errors.length) out.push(`Errors: none logged.`);
   else out.push(`Last ${errors.length === 1 ? 'error' : `${errors.length} errors`} (from ${tilde(errorLogPath(env))}):`, '', ...errors.map((entry) => entry.replace(/^/gm, '  ')));
   out.push('', `Something wrong? Open an issue and paste everything above: ${ISSUES_URL}`);
+  out.push('Issues are public, so look it over first: error details can include folder names.');
   return out.join('\n');
 }
 

package/src/install/install.mjs

@@ -69,6 +69,16 @@ export function commandFor(verb, { nodePath, scriptPath, platform = process.plat
 
 export const statusLineCommand = (options) => commandFor('statusline', options);
 
+// The program a command from commandFor starts, with its quoting undone: the
+// Node it was installed with, or plain `node` on Windows.
+export function commandProgram(command) {
+  const word = /^\s*('(?:[^']|'\\'')*'|"[^"]*"|[^\s'"]+)/.exec(String(command ?? ''))?.[1];
+  if (!word) return null;
+  if (word.startsWith("'")) return word.slice(1, -1).replace(/'\\''/g, "'");
+  if (word.startsWith('"')) return word.slice(1, -1);
+  return word;
+}
+
 const runsCarwash = (verb) => (command) => typeof command === 'string' && new RegExp(`carwash\\.mjs['"]?\\s+${verb}\\s*$`).test(command);
 export const isCarwashCommand = runsCarwash('statusline');
 export const isCarwashHook = runsCarwash('hook');
@@ -178,7 +188,10 @@ export function planInstall({ env = process.env, platform = process.platform } =
   };
   const skill = planSkill(env);
 
-  return { home, appDir, file, settings, record, original, alreadyInstalled, next, skill, keepsHooks: isPlainObject(theirHooks) && Object.keys(theirHooks).length > 0 };
+  // The Node the commands will run with. Windows finds `node` on PATH instead.
+  const node = platform === 'win32' ? null : script.nodePath;
+
+  return { home, appDir, file, settings, record, original, alreadyInstalled, next, skill, node, keepsHooks: isPlainObject(theirHooks) && Object.keys(theirHooks).length > 0 };
 }
 
 export function describeInstall(plan) {
@@ -202,6 +215,9 @@ export function describeInstall(plan) {
   }
   lines.push(`  3. Add the /wash command at ${tilde(plan.skill.dir)}`);
   lines.push('', 'Writing a brief is an ordinary Claude reply, so it uses tokens like any other.');
+  // Version managers such as nvm keep a folder per Node version, so removing
+  // an old version takes this path with it, and nothing of Carwash can start.
+  if (plan.node) lines.push(`Carwash runs with the Node at ${tilde(plan.node)}. If you remove that Node later, for example an old version in nvm, run install again.`);
   lines.push('Nothing else is touched. To undo everything: carwash uninstall');
   return lines.join('\n');
 }

package/src/install/update.mjs

@@ -1,9 +1,9 @@
 import { spawnSync } from 'node:child_process';
 
-// Whether a newer Context Carwash is on npm, and handing over to it. Only the
-// installer asks, since npx can quietly rerun a copy it downloaded earlier, and
-// people should not have to know to type @latest. The meter and /wash never
-// use the network.
+// Whether a newer Context Carwash is on npm, and handing over to it, for the
+// installer: npx can quietly rerun a copy it downloaded earlier, and people
+// should not have to know to type @latest. The daily check behind the update
+// notice is in notice.mjs. The meter and /wash never go online themselves.
 
 const LATEST_URL = 'https://registry.npmjs.org/context-carwash/latest';
 const TIMEOUT_MS = 3000;