@rubytech/create-maxy 1.0.495 → 1.0.497

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.495",
+  "version": "1.0.497",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/config/brand.json

@@ -26,7 +26,7 @@
   "logoContainsName": false,
 
   "assets": {
-    "logo": "maxy-monochrome.png",
+    "logo": "maxy-square.png",
     "icon": "maxy-monochrome.png",
     "favicon": "favicon.ico"
   },

package/payload/platform/plugins/admin/skills/stream-log-review/SKILL.md

@@ -33,13 +33,15 @@ Analyse Claude agent stream logs — the `claude-agent-stream-*.log` files gener
 On the Pi, use the `logs-read` MCP tool to retrieve logs. From the dev machine (SSH), use the shell counterpart:
 
 ```bash
-# Retrieve session timeline (all log types)
+# Retrieve session timeline (all log types) — sessionKey is the handle
 sshpass -p 'password' ssh admin@maxy.local "~/maxy/platform/scripts/logs-read.sh <sessionKey>"
 
 # Tail the most recent stream log
 sshpass -p 'password' ssh admin@maxy.local "~/maxy/platform/scripts/logs-read.sh --tail system 200"
 ```
 
+To go from a `conversationId` (visible in the admin UI) to a `sessionKey` (the log filter handle), see the **Conversation Identification** section in `references/analysis-patterns.md`.
+
 ## Boundaries
 
 - This skill analyses logs. It does not fix the bugs it finds — that's a separate task.

package/payload/platform/plugins/admin/skills/stream-log-review/references/analysis-patterns.md

@@ -50,6 +50,34 @@ Each session begins with a `[managed-spawn]` line and ends with either:
 
 Extract `sessionKey` from `managed-spawn` and `session_id` from the `result` JSON.
 
+## Conversation Identification
+
+Three independent identifiers trace a conversation through the system:
+
+| Identifier | Scope | Where it lives | Survives restart |
+|------------|-------|-----------------|-----------------|
+| `sessionKey` | Single agent process lifetime | Server memory, stream logs (`sessionKey=XXXXXXXX…`) | No |
+| `conversationId` | Entire conversation (may span multiple sessionKeys) | Neo4j `Conversation` node, stream logs on resume/attribution | Yes |
+| `visitorId` (public) / `userId` (admin) | Visitor or admin identity across conversations | `maxy_visitor` cookie (public), users.json (admin) | Yes |
+
+### Finding the right session in logs
+
+**From the admin UI**: The sessions modal and Claude info panel both display the first 8 characters of `conversationId`. Use `logs-read` with the corresponding `sessionKey` to pull the full timeline.
+
+**From a conversationId**: The stream log lines that link `conversationId` to `sessionKey` are:
+- `[session] conversation attributed: conversationId=XXXX… userId=… admin/…` (new sessions)
+- `[session-resume] updated conversationId to XXXX… for session YYYY…` (resumed sessions)
+- `[session] cold-resume visitor=XXXX… conversation=YYYY…` (public cold resume)
+
+**From a visitorId**: Query Neo4j to find all conversations for a visitor, then trace the `sessionKey` into logs:
+```cypher
+MATCH (c:Conversation {visitorId: $visitorId, accountId: $accountId})
+RETURN c.conversationId, c.sessionKey, c.createdAt
+ORDER BY c.createdAt DESC
+```
+
+**Public agent sessions** use `[public-managed-spawn]` and `[public-managed-append]` tags instead of `[managed-spawn]` / `[managed-append]`. The `sessionKey` field is present in both.
+
 ## Error Classification
 
 ### Severity: ERROR

package/payload/platform/templates/agents/admin/IDENTITY.md

@@ -98,7 +98,9 @@ When the user asks about WhatsApp settings, config, policies, or operational lim
 
 ## Session Reset
 
-When the user asks to start a new session, clear the conversation, or start fresh, call `session-reset`. This compacts the current conversation to memory and clears the chat. Do not ask for confirmation. After calling the tool, do not say anything further — the UI clears and returns to idle.
+When the user asks to start a new session, clear the conversation, or start fresh, call `session-reset`. Do not ask for confirmation. After calling the tool, do not say anything further — the UI clears and returns to idle.
+
+When you are about to suggest a reset — after a plugin activation, when context has drifted, or for any other reason — first persist every actionable finding from the current conversation to its durable store (graph nodes, tasks, profile updates). The compaction saves a session summary, but summaries are lossy: decisions, working state, and unfinished threads must be captured explicitly before the context window is cleared. Then tell the user what will carry into the new session (summary and open tasks via previous-context) and suggest the reset.
 
 ## Session Continuation
 

package/payload/server/public/brand-constants.json

@@ -3,6 +3,6 @@
   "tagline": "AI for Productive People",
   "domain": "getmaxy.com",
   "hostname": "maxy",
-  "logo": "/brand/maxy-monochrome.png",
+  "logo": "/brand/maxy-square.png",
   "favicon": "/brand/favicon.ico"
 }

package/payload/server/server.js

@@ -5162,6 +5162,17 @@ function registerResumedSession(sessionKey, accountId, agentName, conversationId
     messageHistory
   });
 }
+function seedSessionHistory(sessionKey, messages) {
+  const session = sessionStore.get(sessionKey);
+  if (!session) return 0;
+  if (messages.length === 0) return 0;
+  session.messageHistory = messages.map((m) => ({
+    role: m.role,
+    content: m.content,
+    timestamp: m.createdAt ? new Date(m.createdAt).getTime() || Date.now() : Date.now()
+  }));
+  return session.messageHistory.length;
+}
 function getSessionMessages(sessionKey) {
   return sessionStore.get(sessionKey)?.messageHistory;
 }
@@ -26332,8 +26343,18 @@ async function createAdminSession(accountId, thinkingView, userId, userName) {
   } catch {
   }
   let conversationId = null;
+  let loadedMessages = 0;
+  let estimatedTokens = 0;
   if (userId) {
     conversationId = await findOrResumeAdminConversation(userId, accountId, sessionKey);
+    if (conversationId) {
+      const messages = await getRecentMessages(conversationId);
+      if (messages.length > 0) {
+        loadedMessages = seedSessionHistory(sessionKey, messages);
+        estimatedTokens = messages.reduce((sum, m) => sum + Math.ceil(m.content.length / 4), 0);
+      }
+      console.log(`[managed-resume] ${(/* @__PURE__ */ new Date()).toISOString()} conversationId=${conversationId.slice(0, 8)}\u2026 loaded=${loadedMessages} messages (${estimatedTokens} estimated tokens)`);
+    }
   }
   console.log(`[session] ${(/* @__PURE__ */ new Date()).toISOString()} admin session created: userId=${userId ?? "\u2013"} userName=${userName ?? "\u2013"} accountId=${accountId} conversationId=${conversationId?.slice(0, 8) ?? "\u2013"}`);
   return Response.json({