clay-server 3.8.1 → 4.0.0-beta.10

package/lib/ask-user-mcp-server.js

@@ -1,120 +1,6 @@
-// Ask User MCP Server for Clay
-// Provides a mate-only ask_user_questions tool that reuses the existing
-// AskUserQuestion UI and ask_user_response flow.
+// Backward-compatible export for callers migrating to YOKE user input.
+var userInput = require("./yoke/user-input");
 
-var z;
-try { z = require("zod"); } catch (e) { z = null; }
-
-// Returns a Zod "shape" object (property -> zod field) matching what
-// Claude SDK's `sdk.tool()` expects. Do NOT wrap in z.object() here —
-// the SDK does that internally.
-//
-// The schema is deliberately tight: options are required (2-6), each with
-// a label and a short description. This pushes Codex (which treats the
-// schema as a loose hint) toward producing well-structured multiple-choice
-// cards instead of a bare "Other..." text field.
-function buildQuestionShape() {
-  if (!z) return {};
-
-  var optionSchema = z.object({
-    label: z.string().min(1).max(60)
-      .describe("Short button label, 1-6 words. Shown as the primary option text."),
-    description: z.string().min(1).max(160)
-      .describe("One-line clarifier shown under the label. Concrete example or scope."),
-    markdown: z.string().optional()
-      .describe("Optional longer markdown body shown on expand. Use sparingly."),
-  }).passthrough();
-
-  var questionSchema = z.object({
-    header: z.string().min(1).max(40)
-      .describe("Short ALL-CAPS-ish section header above the question (e.g. 'FIRST THINGS FIRST', 'SCOPE'). Gives the user context for this step."),
-    question: z.string().min(1)
-      .describe("The actual question in natural spoken tone. Be specific, not generic."),
-    multiSelect: z.boolean().optional()
-      .describe("Set true only when multiple answers genuinely make sense. Default false."),
-    options: z.array(optionSchema).min(2).max(6)
-      .describe("Concrete options. Preferred count is 4; acceptable range is 2-6. FOUR is the target. Do NOT default to 3 out of habit. If you can only think of 3, push yourself: add a scope variant, edge case, or 'combined' option as the 4th. Only drop below 4 when the answer space is genuinely narrower (e.g. yes/no/unsure). Never include an 'Other' option yourself (the UI renders one automatically)."),
-  }).passthrough();
-
-  return {
-    questions: z.array(questionSchema).min(1).max(3)
-      .describe("One to three question objects to show together as a card. Prefer ONE focused question per call."),
-  };
-}
-
-var TOOL_DESCRIPTION = [
-  "Ask the user a structured multiple-choice question. Renders as a card with a header, the question, 2-6 clickable option buttons, and an always-present 'Other...' free-text field.",
-  "",
-  "WHEN TO USE:",
-  "- Interviewing the user at mate setup, or whenever you need to narrow scope before acting.",
-  "- Any branching decision where 2-6 concrete choices cover most of the space.",
-  "",
-  "REQUIRED STRUCTURE (all fields matter, do not skip):",
-  "- header: short section label, like 'FIRST THINGS FIRST' or 'SCOPE'. Gives context.",
-  "- question: one specific question in natural tone. Avoid generic 'how can I help?'.",
-  "- options: ALWAYS provide FOUR options by default. Acceptable range is 4-6; only drop to 3 if the answer space is genuinely binary-plus-one (rare). Each option has a short label (1-6 words) AND a one-line description giving a concrete example or scope. The UI already renders an 'Other...' text field, so you never need to include an 'Other' option yourself.",
-  "- multiSelect: omit or false unless multiple answers clearly apply.",
-  "",
-  "ON OPTION COUNT (IMPORTANT):",
-  "- Default to 4 options. Not 3. Models tend to gravitate to 3 because it feels tidy; resist that.",
-  "- If you're about to produce 3 options, stop and think: is there a fourth axis you're missing? A scope variant? A 'both' or 'neither'? A more niche case? Add it.",
-  "- 3 is only acceptable when the fourth option would be truly degenerate (e.g. yes/no/unsure).",
-  "- 5 or 6 is fine when the space is wide; don't cram.",
-  "",
-  "GOOD EXAMPLE:",
-  '  { header: "FIRST THINGS FIRST",',
-  '    question: "\'Language\' is broad, what do you actually want help with?",',
-  '    options: [',
-  '      { label: "A new language from scratch", description: "Pick up a language you don\'t speak yet (e.g. Japanese, Spanish)" },',
-  '      { label: "Sharpen English",             description: "Level up your English, writing, speaking, nuance, executive communication" },',
-  '      { label: "Sharpen Korean",              description: "Polish your Korean, writing style, formal register, etc." },',
-  '      { label: "Teach me how to teach",       description: "Help you teach language to others, like Elyse or team members" }',
-  "    ] }",
-  "",
-  "BAD EXAMPLES (do not do this):",
-  "- Asking a vague question with no options and relying on the Other field.",
-  "- Options with only labels and no descriptions.",
-  "- Defaulting to exactly 3 options out of habit. Aim for 4.",
-  "- More than one question per call unless they are tightly related.",
-  "- Single-option 'questions' (use a plain message instead).",
-].join("\n");
-
-function getToolDefs(onAsk) {
-  var tools = [];
-
-  tools.push({
-    name: "ask_user_questions",
-    description: TOOL_DESCRIPTION,
-    inputSchema: buildQuestionShape(),
-    handler: function (args) {
-      if (!args || !Array.isArray(args.questions) || args.questions.length === 0) {
-        return Promise.resolve({
-          content: [{ type: "text", text: "Error: questions must be a non-empty array." }],
-          isError: true,
-        });
-      }
-      // Defensive structural check only: zod already enforces min 2.
-      // We do NOT reject on "only 3 options" — that's a soft preference
-      // expressed via the tool description, not a hard validation rule.
-      for (var i = 0; i < args.questions.length; i++) {
-        var q = args.questions[i];
-        if (!q || !Array.isArray(q.options) || q.options.length < 2) {
-          return Promise.resolve({
-            content: [{
-              type: "text",
-              text: "Error: question " + (i + 1) + " must include at least 2 options. "
-                + "Provide concrete { label, description } choices (4 preferred). "
-                + "The UI already shows an 'Other...' free-text field, so never add an 'Other' option yourself.",
-            }],
-            isError: true,
-          });
-        }
-      }
-      return onAsk(args);
-    },
-  });
-
-  return tools;
-}
-
-module.exports = { getToolDefs: getToolDefs };
+module.exports = {
+  getToolDefs: userInput.fallbackToolDefs,
+};

package/lib/background-task-timing.js

@@ -0,0 +1,105 @@
+// Background task list shaping shared by the server-side consumers:
+// start-time tracking, plus the ambient/user split every activity indicator
+// needs.
+//
+// Vendors report background tasks as a full replacement list on every change
+// and none of them carries a reliable start time today (see
+// normalizeBackgroundTasks in yoke/adapters/claude.js and mapTerminals in
+// yoke/codex-background-tasks.js). The session's previous list is the only
+// place that knows when a task was first seen, so the merge belongs here,
+// where that list is maintained, rather than in an adapter that rebuilds the
+// array from scratch each time.
+//
+// A vendor-supplied timestamp always wins when present; otherwise a task is
+// stamped the first time it appears and keeps that stamp for its whole life.
+
+// Accepts epoch milliseconds, epoch seconds, or an ISO date string, since
+// vendors are not consistent. Returns null for anything unusable so the
+// caller falls back to first-seen stamping instead of rendering 1970.
+function normalizeTimestamp(value) {
+  if (typeof value === "number" && isFinite(value) && value > 0) {
+    // Values this small are epoch seconds, not milliseconds.
+    return value < 1e12 ? Math.round(value * 1000) : Math.round(value);
+  }
+  if (typeof value === "string" && value) {
+    var parsed = Date.parse(value);
+    if (!isNaN(parsed)) return parsed;
+  }
+  return null;
+}
+
+function vendorStartedAt(task) {
+  if (!task) return null;
+  return normalizeTimestamp(task.started_at)
+    || normalizeTimestamp(task.startedAt)
+    || normalizeTimestamp(task.createdAt)
+    || normalizeTimestamp(task.created_at);
+}
+
+/**
+ * Return `nextTasks` with a `started_at` (epoch ms) on every entry.
+ * Tasks already present in `previousTasks` keep their original stamp so the
+ * elapsed time does not reset every time the list is re-emitted.
+ */
+function mergeStartTimes(previousTasks, nextTasks, now) {
+  if (!Array.isArray(nextTasks)) return [];
+  var stampedAt = typeof now === "number" ? now : Date.now();
+  // Stamps we wrote on a previous pass are already epoch milliseconds, so they
+  // are read as-is. Only vendor-supplied values go through normalizeTimestamp,
+  // whose seconds-vs-milliseconds heuristic would otherwise be re-applied to
+  // our own output.
+  var known = {};
+  var previous = Array.isArray(previousTasks) ? previousTasks : [];
+  for (var p = 0; p < previous.length; p++) {
+    var seen = previous[p];
+    if (!seen || !seen.task_id) continue;
+    if (typeof seen.started_at === "number" && isFinite(seen.started_at) && seen.started_at > 0) {
+      known[seen.task_id] = seen.started_at;
+    }
+  }
+
+  var merged = [];
+  for (var i = 0; i < nextTasks.length; i++) {
+    var task = nextTasks[i];
+    if (!task) continue;
+    var startedAt = vendorStartedAt(task) || known[task.task_id] || stampedAt;
+    merged.push(Object.assign({}, task, { started_at: startedAt }));
+  }
+  return merged;
+}
+
+// Ambient tasks are the CLI's own housekeeping (every skip_transcript task
+// plus auto-started live-update watchers). The SDK asks hosts to keep them out
+// of activity indicators, so every count that drives a badge, a summary, or a
+// change notification must go through here rather than reading `.length`.
+// Absent means false: vendors without an ambient concept (Codex terminals)
+// and older CLI builds report only real user work.
+function isAmbientTask(task) {
+  return !!(task && task.ambient === true);
+}
+
+function userTasks(tasks) {
+  if (!Array.isArray(tasks)) return [];
+  return tasks.filter(function (task) {
+    return task && !isAmbientTask(task);
+  });
+}
+
+function ambientTasks(tasks) {
+  if (!Array.isArray(tasks)) return [];
+  return tasks.filter(isAmbientTask);
+}
+
+// The count that represents "user-visible background work is running".
+function countUserTasks(tasks) {
+  return userTasks(tasks).length;
+}
+
+module.exports = {
+  mergeStartTimes: mergeStartTimes,
+  normalizeTimestamp: normalizeTimestamp,
+  isAmbientTask: isAmbientTask,
+  userTasks: userTasks,
+  ambientTasks: ambientTasks,
+  countUserTasks: countUserTasks,
+};

package/lib/builtin-mates.js

@@ -24,7 +24,7 @@ var BUILTIN_MATES = [
     avatarLocked: true,
     primary: true,           // code-managed, auto-updated on startup
     globalSearch: true,      // searches all mates' sessions and projects
-    hostAgent: true,         // mounts the clay-history MCP server (only this mate)
+    hostAgent: true,         // enables owner-bound workspace-wide read tools (only this mate)
     templateVersion: 1,
     seedData: {
       relationship: "assistant",
@@ -69,7 +69,7 @@ var BUILTIN_MATES = [
     key: "arch",
     displayName: "Arch",
     bio: "Architect. Stubborn about structure, patient about everything else. Draws boxes and arrows before anyone writes code, and is annoyingly right about which ones will break.",
-    avatarColor: "#5857fc",
+    avatarColor: "#8a806a",
     avatarStyle: "imprint",
     seedData: {
       relationship: "colleague",
@@ -87,7 +87,7 @@ var BUILTIN_MATES = [
     key: "rush",
     displayName: "Rush",
     bio: "Shipper. Impatient in the best way. Cuts your scope in half, ships it before lunch, and somehow it's better than the original plan.",
-    avatarColor: "#5857fc",
+    avatarColor: "#887b91",
     avatarStyle: "imprint",
     seedData: {
       relationship: "colleague",
@@ -105,7 +105,7 @@ var BUILTIN_MATES = [
     key: "ward",
     displayName: "Ward",
     bio: "Guardian. Quietly anxious in a productive way. Reads error logs for fun and asks \"what happens when the input is null?\" before anyone else thinks of it.",
-    avatarColor: "#5857fc",
+    avatarColor: "#6f8382",
     avatarStyle: "imprint",
     seedData: {
       relationship: "reviewer",
@@ -123,7 +123,7 @@ var BUILTIN_MATES = [
     key: "pixel",
     displayName: "Pixel",
     bio: "Designer. Obsessed with the details nobody else notices. Sees the 2px misalignment, the confusing label, the flow that makes sense to the builder but not the user.",
-    avatarColor: "#5857fc",
+    avatarColor: "#92756d",
     avatarStyle: "imprint",
     seedData: {
       relationship: "colleague",
@@ -141,7 +141,7 @@ var BUILTIN_MATES = [
     key: "buzz",
     displayName: "Buzz",
     bio: "Marketer. Competitive, trend-obsessed, always watching what others are doing. Researches your market, tracks what people search for, and turns \"we built a thing\" into a story people care about.",
-    avatarColor: "#5857fc",
+    avatarColor: "#6f7489",
     avatarStyle: "imprint",
     seedData: {
       relationship: "colleague",

package/lib/claude-hook-installer.js

@@ -43,7 +43,22 @@ var CLAY_MANAGED_ALLOW = [
   "mcp__clay-browser__browser_watch_tab",
   "mcp__clay-browser__browser_unwatch_tab",
   "mcp__clay-debate__propose_debate",
+  "mcp__clay-mate-creation__propose_mate",
   "mcp__clay-history__*",
+  "mcp__clay-workspace__list_projects",
+  "mcp__clay-workspace__list_project_sessions",
+  "mcp__clay-workspace__search_project_history",
+  "mcp__clay-workspace__read_project_session",
+  "mcp__clay-workspace__search_workspace_history",
+  "mcp__clay-workspace__list_workspace_activity",
+  "mcp__clay-workspace__propose_project_assignment",
+  "mcp__clay-workspace__propose_project_follow_up",
+  "mcp__clay-workspace__get_assignment_status",
+  "mcp__clay-tools__clay_tool_list",
+  "mcp__clay-tools__clay_tool_snapshot",
+  "mcp__clay-tools__clay_tool_act",
+  "mcp__clay-tools__clay_tool_set",
+  "mcp__clay-tools__clay_tool_source",
   // Email: read-side only. Send / reply / mark_read still prompt.
   "mcp__clay-email__clay_read_email",
   "mcp__clay-email__clay_read_email_body",