@codeagentswarm/cas-cloud 0.0.15 → 0.0.16

package/dist/mcp-stdio-server.js

@@ -1,4 +1,5 @@
 #!/usr/bin/env node
+"use strict";
 var __getOwnPropNames = Object.getOwnPropertyNames;
 var __commonJS = (cb, mod) => function __require() {
   try {
@@ -8,9 +9,9 @@ var __commonJS = (cb, mod) => function __require() {
   }
 };
 
-// src/infrastructure/terminal/sandbox-project-request-store.js
+// ../../src/infrastructure/terminal/sandbox-project-request-store.js
 var require_sandbox_project_request_store = __commonJS({
-  "src/infrastructure/terminal/sandbox-project-request-store.js"(exports2, module2) {
+  "../../src/infrastructure/terminal/sandbox-project-request-store.js"(exports2, module2) {
     "use strict";
     var crypto = require("crypto");
     var fs2 = require("fs");
@@ -83,9 +84,10 @@ var require_sandbox_project_request_store = __commonJS({
   }
 });
 
-// src/infrastructure/platform/platform-config.js
+// ../../src/infrastructure/platform/platform-config.js
 var require_platform_config = __commonJS({
-  "src/infrastructure/platform/platform-config.js"(exports2, module2) {
+  "../../src/infrastructure/platform/platform-config.js"(exports2, module2) {
+    "use strict";
     var os2 = require("os");
     var path2 = require("path");
     var fs2 = require("fs");
@@ -395,9 +397,10 @@ var require_platform_config = __commonJS({
   }
 });
 
-// src/shared/logger/child-process-logger.js
+// ../../src/shared/logger/child-process-logger.js
 var require_child_process_logger = __commonJS({
-  "src/shared/logger/child-process-logger.js"(exports2, module2) {
+  "../../src/shared/logger/child-process-logger.js"(exports2, module2) {
+    "use strict";
     var EventEmitter = require("events");
     var ChildProcessLogger2 = class extends EventEmitter {
       constructor(sourceName) {
@@ -484,9 +487,10 @@ var require_child_process_logger = __commonJS({
   }
 });
 
-// src/infrastructure/platform/platform-utils.js
+// ../../src/infrastructure/platform/platform-utils.js
 var require_platform_utils = __commonJS({
-  "src/infrastructure/platform/platform-utils.js"(exports2, module2) {
+  "../../src/infrastructure/platform/platform-utils.js"(exports2, module2) {
+    "use strict";
     var { execSync } = require("child_process");
     var os2 = require("os");
     var crypto = require("crypto");
@@ -810,9 +814,10 @@ var require_platform_utils = __commonJS({
   }
 });
 
-// src/infrastructure/database/improved-similarity-algorithm.js
+// ../../src/infrastructure/database/improved-similarity-algorithm.js
 var require_improved_similarity_algorithm = __commonJS({
-  "src/infrastructure/database/improved-similarity-algorithm.js"(exports2, module2) {
+  "../../src/infrastructure/database/improved-similarity-algorithm.js"(exports2, module2) {
+    "use strict";
     var ImprovedSimilarityCalculator = class {
       constructor() {
         this.synonymGroups = [
@@ -1054,9 +1059,10 @@ var require_improved_similarity_algorithm = __commonJS({
   }
 });
 
-// src/infrastructure/database/database-mcp-standalone.js
+// ../../src/infrastructure/database/database-mcp-standalone.js
 var require_database_mcp_standalone = __commonJS({
-  "src/infrastructure/database/database-mcp-standalone.js"(exports2, module2) {
+  "../../src/infrastructure/database/database-mcp-standalone.js"(exports2, module2) {
+    "use strict";
     var path2 = require("path");
     var fs2 = require("fs");
     var os2 = require("os");
@@ -2911,9 +2917,9 @@ ${sql}`);
   }
 });
 
-// src/shared/utils/worktree-project-resolver.js
+// ../../src/shared/utils/worktree-project-resolver.js
 var require_worktree_project_resolver = __commonJS({
-  "src/shared/utils/worktree-project-resolver.js"(exports2, module2) {
+  "../../src/shared/utils/worktree-project-resolver.js"(exports2, module2) {
     "use strict";
     function resolveProjectDir(directory, worktreeRows) {
       if (!directory) return directory;
@@ -2952,7 +2958,7 @@ var require_worktree_project_resolver = __commonJS({
   }
 });
 
-// src/infrastructure/mcp/mcp-stdio-server.js
+// ../../src/infrastructure/mcp/mcp-stdio-server.js
 var { inspect } = require("util");
 var writeProtocol = process.stdout.write.bind(process.stdout);
 var _toStderr = (...args) => process.stderr.write(args.map((a) => typeof a === "string" ? a : inspect(a)).join(" ") + "\n");
@@ -3800,6 +3806,18 @@ var MCPStdioServer = class _MCPStdioServer {
     } catch (e) {
     }
   }
+  _hasNudgeMarker(kind) {
+    try {
+      const os2 = require("os");
+      const fs2 = require("fs");
+      const stateDir = path.join(os2.homedir(), ".codeagentswarm", "terminal-nudge-state");
+      const rawKey = process.env.CODEAGENTSWARM_TERMINAL_ID || process.env.CODEAGENTSWARM_CURRENT_QUADRANT;
+      const key = String(rawKey || "").replace(/[^A-Za-z0-9_-]/g, "_");
+      return !!key && fs2.existsSync(path.join(stateDir, `${key}.${kind}`));
+    } catch (e) {
+      return false;
+    }
+  }
   // Resolve the current terminal id (1-based) from the environment.
   _getCurrentTerminalId() {
     const terminalId = process.env.CODEAGENTSWARM_CURRENT_QUADRANT;
@@ -3818,20 +3836,30 @@ var MCPStdioServer = class _MCPStdioServer {
   }
   // Set the GENERAL terminal title: the sticky tab label that represents the
   // product-level goal of what this terminal is working on. Set it ONCE at the
-  // start of work; call it again only to refine when the overall functionality
-  // changes, or to replace it when the terminal pivots to a radically different
-  // topic. It does NOT represent the current step — use update_terminal_activity
-  // for that.
+  // start of the conversation. Later calls preserve it unless the caller explicitly
+  // declares a radical topic change. It does NOT represent the current step — use
+  // update_terminal_activity for that.
   async setTerminalTitle(params) {
-    const { title, long_title } = params;
+    const { title, long_title, replace_existing } = params;
     if (!title) {
       throw new Error("title is required");
     }
     if (isPlaceholderTitle(title)) {
       throw new Error(`"${title}" looks like example text copied from the tool documentation, not a real title. Call the tool again with a title that describes the ACTUAL feature or goal you are working on in this agent (max 6 words).`);
     }
-    const shortTitle = this.generateShortTitle(title);
+    if (replace_existing !== void 0 && typeof replace_existing !== "boolean") {
+      throw new Error("replace_existing must be a boolean");
+    }
     const terminalId = this._getCurrentTerminalId();
+    if (replace_existing !== true && this._hasNudgeMarker("title")) {
+      return {
+        terminal_id: terminalId,
+        updated: false,
+        preserved: true,
+        message: "The existing conversation title was preserved. Use update_terminal_activity for follow-up work; set replace_existing=true only after the user pivots to a completely different functionality."
+      };
+    }
+    const shortTitle = this.generateShortTitle(title);
     const currentTask = this._getCurrentTask(terminalId);
     const taskId = currentTask ? currentTask.id : null;
     let longTitle = long_title;
@@ -4729,7 +4757,7 @@ Use 'clear' to remove the status.`;
       },
       {
         name: "set_terminal_title",
-        description: 'Set the GENERAL agent title AND the agent GOAL \u2014 pass BOTH arguments, because the user sees them together. `title` is the sticky Agent tab label at the FEATURE level (e.g. "Promo video for Twitter", "Minimize agents"); `long_title` is one sentence on what this agent is FOR, shown in the hover under the title. Keep the title high-level: name the feature, not a low-level step or work phase. Set it once at the start, then only refine it when the overall goal changes. Use update_terminal_activity for the current step. LANGUAGE: write BOTH in the SAME language the user is speaking.',
+        description: "Set the GENERAL agent title AND the agent GOAL from the first user request that established this conversation's topic. Pass BOTH text arguments because the user sees them together. This is once per conversation, NOT once per user message, turn, task, review, validation, or resumed session. Follow-up work belongs in update_terminal_activity and repeated calls preserve the original title. Only a user pivot to a completely different functionality may replace it, by passing replace_existing=true. LANGUAGE: write both text fields in the SAME language the user is speaking.",
         inputSchema: {
           type: "object",
           properties: {
@@ -4740,6 +4768,10 @@ Use 'clear' to remove the status.`;
             long_title: {
               type: "string",
               description: `The agent GOAL: one sentence saying what this agent is FOR \u2014 the outcome the work is aiming at, not the current step. ALWAYS provide it: the user reads it in the Agent hover, labelled GOAL, under the short title. Write the real goal in the user's language. Do NOT restate the title or prefix it with "Working on:".`
+            },
+            replace_existing: {
+              type: "boolean",
+              description: "Leave false or omit for normal follow-up work. Set true ONLY when the user explicitly pivots this existing conversation to a completely different functionality; reviews, tests, fixes, implementation phases, and refinements of the original request are activities and must not replace the title."
             }
           },
           // long_title is NOT in `required` on purpose: some agent clients
@@ -5193,7 +5225,8 @@ Use 'clear' to remove the status.`;
       case "set_terminal_title":
         result = await this.setTerminalTitle({
           title: args.title,
-          long_title: args.long_title
+          long_title: args.long_title,
+          replace_existing: args.replace_existing
         });
         break;
       case "update_terminal_activity":

package/dist/templates/antigravity-md-titles-section.md

@@ -19,7 +19,7 @@ Task management is disabled in CodeAgentSwarm Settings. Do NOT create, start, or
 ### Agent Title + Activity (product-focused)
 
 Three things, all described at the PRODUCT level:
-- **General title** (sticky tab): set it ONCE at the start with `set_terminal_title(title, long_title)`. It names the FEATURE / functionality this agent works on (e.g. "Promo Video", "Minimize Agents"); keep it a bit high-level so the context stays clear, NOT a low-level step and NOT a work phase (testing, e2e, validating, reviewing, deploying) — running the e2e for a settings redesign keeps the title "Settings Redesign", never "Settings E2E Tests"; phases go in update_terminal_activity. Change it again only to refine when the overall goal changes, or to REPLACE it when the conversation pivots to a radically different topic — never leave a stale title while only updating the activity. Set it as your FIRST action so the agent is never without info; a manual rename always wins (the app keeps it).
+- **General title** (sticky tab): derive it from the **first user request** that established this conversation's functionality and set it ONCE per conversation with `set_terminal_title(title, long_title)`. It stays stable across follow-up messages, new turns, task changes, reviews, tests, validation, implementation phases, and context compaction; those change `update_terminal_activity`, not the title. Only when the user pivots this conversation to a completely different functionality call `set_terminal_title` again with `replace_existing=true`. Refining, extending, fixing, reviewing, or finishing the original request is not a radical pivot. Keep the title at the FEATURE level, never a work phase; a manual rename always wins.
 - **Goal** (hover, labelled GOAL): the SAME call carries it in `long_title` — one sentence on what this agent is FOR, the outcome the work aims at, not the step you are on. ALWAYS pass it: it is the only place that answers "why does this agent exist", and three words of title cannot. Write it in the user's language. Good: title "Orden notificación" + long_title "Que las notificaciones no salgan antes de que cambie el status del agente". Bad: a long_title that only repeats the title, or one prefixed "Working on:" — both are DISCARDED and the user then sees no goal at all; omitting it has the same effect.
 - **Current activity** (hover + activity log): call `update_terminal_activity(activity)` OFTEN, one short sentence per step framed at the PRODUCT/feature level (what it does for the user), NOT in technical/internal terms (avoid handler, function, class, module, hook). Bad: "Investigating the output handler cost". Good: "Investigating why agents feel slow". It does NOT change the tab.
 
@@ -33,7 +33,7 @@ LANGUAGE: write the title, the goal and the activity in the SAME language the us
 
 ```
 CORRECT:
-1. set_terminal_title(title, long_title)   <- once at the start: tab label + GOAL sentence
+1. set_terminal_title(title, long_title)   <- first request in this conversation only
 2. update_terminal_activity(activity=...)  <- before you act, then often as you work
 3. update_terminal_activity(activity=...)  <- a final summary when you finish
 ```
@@ -44,7 +44,7 @@ CORRECT:
 
 | Tool | Purpose |
 |------|---------|
-| `set_terminal_title` | Set the agent's general (sticky tab) title AND its GOAL (`long_title`), ONCE at the start |
+| `set_terminal_title` | Set the sticky title + GOAL once per conversation; replace only for a radical pivot |
 | `update_terminal_activity` | Log the current product-focused activity, often as you work |
 <!-- CAS:STATUS:START -->
 | `set_terminal_status` | Keep the work-phase status badge honest at every phase change |

package/dist/templates/codex-md-titles-section.md

@@ -19,7 +19,7 @@ Task management is disabled in CodeAgentSwarm Settings. Do NOT create, start, or
 ### Agent Title + Activity (product-focused)
 
 Three things, all described at the PRODUCT level:
-- **General title** (sticky tab): set it ONCE at the start with `set_terminal_title(title, long_title)`. It names the FEATURE / functionality this agent works on (e.g. "Promo Video", "Minimize Agents"); keep it a bit high-level so the context stays clear, NOT a low-level step and NOT a work phase (testing, e2e, validating, reviewing, deploying) — running the e2e for a settings redesign keeps the title "Settings Redesign", never "Settings E2E Tests"; phases go in update_terminal_activity. Change it again only to refine when the overall goal changes, or to REPLACE it when the conversation pivots to a radically different topic — never leave a stale title while only updating the activity. Set it as your FIRST action so the agent is never without info; a manual rename always wins (the app keeps it).
+- **General title** (sticky tab): derive it from the **first user request** that established this conversation's functionality and set it ONCE per conversation with `set_terminal_title(title, long_title)`. It stays stable across follow-up messages, new turns, task changes, reviews, tests, validation, implementation phases, and context compaction; those change `update_terminal_activity`, not the title. Only when the user pivots this conversation to a completely different functionality call `set_terminal_title` again with `replace_existing=true`. Refining, extending, fixing, reviewing, or finishing the original request is not a radical pivot. Keep the title at the FEATURE level, never a work phase; a manual rename always wins.
 - **Goal** (hover, labelled GOAL): the SAME call carries it in `long_title` — one sentence on what this agent is FOR, the outcome the work aims at, not the step you are on. ALWAYS pass it: it is the only place that answers "why does this agent exist", and three words of title cannot. Write it in the user's language. Good: title "Orden notificación" + long_title "Que las notificaciones no salgan antes de que cambie el status del agente". Bad: a long_title that only repeats the title, or one prefixed "Working on:" — both are DISCARDED and the user then sees no goal at all; omitting it has the same effect.
 - **Current activity** (hover + activity log): call `update_terminal_activity(activity)` OFTEN, one short sentence per step framed at the PRODUCT/feature level (what it does for the user), NOT in technical/internal terms (avoid handler, function, class, module, hook). Bad: "Investigating the output handler cost". Good: "Investigating why agents feel slow". It does NOT change the tab.
 
@@ -33,7 +33,7 @@ LANGUAGE: write the title, the goal and the activity in the SAME language the us
 
 ```
 CORRECT:
-1. set_terminal_title(title, long_title)   <- once at the start: tab label + GOAL sentence
+1. set_terminal_title(title, long_title)   <- first request in this conversation only
 2. update_terminal_activity(activity=...)  <- before you act, then often as you work
 3. update_terminal_activity(activity=...)  <- a final summary when you finish
 ```
@@ -44,7 +44,7 @@ CORRECT:
 
 | Tool | Purpose |
 |------|---------|
-| `set_terminal_title` | Set the agent's general (sticky tab) title AND its GOAL (`long_title`), ONCE at the start |
+| `set_terminal_title` | Set the sticky title + GOAL once per conversation; replace only for a radical pivot |
 | `update_terminal_activity` | Log the current product-focused activity, often as you work |
 <!-- CAS:STATUS:START -->
 | `set_terminal_status` | Keep the work-phase status badge honest at every phase change |

package/dist/templates/grok-md-titles-section.md

@@ -22,16 +22,15 @@ Task management is disabled in CodeAgentSwarm Settings. Do NOT create, start, or
 (read, grep, bash, image gen, web search, file writes, MCP discovery for non-title work, etc.):
 
 ```
-1. set_terminal_title(title, long_title)   <- sticky tab + GOAL (ALWAYS both args)
+1. On the conversation's first request only: set_terminal_title(title, long_title)
 <!-- CAS:STATUS:START -->
 2. set_terminal_status("working")          <- work-phase badge
 <!-- CAS:STATUS:END -->
-3. update_terminal_activity(activity=...)  <- first product-focused step
+3. On every request: update_terminal_activity(activity=...) for the current step
 ```
 
-**This bootstrap is MANDATORY for every request** — research, answering questions,
-brainstorming, design, generating images, one-line advice, reading code. Skipping
-title/goal/activity while working is a failure.
+The title/goal call is mandatory only for the first request that establishes the
+conversation topic. On later requests, keep the existing title and update status/activity.
 
 Batch the bootstrap calls in the **same first tool round** as `check_active` when
 possible (or immediately after it). Do not start real work until they succeed.
@@ -47,22 +46,20 @@ them in your function list is not a reason to skip the title.**
 How to call them in this runtime:
 
 1. `search_tool` with query `codeagentswarm set_terminal_title` (once per session is enough).
-2. Immediately `use_tool` with `tool_name` **`codeagentswarm-tasks__set_terminal_title`**
-   and `tool_input` `{ "title": "...", "long_title": "..." }` (both args).
-3. Same round: `codeagentswarm-tasks__update_terminal_activity` with `{ "activity": "..." }`.
+2. On this conversation's first request, `use_tool` with `tool_name`
+   **`codeagentswarm-tasks__set_terminal_title`** and both title arguments.
+3. On every turn, call `codeagentswarm-tasks__update_terminal_activity`.
 <!-- CAS:STATUS:START -->
 4. Same round: `codeagentswarm-tasks__set_terminal_status` with `{ "status": "working" }`.
 <!-- CAS:STATUS:END -->
 
-Do this **before** Read, Grep, bash, skills, docs, or image tools. If you already
-have the schemas from an earlier `search_tool` in this session, skip rediscovery
-and call `use_tool` directly. If you already started work without a title, call
-these MCP tools immediately.
+Do the applicable calls **before** real work. On a later turn, keep the existing
+title. For a radical topic pivot only, pass `replace_existing=true`.
 
 ### Agent Title + Activity (product-focused)
 
 Three things, all described at the PRODUCT level:
-- **General title** (sticky tab): set it ONCE at the start with `set_terminal_title(title, long_title)`. It names the FEATURE / functionality this agent works on (e.g. "Promo Video", "Minimize Agents"); keep it a bit high-level so the context stays clear, NOT a low-level step and NOT a work phase (testing, e2e, validating, reviewing, deploying) — running the e2e for a settings redesign keeps the title "Settings Redesign", never "Settings E2E Tests"; phases go in update_terminal_activity. Change it again only to refine when the overall goal changes, or to REPLACE it when the conversation pivots to a radically different topic — never leave a stale title while only updating the activity. Set it as your FIRST action so the agent is never without info; a manual rename always wins (the app keeps it).
+- **General title** (sticky tab): derive it from the **first user request** that established this conversation's functionality and set it ONCE per conversation with `set_terminal_title(title, long_title)`. It stays stable across follow-up messages, new turns, task changes, reviews, tests, validation, implementation phases, and context compaction; those change `update_terminal_activity`, not the title. Only when the user pivots this conversation to a completely different functionality call `set_terminal_title` again with `replace_existing=true`. Refining, extending, fixing, reviewing, or finishing the original request is not a radical pivot. Keep the title at the FEATURE level, never a work phase; a manual rename always wins.
 - **Goal** (hover, labelled GOAL): the SAME call carries it in `long_title` — one sentence on what this agent is FOR, the outcome the work aims at, not the step you are on. ALWAYS pass it: it is the only place that answers "why does this agent exist", and three words of title cannot. Write it in the user's language. Good: title "Orden notificación" + long_title "Que las notificaciones no salgan antes de que cambie el status del agente". Bad: a long_title that only repeats the title, or one prefixed "Working on:" — both are DISCARDED and the user then sees no goal at all; omitting it has the same effect.
 - **Current activity** (hover + activity log): call `update_terminal_activity(activity)` OFTEN, one short sentence per step framed at the PRODUCT/feature level (what it does for the user), NOT in technical/internal terms (avoid handler, function, class, module, hook). Bad: "Investigating the output handler cost". Good: "Investigating why agents feel slow". It does NOT change the tab.
 
@@ -75,9 +72,9 @@ Do NOT keep renaming the tab every few minutes; use `update_terminal_activity` f
 LANGUAGE: write the title, the goal and the activity in the SAME language the user is speaking (e.g. Spanish if the user writes in Spanish).
 
 ```
-CORRECT (every request — research, questions, design, advice):
+CORRECT:
 1. check_active
-2. set_terminal_title(title, long_title)   <- once at the start: tab label + GOAL sentence
+2. set_terminal_title(title, long_title)   <- first request in this conversation only
 <!-- CAS:STATUS:START -->
 3. set_terminal_status("working")
 <!-- CAS:STATUS:END -->
@@ -92,7 +89,7 @@ CORRECT (every request — research, questions, design, advice):
 | Tool | Purpose |
 |------|---------|
 | `check_active` | Gate: only use CAS tools when inside CodeAgentSwarm |
-| `set_terminal_title` | Set the agent's general (sticky tab) title AND its GOAL (`long_title`), ONCE at the start |
+| `set_terminal_title` | Set the sticky title + GOAL once per conversation; replace only for a radical pivot |
 | `update_terminal_activity` | Log the current product-focused activity, often as you work |
 <!-- CAS:STATUS:START -->
 | `set_terminal_status` | Keep the work-phase status badge honest at every phase change |
@@ -100,12 +97,12 @@ CORRECT (every request — research, questions, design, advice):
 
 ### MEMORIZE (every session)
 
-1. **Start work** → `check_active` then `set_terminal_title(title, long_title)` + `update_terminal_activity` **before any other tool**
+1. **First request** → `check_active`, then `set_terminal_title(title, long_title)` once
 <!-- CAS:STATUS:START -->
 2. **Also set status** → `set_terminal_status("working")` at start; update on every phase change (`needs_input` / `needs_testing` / `done`)
 <!-- CAS:STATUS:END -->
-3. **New step** → `update_terminal_activity` (product step)
-4. **Radical topic change** → new `set_terminal_title` (never leave a stale tab)
+3. **Every request/new step** → `update_terminal_activity` (product step), never retitle
+4. **Radical topic change** → `set_terminal_title(..., replace_existing=true)`
 
 ### Mobile list cards = desktop List tabs (2026-08-13)
 

package/dist/templates/kimi-md-titles-section.md

@@ -22,16 +22,15 @@ Task management is disabled in CodeAgentSwarm Settings. Do NOT create, start, or
 (read, grep, bash, image gen, web search, file writes, MCP discovery for non-title work, etc.):
 
 ```
-1. set_terminal_title(title, long_title)   <- sticky tab + GOAL (ALWAYS both args)
+1. On the conversation's first request only: set_terminal_title(title, long_title)
 <!-- CAS:STATUS:START -->
 2. set_terminal_status("working")          <- work-phase badge
 <!-- CAS:STATUS:END -->
-3. update_terminal_activity(activity=...)  <- first product-focused step
+3. On every request: update_terminal_activity(activity=...) for the current step
 ```
 
-**This bootstrap is MANDATORY for every request** — research, answering questions,
-brainstorming, design, generating images, one-line advice, reading code. Skipping
-title/goal/activity while working is a failure.
+The title/goal call is mandatory only for the first request that establishes the
+conversation topic. On later requests, keep the existing title and update status/activity.
 
 Batch the bootstrap calls in the **same first tool round** as `check_active` when
 possible (or immediately after it). Do not start real work until they succeed.
@@ -41,7 +40,7 @@ LANGUAGE: write title, goal (`long_title`) and activity in the SAME language the
 ### Agent Title + Activity (product-focused)
 
 Three things, all described at the PRODUCT level:
-- **General title** (sticky tab): set it ONCE at the start with `set_terminal_title(title, long_title)`. It names the FEATURE / functionality this agent works on (e.g. "Promo Video", "Minimize Agents"); keep it a bit high-level so the context stays clear, NOT a low-level step and NOT a work phase (testing, e2e, validating, reviewing, deploying) — running the e2e for a settings redesign keeps the title "Settings Redesign", never "Settings E2E Tests"; phases go in update_terminal_activity. Change it again only to refine when the overall goal changes, or to REPLACE it when the conversation pivots to a radically different topic — never leave a stale title while only updating the activity. Set it as your FIRST action so the agent is never without info; a manual rename always wins (the app keeps it).
+- **General title** (sticky tab): derive it from the **first user request** that established this conversation's functionality and set it ONCE per conversation with `set_terminal_title(title, long_title)`. It stays stable across follow-up messages, new turns, task changes, reviews, tests, validation, implementation phases, and context compaction; those change `update_terminal_activity`, not the title. Only when the user pivots this conversation to a completely different functionality call `set_terminal_title` again with `replace_existing=true`. Refining, extending, fixing, reviewing, or finishing the original request is not a radical pivot. Keep the title at the FEATURE level, never a work phase; a manual rename always wins.
 - **Goal** (hover, labelled GOAL): the SAME call carries it in `long_title` — one sentence on what this agent is FOR, the outcome the work aims at, not the step you are on. ALWAYS pass it: it is the only place that answers "why does this agent exist", and three words of title cannot. Write it in the user's language. Good: title "Orden notificación" + long_title "Que las notificaciones no salgan antes de que cambie el status del agente". Bad: a long_title that only repeats the title, or one prefixed "Working on:" — both are DISCARDED and the user then sees no goal at all; omitting it has the same effect.
 - **Current activity** (hover + activity log): call `update_terminal_activity(activity)` OFTEN, one short sentence per step framed at the PRODUCT/feature level (what it does for the user), NOT in technical/internal terms (avoid handler, function, class, module, hook). Bad: "Investigating the output handler cost". Good: "Investigating why agents feel slow". It does NOT change the tab.
 
@@ -54,9 +53,9 @@ Do NOT keep renaming the tab every few minutes; use `update_terminal_activity` f
 LANGUAGE: write the title, the goal and the activity in the SAME language the user is speaking (e.g. Spanish if the user writes in Spanish).
 
 ```
-CORRECT (every request — research, questions, design, advice):
+CORRECT:
 1. check_active
-2. set_terminal_title(title, long_title)   <- once at the start: tab label + GOAL sentence
+2. set_terminal_title(title, long_title)   <- first request in this conversation only
 <!-- CAS:STATUS:START -->
 3. set_terminal_status("working")
 <!-- CAS:STATUS:END -->
@@ -71,7 +70,7 @@ CORRECT (every request — research, questions, design, advice):
 | Tool | Purpose |
 |------|---------|
 | `check_active` | Gate: only use CAS tools when inside CodeAgentSwarm |
-| `set_terminal_title` | Set the agent's general (sticky tab) title AND its GOAL (`long_title`), ONCE at the start |
+| `set_terminal_title` | Set the sticky title + GOAL once per conversation; replace only for a radical pivot |
 | `update_terminal_activity` | Log the current product-focused activity, often as you work |
 <!-- CAS:STATUS:START -->
 | `set_terminal_status` | Keep the work-phase status badge honest at every phase change |
@@ -79,11 +78,11 @@ CORRECT (every request — research, questions, design, advice):
 
 ### MEMORIZE (every session)
 
-1. **Start work** → `check_active` then `set_terminal_title(title, long_title)` + `update_terminal_activity` **before any other tool**
+1. **First request** → `check_active`, then `set_terminal_title(title, long_title)` once
 <!-- CAS:STATUS:START -->
 2. **Also set status** → `set_terminal_status("working")` at start; update on every phase change (`needs_input` / `needs_testing` / `done`)
 <!-- CAS:STATUS:END -->
-3. **New step** → `update_terminal_activity` (product step)
-4. **Radical topic change** → new `set_terminal_title` (never leave a stale tab)
+3. **Every request/new step** → `update_terminal_activity` (product step), never retitle
+4. **Radical topic change** → `set_terminal_title(..., replace_existing=true)`
 
 <!-- CODEAGENTSWARM GLOBAL CONFIG END -->

package/dist/templates/opencode-md-titles-section.md

@@ -19,7 +19,7 @@ Task management is disabled in CodeAgentSwarm Settings. Do NOT create, start, or
 ### Agent Title + Activity (product-focused)
 
 Three things, all described at the PRODUCT level:
-- **General title** (sticky tab): set it ONCE at the start with `set_terminal_title(title, long_title)`. It names the FEATURE / functionality this agent works on (e.g. "Promo Video", "Minimize Agents"); keep it a bit high-level so the context stays clear, NOT a low-level step and NOT a work phase (testing, e2e, validating, reviewing, deploying) — running the e2e for a settings redesign keeps the title "Settings Redesign", never "Settings E2E Tests"; phases go in update_terminal_activity. Change it again only to refine when the overall goal changes, or to REPLACE it when the conversation pivots to a radically different topic — never leave a stale title while only updating the activity. Set it as your FIRST action so the agent is never without info; a manual rename always wins (the app keeps it).
+- **General title** (sticky tab): derive it from the **first user request** that established this conversation's functionality and set it ONCE per conversation with `set_terminal_title(title, long_title)`. It stays stable across follow-up messages, new turns, task changes, reviews, tests, validation, implementation phases, and context compaction; those change `update_terminal_activity`, not the title. Only when the user pivots this conversation to a completely different functionality call `set_terminal_title` again with `replace_existing=true`. Refining, extending, fixing, reviewing, or finishing the original request is not a radical pivot. Keep the title at the FEATURE level, never a work phase; a manual rename always wins.
 - **Goal** (hover, labelled GOAL): the SAME call carries it in `long_title` — one sentence on what this agent is FOR, the outcome the work aims at, not the step you are on. ALWAYS pass it: it is the only place that answers "why does this agent exist", and three words of title cannot. Write it in the user's language. Good: title "Orden notificación" + long_title "Que las notificaciones no salgan antes de que cambie el status del agente". Bad: a long_title that only repeats the title, or one prefixed "Working on:" — both are DISCARDED and the user then sees no goal at all; omitting it has the same effect.
 - **Current activity** (hover + activity log): call `update_terminal_activity(activity)` OFTEN, one short sentence per step framed at the PRODUCT/feature level (what it does for the user), NOT in technical/internal terms (avoid handler, function, class, module, hook). Bad: "Investigating the output handler cost". Good: "Investigating why agents feel slow". It does NOT change the tab.
 
@@ -33,7 +33,7 @@ LANGUAGE: write the title, the goal and the activity in the SAME language the us
 
 ```
 CORRECT:
-1. set_terminal_title(title, long_title)   <- once at the start: tab label + GOAL sentence
+1. set_terminal_title(title, long_title)   <- first request in this conversation only
 2. update_terminal_activity(activity=...)  <- before you act, then often as you work
 3. update_terminal_activity(activity=...)  <- a final summary when you finish
 ```
@@ -44,7 +44,7 @@ CORRECT:
 
 | Tool | Purpose |
 |------|---------|
-| `set_terminal_title` | Set the agent's general (sticky tab) title AND its GOAL (`long_title`), ONCE at the start |
+| `set_terminal_title` | Set the sticky title + GOAL once per conversation; replace only for a radical pivot |
 | `update_terminal_activity` | Log the current product-focused activity, often as you work |
 <!-- CAS:STATUS:START -->
 | `set_terminal_status` | Keep the work-phase status badge honest at every phase change |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codeagentswarm/cas-cloud",
-  "version": "0.0.15",
+  "version": "0.0.16",
   "description": "CAS Cloud runtime for remote CodeAgentSwarm sessions",
   "author": "Arturo Garcia <hello@codeagentswarm.com>",
   "license": "PolyForm-Noncommercial-1.0.0",