@particle-academy/prism-acp 0.4.0 → 0.4.1

package/README.md

@@ -172,6 +172,23 @@ proceeds exactly as it did before. Calling a real session absent would refuse a
 resume that would have worked, which is worse than the late error this replaces;
 that error is still there as the backstop.
 
+**It looks where the CLI looks, including `CLAUDE_CONFIG_DIR`.** The CLI resolves
+its configuration home as that variable or, unset, `<home>/.claude`, and keeps
+`projects` under whichever it picked — so the probe does the same. This is not a
+detail: an installation that sets it does so because the stored subscription
+credential lives there, which is exactly the installation whose resumes matter,
+and reading the wrong store would report a real conversation `absent` and refuse
+a resume that would have worked.
+
+`childEnv` passes that variable through unchanged, so a driver spawned from this
+process resolves the same store the probe read, by construction. Hand the driver
+a `parentEnv` you built yourself and hand the same environment to the probe, or
+name the store outright:
+
+```ts
+const probeSession = (sessionId: string) => probeSessionStore(sessionId, { env: parentEnv });
+```
+
 `probeSession` is yours to supply because the answer belongs to the agent being
 driven, not to ACP: `probeSessionStore` reads claude's session store, and a Codex
 driver would resolve the same question through `thread/resume`. Omit it and

package/dist/claude/session-store.d.ts

@@ -15,5 +15,20 @@ export interface SessionProbe {
 export interface SessionStoreOptions {
     /** Overridable so tests never read the developer's real sessions. */
     readonly home?: string;
+    /**
+     * The CLI's configuration home, naming the store directly. Outranks both
+     * {@link home} and the environment -- for a caller that knows where the store
+     * is, or that builds the driven CLI's environment itself.
+     */
+    readonly configDir?: string;
+    /**
+     * The environment the DRIVEN CLI will see, read for `CLAUDE_CONFIG_DIR`.
+     *
+     * Defaults to this process's own, which is correct by construction when the
+     * driver is spawned from here: `childEnv` passes `CLAUDE_CONFIG_DIR` through
+     * unchanged, so the probe and the child resolve one store. Hand the driver a
+     * `parentEnv` of your own and hand the same one here, or they will not.
+     */
+    readonly env?: Readonly<Record<string, string | undefined>>;
 }
 export declare function probeSessionStore(sessionId: string, options?: SessionStoreOptions): SessionProbe;

package/dist/claude/session-store.js

@@ -26,9 +26,51 @@
 // every project, so looking for the FILE is enough and needs no slug at all.
 import { readdirSync, statSync } from 'node:fs';
 import { homedir } from 'node:os';
-import { join } from 'node:path';
+import { isAbsolute, join } from 'node:path';
 /** The CLI accepts a UUID, or a session TITLE, and nothing else. */
 const UUID = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
+/**
+ * WHERE THE STORE IS. The CLI resolves its configuration home as
+ * `CLAUDE_CONFIG_DIR` or, unset, `<home>/.claude`, and keeps `projects` under
+ * whichever it picked.
+ *
+ * Reading only the second was this probe's one serious bug (0.4.0). An
+ * installation that sets the variable -- Genie forwards it deliberately,
+ * because the stored subscription credential lives there and is what lets a
+ * child run with no API key at all -- had the probe read a store the CLI does
+ * not use, find nothing, and report `absent` for a conversation that exists.
+ * That refuses a resume that would have worked: the failure this whole
+ * three-state design exists to avoid, reintroduced by the check meant to
+ * prevent it.
+ *
+ * The variable names the configuration home ITSELF, so `projects` sits directly
+ * inside it and no `.claude` is appended. Resolving it as
+ * `home: dirname(CLAUDE_CONFIG_DIR)` instead would work only while the
+ * directory happens to be named `.claude`.
+ */
+function storeRoot(options) {
+    const configured = options.configDir ?? (options.env ?? process.env).CLAUDE_CONFIG_DIR;
+    const trimmed = configured?.trim();
+    // The CLI reads it with `||`, so an empty or blank value is no value. Taking
+    // it literally would resolve `projects` against this process's working
+    // directory.
+    if (trimmed === undefined || trimmed === '') {
+        return { root: join(options.home ?? homedir(), '.claude', 'projects') };
+    }
+    // The CLI refuses to run at all with a relative configuration home -- "the
+    // configuration home (CLAUDE_CONFIG_DIR) is not an absolute path" -- so there
+    // is no store to name, and resolving it against our own cwd would answer
+    // about a directory the CLI never looks in. It is also not a case for the
+    // `<home>/.claude` fallback: the CLI will not fall back either.
+    if (!isAbsolute(trimmed)) {
+        // The value itself stays out of the message. Every other `detail` here
+        // names the path it looked at, which is useful and harmless for a path we
+        // derived; this one is an environment value, and a detail string travels to
+        // the client.
+        return { reason: 'CLAUDE_CONFIG_DIR is not an absolute path, so the session store it names cannot be located' };
+    }
+    return { root: join(trimmed, 'projects') };
+}
 export function probeSessionStore(sessionId, options = {}) {
     // A non-UUID is refused by the CLI outright -- verified against claude
     // 2.1.292: "Provided value ... is not a UUID and does not match any session
@@ -45,7 +87,10 @@ export function probeSessionStore(sessionId, options = {}) {
             detail: `${sessionId} is not a session id the CLI can resume: it is not a UUID.`,
         };
     }
-    const root = join(options.home ?? homedir(), '.claude', 'projects');
+    const resolved = storeRoot(options);
+    if ('reason' in resolved)
+        return { existence: 'indeterminate', detail: resolved.reason };
+    const { root } = resolved;
     let projects;
     try {
         if (!statSync(root).isDirectory()) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/prism-acp",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Speak the Agent Client Protocol to a coding-agent CLI the user has already authenticated. No API key, no third-party adapter.",
   "license": "MIT",
   "repository": {