memhouse 0.18.8 → 0.18.9

package/memhouse/delivery/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mem",
   "description": "Conversation memory for AI agents over the memhouse typed ClickHouse store: recall past sessions and answer from them, run analytics, check the house, bring people in, and administer the server. Skills install as /mem:recall, /mem:sql, /mem:house, /mem:access, and /mem:admin.",
-  "version": "0.18.8",
+  "version": "0.18.9",
   "author": {
     "name": "Ramazan Polat"
   },

package/memhouse/server/queries.js

@@ -471,10 +471,24 @@ async function getChats(opts = {}) {
   // Price the fifty rows on the page, not the twelve hundred in the house. This query
   // set was the most expensive thing the dashboard ran — 1,413,624 rows read and 272 MiB
   // per call, three endpoints calling it — and getChats used ~4% of what it asked for.
-  const perChat = await computePerChatCosts(f, {
-    ids: rows.map((r) => String(r.id)),
-    users: rows.map((r) => String(r.user_id)),
-  });
+    // In CHUNKS. The scope travels as `{scopeIds:Array(String)}` query parameters, and the
+    // driver puts query parameters in the REQUEST URI — so a page of N sessions builds a URI
+    // of roughly 60 bytes per id, twice (ids and users). Zeo is reached through a Cloudflare
+    // tunnel, which rejects a URI far below ClickHouse's own 1 MiB `http_max_uri_size`: at
+    // 925 sessions the request came back 500 with an EMPTY message (the driver reports a
+    // transport-level refusal as `new Error('')`), so `/api/chats?limit=1000` — exactly what
+    // the Sessions page asks for — returned 500 and the page rendered blank. 900 worked,
+    // 925 did not. Chunked, the URI stays small whatever the page size, and the per-chunk
+    // results merge because each chunk is disjoint by construction.
+    const COST_SCOPE_CHUNK = 250;
+    const perChat = [];
+    for (let i = 0; i < rows.length; i += COST_SCOPE_CHUNK) {
+      const slice = rows.slice(i, i + COST_SCOPE_CHUNK);
+      perChat.push(...await computePerChatCosts(f, {
+        ids: slice.map((r) => String(r.id)),
+        users: slice.map((r) => String(r.user_id)),
+      }));
+    }
   const costBySession = {};
   const topModelBySession = {};
   for (const r of perChat) {

package/memhouse/server/server.js

@@ -49,7 +49,15 @@ function parseDateOpts(query) {
 
 // Route helper: async handler with the uniform 500 shape.
 const route = (fn) => async (req, res) => {
-  try { await fn(req, res); } catch (err) { res.status(500).json({ error: err.message }); }
+  try { await fn(req, res); } catch (err) {
+    // `{"error":""}` and nothing in the log was the whole diagnosis for a 500 that made the
+    // Sessions page render blank: the ClickHouse driver reports a transport-level refusal as
+    // `new Error('')` — no message, no code, no own keys. An empty error is a dead end for
+    // whoever is looking, so say what we do know: the class of failure and the route.
+    const why = (err && err.message) || (err && err.code) || `${err && err.constructor ? err.constructor.name : 'Error'} with no message — often the server or a proxy in front of it refusing the request (URI too long, body too large, timeout)`;
+    console.error(`[memhouse] ${req.method} ${req.originalUrl} failed: ${why}`);
+    res.status(500).json({ error: String(why) });
+  }
 };
 
 app.get('/api/ping', (req, res) => res.json({ app: 'agentlytics', pid: process.pid }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memhouse",
-  "version": "0.18.8",
+  "version": "0.18.9",
   "description": "memhouse \u2014 agent conversation memory across 17 editors: parse-on-client shippers, a typed ClickHouse store with one set of rooms per member, kernel-agency install, and the agentlytics dashboard",
   "main": "bin/memhouse.js",
   "bin": {