From 40a6a3ce76039ab93c2a3360e46616d2fc70e4a3 Mon Sep 17 00:00:00 2001
From: zeroaltitude <zeroaltitude@gmail.com>
Date: Sun, 8 Mar 2026 16:58:34 -0700
Subject: [PATCH] fix(session-memory): use displaySessionKey instead of
 event.sessionKey in entry
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The resolveDisplaySessionKey function correctly resolved workspace-based
agent IDs (e.g. agent:main:main → agent:navi:main when workspaceDir
matches the navi agent), but the entry template used event.sessionKey
directly, bypassing the resolution.
---
 src/hooks/bundled/session-memory/handler.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/hooks/bundled/session-memory/handler.ts b/src/hooks/bundled/session-memory/handler.ts
index fe4736c5bbc..4de19361545 100644
--- a/src/hooks/bundled/session-memory/handler.ts
+++ b/src/hooks/bundled/session-memory/handler.ts
@@ -366,7 +366,7 @@ const saveSessionToMemory: HookHandler = async (event) => {
       const entryParts = [
         `# Session: ${dateStr} ${timeStr} UTC`,
         "",
-        `- **Session Key**: ${event.sessionKey}`,
+        `- **Session Key**: ${displaySessionKey}`,
         `- **Session ID**: ${sessionId}`,
         `- **Source**: ${source}`,
         "",