@lorekit/cli 1.59.0 → 1.59.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lorekit/cli",
-  "version": "1.59.0",
+  "version": "1.59.1",
   "description": "Install the LoreKit shared-memory skill and run health checks for the LoreKit MCP server.",
   "license": "MIT",
   "repository": {

package/src/adapters/cursor.mjs

@@ -28,7 +28,7 @@ export const cursor = {
       cwd:
         input.cwd ||
         (Array.isArray(input.workspace_roots) ? input.workspace_roots[0] : null),
-      sessionId: input.generation_id || input.conversation_id || null,
+      sessionId: input.conversation_id || input.generation_id || null,
       toolName: 'command',
       toolResponse: null,
       event: input.hook_event_name || null,

package/src/commands/hook.mjs

@@ -109,6 +109,23 @@ async function run(args, meter) {
   const parsed = adapter.parse(input);
   const event = args.event || parsed.event;
 
+  // Every adapter already normalises the host's own session id off the stdin
+  // payload (Claude's `session_id`, Codex's `thread_id`, Cursor's
+  // `conversation_id`). Publishing it as `LOREKIT_SESSION_ID` — the first name
+  // `deriveSessionContext` looks for — is what lets a hook-driven remote read
+  // carry a `correlation_id`, so the dashboard's Runs view can group a session's
+  // reads and writes. It is the AUTHORITATIVE id: the payload says which session
+  // this fire belongs to, whereas an inherited env var only says which process
+  // tree we happen to be in, and Cursor/Codex export nothing at all.
+  //
+  // `||=`, never an overwrite: an explicit LOREKIT_SESSION_ID (or the
+  // LOREKIT_CORRELATION_ID that outranks all of this) is a deliberate override
+  // and must keep winning. Process-local and short-lived — this CLI invocation
+  // handles exactly one hook fire and exits.
+  if (parsed.sessionId && !process.env.LOREKIT_SESSION_ID) {
+    process.env.LOREKIT_SESSION_ID = parsed.sessionId;
+  }
+
   // Harvest the real payload when recording is enabled (opt-in via env).
   recordFixture(args.adapter, event, raw);
 

package/src/shared/mcp.mjs

@@ -231,7 +231,19 @@ export function deriveSessionContext(env = process.env) {
   // Well-known agent-host session id env vars. Best-effort: hosts differ and
   // this is not an exhaustive registry, so an unrecognised host still falls
   // through to `unknown` rather than fabricating an id.
-  const sessionId = firstNonEmptyEnv(env, ['LOREKIT_SESSION_ID', 'CLAUDE_SESSION_ID']);
+  //
+  // `CLAUDE_CODE_SESSION_ID` is the name Claude Code actually exports (verified
+  // against a live session's env); `CLAUDE_SESSION_ID` was a guess and is not
+  // set by any Claude Code version, so before it was joined here EVERY local
+  // Claude session fell through to `unknown` with no correlation id — which is
+  // why `GET /memories/usage/runs` returned an empty list on an account with
+  // ~44K usage events. Kept alongside rather than replaced: it costs nothing,
+  // and dropping a name is how the same blind spot comes back.
+  const sessionId = firstNonEmptyEnv(env, [
+    'LOREKIT_SESSION_ID',
+    'CLAUDE_CODE_SESSION_ID',
+    'CLAUDE_SESSION_ID',
+  ]);
   if (sessionId) {
     // A local session IS known even when the specific id fails the
     // correlation-id charset/length check — report the kind either way, and