clay-server 4.0.0-beta.11 → 4.0.0-beta.12

package/lib/project-session-pair.js

@@ -322,8 +322,7 @@ function attachSessionPair(ctx) {
         title: resolved.partner.title || "New Session",
         turns: count > 0 ? recentTurns(resolved.partner, count) : [],
       };
-      // The same bounded capacity report partner_status returns, so a Driver
-      // already reading turns needs no second call; null for anyone else.
+      // partner_status's bounded report, so reading turns needs no second call.
       payload.capacity = lifecycle.optionalStatus(caller);
       return toolResult(payload);
     } catch (e) {
@@ -411,7 +410,8 @@ function attachSessionPair(ctx) {
       .concat(workerProposal.getToolDefs(boundSession));
   }
 
-  var factory = attachPairFactory({ sm: sm, splitStore: store, ctx: ctx });
+  // Passed through as-is; re-wrapping drops fields. See session-pair-factory.js.
+  var factory = attachPairFactory(ctx);
   var createPairRecord = factory.createPairRecord;
   var createWorkerForDriver = factory.createWorkerForDriver;
   var createPair = factory.createPair;

package/lib/public/modules/tools.js

@@ -203,6 +203,23 @@ export function toolActivityText(name, input) {
   return "Running " + name + "...";
 }
 
+// The sublabel for a call that has finished. `toolActivityText` is written in
+// the present progressive for a call in flight, so re-asserting it after a
+// result has arrived leaves a finished card claiming to still be running —
+// which is how a failed custom tool ended up reading "Running
+// send_to_partner..." beside its own error output.
+//
+// Only ever used where a result exists, so a genuinely in-flight call is never
+// relabelled. A failure states so plainly; a success keeps whatever specific
+// description the activity text produced ("Reading foo.js"), because that still
+// describes the call accurately, and only the generic present-progressive
+// fallback is replaced.
+export function toolTerminalText(name, input, isError) {
+  if (isError) return name + " failed";
+  var activity = toolActivityText(name, input);
+  return activity === "Running " + name + "..." ? name : activity;
+}
+
 function shortPath(p) {
   if (!p) return "";
   var parts = p.split("/");
@@ -2136,9 +2153,12 @@ export function updateToolResult(id, content, isError, images) {
   var tool = tools[id];
   if (!tool) return;
 
+  // Re-render the sublabel from the now-complete input (streaming can have
+  // built it from a partial one), but in its terminal form: a result has
+  // arrived, so this call is no longer running.
   var subtitleText = tool.el.querySelector(".tool-subtitle-text");
   if (subtitleText && tool.input) {
-    subtitleText.textContent = toolActivityText(tool.name, tool.input);
+    subtitleText.textContent = toolTerminalText(tool.name, tool.input, isError);
   }
 
   var resultBlock = document.createElement("div");

package/lib/session-pair-factory.js

@@ -9,6 +9,17 @@
 // Ownership always comes from the connection or the Driver session, never from
 // the incoming message.
 //
+// CONTEXT CONTRACT: this module reads `sm`, `splitStore`, `isMate`,
+// `usersModule` and `sendTo` off its own argument, all at the top level.
+// attachSessionPair's context already carries all five, so it is passed
+// through unchanged. Re-wrapping it (it was once `{ sm, splitStore, ctx }`)
+// leaves `isMate`, `usersModule` and `sendTo` undefined, which silently
+// disables the Mate guard, breaks the pair_session_create reply, and throws
+// "Cannot read properties of undefined (reading 'isMultiUser')" the moment a
+// pair is created for an owned session — single-user installs escape it only
+// because a Driver with no ownerId short-circuits that expression. Add any new
+// dependency as a top-level field of that same context.
+//
 // Two ordering rules matter and are load-bearing:
 //
 //   1. Nothing is created until everything is validated. Driver eligibility and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clay-server",
-  "version": "4.0.0-beta.11",
+  "version": "4.0.0-beta.12",
   "description": "Self-hosted team workspace for Claude Code and Codex. Multi-user, browser-based, with persistent AI mates.",
   "bin": {
     "clay-server": "./bin/cli.js",