@f5-sales-demo/xcsh 19.74.2 → 19.75.0

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@f5-sales-demo/xcsh",
-	"version": "19.74.2",
+	"version": "19.75.0",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://github.com/f5-sales-demo/xcsh",
 	"author": "Can Boluk",
@@ -56,13 +56,13 @@
 	"dependencies": {
 		"@agentclientprotocol/sdk": "0.16.1",
 		"@mozilla/readability": "^0.6",
-		"@f5-sales-demo/xcsh-stats": "19.74.2",
-		"@f5-sales-demo/pi-agent-core": "19.74.2",
-		"@f5-sales-demo/pi-ai": "19.74.2",
-		"@f5-sales-demo/pi-natives": "19.74.2",
-		"@f5-sales-demo/pi-resource-management": "19.74.2",
-		"@f5-sales-demo/pi-tui": "19.74.2",
-		"@f5-sales-demo/pi-utils": "19.74.2",
+		"@f5-sales-demo/xcsh-stats": "19.75.0",
+		"@f5-sales-demo/pi-agent-core": "19.75.0",
+		"@f5-sales-demo/pi-ai": "19.75.0",
+		"@f5-sales-demo/pi-natives": "19.75.0",
+		"@f5-sales-demo/pi-resource-management": "19.75.0",
+		"@f5-sales-demo/pi-tui": "19.75.0",
+		"@f5-sales-demo/pi-utils": "19.75.0",
 		"@sinclair/typebox": "^0.34",
 		"@xterm/headless": "^6.0",
 		"ajv": "^8.20",

package/src/browser/capabilities.generated.ts

@@ -26,7 +26,7 @@ export interface ExtensionCapabilities {
 
 export const EXTENSION_CAPABILITIES: ExtensionCapabilities = {
 	"version": "0.1.0",
-	"contractVersion": "1.9.0",
+	"contractVersion": "1.10.0",
 	"multiPortDiscovery": true,
 	"protocol": "tool_request/result",
 	"tools": [
@@ -855,6 +855,6 @@ export const EXTENSION_CAPABILITIES: ExtensionCapabilities = {
 	}
 };
 
-export const EXTENSION_CONTRACT_VERSION = "1.9.0";
+export const EXTENSION_CONTRACT_VERSION = "1.10.0";
 
 export const EXTENSION_TOOL_NAMES: readonly string[] = ["ping","capabilities","reload","debug_exec","detach","set_bridge_port","navigate","login","scroll_to","resize_window","tabs_list","tabs_create","tabs_close","click","click_element","click_xy","type_text","form_input","key_press","select_option","label_select","file_upload","read_ax","get_page_text","query_dom","find","wait_for","assert_text","screenshot","read_console","read_network","diag_suspension","diag_bridges","diag_activation","diag_ttft","capture_login_flow","wait_for_api_response","get_page_context","javascript_tool","browser_batch","set_explain_mode","annotate"];

package/src/browser/capabilities.json

@@ -1,6 +1,6 @@
 {
   "version": "0.1.0",
-  "contractVersion": "1.9.0",
+  "contractVersion": "1.10.0",
   "multiPortDiscovery": true,
   "protocol": "tool_request/result",
   "tools": [

package/src/browser/chat-conformance.json

@@ -1,5 +1,5 @@
 {
-  "contractVersion": "1.9.0",
+  "contractVersion": "1.10.0",
   "schemas": {
     "chat_request": {
       "type": "object",

package/src/browser/chat-handler.ts

@@ -32,6 +32,7 @@ import {
 } from "./chat-protocol";
 import { CONSOLE_ROUTES } from "./console-routes.generated";
 import type { BridgeServer } from "./extension-bridge";
+import { type ClientHost, hostProfile } from "./host-profiles";
 import { interpretPageState } from "./page-state-interpreter";
 import { chatSpans } from "./ttft-spans";
 
@@ -163,7 +164,7 @@ export class ChatHandler {
 		});
 		chat.unsubscribe = unsubscribe;
 
-		const prompt = composeChatPrompt(req.text, req.context, req.mode);
+		const prompt = composeChatPrompt(req.text, req.context, req.mode, this.#server.clientHost);
 
 		try {
 			chat.promptAt = Date.now();
@@ -435,49 +436,6 @@ export function classifyChatErrorReason(message: string): ChatErrorReason | unde
 	return undefined;
 }
 
-/**
- * Chrome-extension self-awareness prompt. Injected when xcsh is serving a browser
- * chat (not the CLI TUI). Tells the LLM it's in a Chrome side panel alongside the
- * F5 XC console, what tools it has, and how to behave differently from the CLI.
- */
-const CHROME_CHAT_SYSTEM_PROMPT = `[System: You are xcsh, an AI assistant for the F5 Distributed Cloud console, running as a Chrome browser side panel — not a terminal CLI.
-
-CRITICAL: ALWAYS respond with TEXT FIRST. Do NOT jump straight to tool calls. The user sees a chat panel and expects a conversational text response, not silence while tools run in the background. For questions ("what page am I on?", "what is this?"), answer with text using the page context below — no tools needed. Only use tools when the user explicitly asks you to DO something (create, navigate, click, modify).
-
-CONTEXT: The user sees a small chat window alongside the F5 XC admin console. You receive page-aware context each turn: the current URL (interpreted as workspace/resource/CRUD operation/namespace), the API resource JSON, and the accessibility tree. USE THIS CONTEXT to answer questions — don't call tools to find information you already have.
-
-BEHAVIOR:
-- Respond concisely with markdown. The chat panel is narrow — avoid long code blocks.
-- You KNOW which page the user is on (injected below). Don't ask "what page are you on?" — tell them.
-- For questions about the page/resource: answer from the injected context. No tools.
-- If a blocking popup/survey appears, dismiss it by clicking the close button.
-- If on the LOGIN page: use the login tool to log in. The login tool handles ALL environments — production (*.console.ves.volterra.io) AND staging (*.staging.volterra.us, login-staging.volterra.us). Do NOT claim the login tool is broken, unsupported, or doesn't work for staging — it does.
-
-BROWSER AUTOMATION (when the user asks to create/modify/navigate resources):
-- You are IN a Chrome browser. The active console tab is your workspace — use IT.
-- For create/modify/delete: call catalog_workflow_runner IMMEDIATELY with ONE tool call per resource:
-  {"resource": "health-check", "operation": "create", "params": {"name": "foo", "namespace": "demo"}, "presentation": "guided"}
-  Do NOT read API specs first, do NOT create todos, do NOT orchestrate multi-step tool chains. The catalog_workflow_runner handles ALL the form navigation internally.
-- Say a brief text message BEFORE the tool call: "Creating health check **foo** — watch the browser." Then call the tool. Nothing else.
-- The human is WATCHING the form automation (fingerprint-before-click, highlights, ~1.5s/step). Do NOT use background API calls.
-- The browser may be at 85% zoom — automation handles coordinates at any zoom.
-- The console catalog has workflows for 100+ F5 XC resources.
-- Do NOT open new tabs — drive the existing console tab.
-
-MULTI-RESOURCE REQUESTS (when the user asks to create several resources in one prompt):
-- Create resources in DEPENDENCY ORDER: health checks first, then origin pools (which reference health checks), then load balancers (which reference origin pools and app firewalls).
-- After each catalog_workflow_runner call completes, IMMEDIATELY proceed to the next resource. Do NOT inspect, verify, click into, or navigate to the resource you just created. Do NOT open the JSON view. Do NOT read the page to confirm — the tool already confirmed success. Move directly to the next creation.
-- Between resources, say ONE short line: "Health check created. Now creating origin pool **bar** — watch the browser." Then call the next tool.
-- NEVER navigate to a list/detail/JSON view between creations. Stay on the automation path.
-
-SAFETY — NEVER DO THESE:
-- NEVER kill, stop, or manage processes on port 19222 — that is YOUR OWN bridge. Killing it kills you.
-- NEVER run lsof, fuser, kill, or pkill on the bridge port. You ARE the bridge.
-- NEVER use bash/shell tools to manage xcsh processes, ports, or the debugger connection.
-- NEVER run commands that would terminate your own process or the WebSocket server.]
-
-`;
-
 const MODE_INSTRUCTIONS: Record<InteractionMode, string> = {
 	educational: "Explain concepts and settings in depth. Help the user understand what they're looking at and why.",
 	presentation: "Guide a structured walkthrough. Narrate each step clearly for a live audience.",
@@ -486,77 +444,94 @@ const MODE_INSTRUCTIONS: Record<InteractionMode, string> = {
 	annotation: "Create on-page teaching annotations that highlight key elements and explain their purpose.",
 };
 
-export function composeChatPrompt(text: string, context: PageContextSnapshot | null, mode: InteractionMode): string {
+export function composeChatPrompt(
+	text: string,
+	context: PageContextSnapshot | null,
+	mode: InteractionMode,
+	host: ClientHost | null,
+): string {
 	const parts: string[] = [];
 
-	// Chrome-extension self-awareness: establishes the agent's browser context.
-	parts.push(CHROME_CHAT_SYSTEM_PROMPT);
-	parts.push(`[Chat mode: ${mode}] ${MODE_INSTRUCTIONS[mode]}`);
+	// Host-aware self-awareness: the Chrome extension gets the browser panel prompt;
+	// an Office add-in (excel/powerpoint/word) gets its document-assistant prompt. A
+	// null/unannounced host falls back to the Chrome profile.
+	const profile = hostProfile(host);
+	parts.push(profile.systemPrompt);
+
+	// Browser hosts ALSO get an interaction mode + the page-context block. Document
+	// hosts get NEITHER: Office sends no page context and has no browser modes; its
+	// tools + document state arrive at runtime via set_host_tools.
+	if (profile.kind === "browser") {
+		parts.push(`[Chat mode: ${mode}] ${MODE_INSTRUCTIONS[mode]}`);
+		if (context) composeBrowserPageContext(parts, context);
+	}
 
-	if (context) {
-		// Interpret the raw URL into structured page state (workspace, resource,
-		// CRUD operation, namespace) using deterministic route-pattern matching
-		// against console_ui.yaml — the LLM sees "origin_pool LIST in demo" not a
-		// raw URL it must guess about.
-		const pageState = interpretPageState(context.url, null, CONSOLE_ROUTES);
+	parts.push("");
+	parts.push(text);
+	return parts.join("\n");
+}
 
-		parts.push("");
-		parts.push(`[Page context — captured at ${new Date(context.capturedAt).toISOString()}]`);
+/** Append the Chrome-only page-context block (interpreted page state + API body +
+ * accessibility tree) to `parts`. Browser hosts only — Office sends no context. */
+function composeBrowserPageContext(parts: string[], context: PageContextSnapshot): void {
+	// Interpret the raw URL into structured page state (workspace, resource,
+	// CRUD operation, namespace) using deterministic route-pattern matching
+	// against console_ui.yaml — the LLM sees "origin_pool LIST in demo" not a
+	// raw URL it must guess about.
+	const pageState = interpretPageState(context.url, null, CONSOLE_ROUTES);
 
-		// Tenant + environment (the LLM knows WHICH tenant on WHICH environment).
-		if (pageState.tenant || pageState.environment) {
-			parts.push(`Tenant: ${pageState.tenant ?? "unknown"} (${pageState.environment ?? "unknown"} environment)`);
-		}
+	parts.push("");
+	parts.push(`[Page context — captured at ${new Date(context.capturedAt).toISOString()}]`);
 
-		// Structured page state (the interpreted context the LLM acts on).
-		if (pageState.operation === "login") {
-			parts.push("Page: LOGIN — session expired or first login. The user is on the Keycloak authentication page.");
-			parts.push(
-				"Use the login tool with their email and password to log in. The login tool handles both production and staging Keycloak (including login-staging.volterra.us). Do NOT bypass it or claim it doesn't support staging.",
-			);
-		} else if (pageState.resource) {
-			const opLabel = pageState.operation.toUpperCase();
-			const nsLabel = pageState.namespace ? ` in namespace "${pageState.namespace}"` : "";
-			const nameLabel = pageState.resourceName ? ` — instance "${pageState.resourceName}"` : "";
-			parts.push(`Page: ${pageState.resource} ${opLabel}${nameLabel} (workspace: ${pageState.workspace}${nsLabel})`);
-		} else {
-			parts.push(`Page: ${context.title} (unrecognized resource)`);
-		}
-		if (pageState.modalBlocking) {
-			parts.push(`⚠ Modal blocking: ${pageState.modalText ?? "unknown overlay"}`);
-		}
-		parts.push(`URL: ${context.url}`);
-		parts.push(`Title: ${context.title}`);
-
-		if (context.api) {
-			parts.push(
-				`API resource (${context.api.resourceType ?? "unknown"}, status ${context.api.status}): ${context.api.url}`,
-			);
-			if (context.api.body) {
-				const body =
-					typeof context.api.body === "string" ? context.api.body : JSON.stringify(context.api.body, null, 2);
-				parts.push(body);
-			}
-			if (context.api.truncated) {
-				parts.push("[API body was truncated]");
-			}
-		}
+	// Tenant + environment (the LLM knows WHICH tenant on WHICH environment).
+	if (pageState.tenant || pageState.environment) {
+		parts.push(`Tenant: ${pageState.tenant ?? "unknown"} (${pageState.environment ?? "unknown"} environment)`);
+	}
 
-		if (context.ax) {
-			const ax = typeof context.ax === "string" ? context.ax : JSON.stringify(context.ax);
-			parts.push(`Accessibility tree: ${ax}`);
+	// Structured page state (the interpreted context the LLM acts on).
+	if (pageState.operation === "login") {
+		parts.push("Page: LOGIN — session expired or first login. The user is on the Keycloak authentication page.");
+		parts.push(
+			"Use the login tool with their email and password to log in. The login tool handles both production and staging Keycloak (including login-staging.volterra.us). Do NOT bypass it or claim it doesn't support staging.",
+		);
+	} else if (pageState.resource) {
+		const opLabel = pageState.operation.toUpperCase();
+		const nsLabel = pageState.namespace ? ` in namespace "${pageState.namespace}"` : "";
+		const nameLabel = pageState.resourceName ? ` — instance "${pageState.resourceName}"` : "";
+		parts.push(`Page: ${pageState.resource} ${opLabel}${nameLabel} (workspace: ${pageState.workspace}${nsLabel})`);
+	} else {
+		parts.push(`Page: ${context.title} (unrecognized resource)`);
+	}
+	if (pageState.modalBlocking) {
+		parts.push(`⚠ Modal blocking: ${pageState.modalText ?? "unknown overlay"}`);
+	}
+	parts.push(`URL: ${context.url}`);
+	parts.push(`Title: ${context.title}`);
+
+	if (context.api) {
+		parts.push(
+			`API resource (${context.api.resourceType ?? "unknown"}, status ${context.api.status}): ${context.api.url}`,
+		);
+		if (context.api.body) {
+			const body =
+				typeof context.api.body === "string" ? context.api.body : JSON.stringify(context.api.body, null, 2);
+			parts.push(body);
 		}
-
-		if (context.truncated) {
-			parts.push("[Page context was truncated]");
+		if (context.api.truncated) {
+			parts.push("[API body was truncated]");
 		}
+	}
 
-		parts.push("---");
+	if (context.ax) {
+		const ax = typeof context.ax === "string" ? context.ax : JSON.stringify(context.ax);
+		parts.push(`Accessibility tree: ${ax}`);
 	}
 
-	parts.push("");
-	parts.push(text);
-	return parts.join("\n");
+	if (context.truncated) {
+		parts.push("[Page context was truncated]");
+	}
+
+	parts.push("---");
 }
 
 export function classifyReferenceKind(url: string): "doc" | "console" {

package/src/browser/chat-protocol.ts

@@ -15,6 +15,11 @@ import type {
 	RpcHostToolUpdate,
 } from "../host-tools/types";
 
+// The client host announced on the `hello` handshake (contract 1.10.0). Re-exported
+// (type-only, fully erased) so browser-safe consumers — the office-pane bundle —
+// can share the wire vocabulary without importing the host-profiles prompt data.
+export type { ClientHost } from "./host-profiles";
+
 // ---------------------------------------------------------------------------
 // Page context snapshot (auto-attached by extension to every chat_request)
 // ---------------------------------------------------------------------------

package/src/browser/extension-bridge-tools.ts

@@ -97,3 +97,19 @@ export const BROWSER_TOOL_NAMES: readonly string[] = [
 	"annotate",
 	"set_explain_mode",
 ];
+
+/**
+ * Builtin agent tools scoped into the headless OFFICE bridge (`xcsh office serve`).
+ * The Office task pane drives a document (Excel/PowerPoint/Word), NOT a browser, so
+ * it must get NONE of the {@link BROWSER_TOOL_NAMES} — those would be hallucinated
+ * against a host with no browser to drive. The document's own tools arrive at
+ * runtime over the bridge via `set_host_tools`; this list is only the minimal
+ * general-purpose, host-neutral builtin toolset a document assistant can safely use.
+ *
+ * NOTE: an EMPTY list cannot express "no builtin tools" — createAgentSession/createTools
+ * treat `[]` as "unscoped" and hand back the FULL builtin registry (bash/edit/python/
+ * browser/…). So we pass an explicit minimal set instead. `calc` is the one builtin
+ * that is pure computation — no browser, no shell, no filesystem, no network — and is
+ * genuinely useful for spreadsheet/document math.
+ */
+export const OFFICE_TOOL_NAMES: readonly string[] = ["calc"];

package/src/browser/extension-bridge.ts

@@ -1,6 +1,7 @@
 import { randomUUID } from "node:crypto";
 import type { Server, ServerWebSocket } from "bun";
 import { LOCALIP_HOST } from "./bridge-cert";
+import { type ClientHost, isClientHost } from "./host-profiles";
 
 export interface ToolResult {
 	content: unknown;
@@ -177,6 +178,9 @@ export class BridgeServer {
 	#onMessage: Array<(msg: Record<string, unknown>) => void> = [];
 	/** Heartbeat interval that sends pings to keep the MV3 service worker alive (sweep + chat). */
 	#heartbeat: ReturnType<typeof setInterval> | null = null;
+	/** The client host learned from the `hello` handshake (null until a client
+	 * announces one; the Chrome extension omits it → stays null → chrome profile). */
+	#clientHost: ClientHost | null = null;
 	/** Provider of this process's tenant identity, answering the `hello` handshake. */
 	#sessionInfo:
 		| (() => {
@@ -203,6 +207,12 @@ export class BridgeServer {
 		return this.#clients.size > 0;
 	}
 
+	/** The client host announced by the connected client's `hello` (null until a
+	 * client announces one). Read by the ChatHandler to pick the host-aware prompt. */
+	get clientHost(): ClientHost | null {
+		return this.#clientHost;
+	}
+
 	/** Number of connected extension clients (channels). */
 	get connectedCount(): number {
 		return this.#clients.size;
@@ -364,7 +374,7 @@ export class BridgeServer {
 
 	#handleMessage(ws: ServerWebSocket<undefined>, message: string | Buffer): void {
 		const text = typeof message === "string" ? message : message.toString("utf8");
-		let msg: { type?: string; id?: string; content?: unknown; is_error?: boolean };
+		let msg: { type?: string; id?: string; content?: unknown; is_error?: boolean; host?: unknown };
 		try {
 			msg = JSON.parse(text);
 		} catch {
@@ -379,6 +389,11 @@ export class BridgeServer {
 			ws.send(JSON.stringify({ type: "pong" }));
 		} else if (msg.type === "hello") {
 			// Identity handshake: tell the extension which tenant this process serves.
+			// Record the announced client host (contract 1.10.0): Office sends its
+			// lowercased Office.context.host ("excel"|"powerpoint"|"word"); the Chrome
+			// extension omits it → clientHost stays null → the browser profile. Invalid
+			// values are ignored (null retained). Echoed back so the client can confirm.
+			if (isClientHost(msg.host)) this.#clientHost = msg.host;
 			const info = this.#sessionInfo?.() ?? {
 				tenant: null,
 				env: null,
@@ -396,6 +411,7 @@ export class BridgeServer {
 					env: info.env,
 					apiUrl: info.apiUrl,
 					contextBound: info.contextBound,
+					host: this.#clientHost,
 					pid: process.pid,
 					wssPort: this.wssPort,
 					canConfigureProvider: true,

package/src/browser/headless-bridge.ts

@@ -21,7 +21,7 @@ import { deriveTenantEnv } from "../services/xcsh-env";
 import { resolveBridgeTls } from "./bridge-cert";
 import { ChatHandler } from "./chat-handler";
 import { type BridgeServer, startBridgeServer } from "./extension-bridge";
-import { BROWSER_TOOL_NAMES, createExtensionBridgeTools, EXTENSION_AGENT_TOOL_NAMES } from "./extension-bridge-tools";
+import { OFFICE_TOOL_NAMES } from "./extension-bridge-tools";
 import { setSharedBridgeServer } from "./provider";
 
 /** A running headless bridge + a teardown that disposes the chat handler and
@@ -67,7 +67,6 @@ export interface HeadlessBridgeDeps {
 	resolveBridgeTls: typeof resolveBridgeTls;
 	startBridgeServer: typeof startBridgeServer;
 	setSharedBridgeServer: typeof setSharedBridgeServer;
-	createExtensionBridgeTools: typeof createExtensionBridgeTools;
 	createAgentSession: typeof createAgentSession;
 	ChatHandlerCtor: typeof ChatHandler;
 }
@@ -95,7 +94,6 @@ const defaultDeps: HeadlessBridgeDeps = {
 	resolveBridgeTls,
 	startBridgeServer,
 	setSharedBridgeServer,
-	createExtensionBridgeTools,
 	createAgentSession,
 	ChatHandlerCtor: ChatHandler,
 };
@@ -130,15 +128,17 @@ export async function startHeadlessChatBridge(deps: HeadlessBridgeDeps = default
 	// selectProvider() reuses a dead bridge. The caller (startOfficeServe) treats
 	// the rethrow as a non-fatal "pane only" fallback.
 	try {
-		// Turn the extension's browser actions into bridge-proxying CustomTools, then
-		// create ONE headless session scoped to the browser tools (Office document
-		// tools arrive at runtime via set_host_tools).
-		const extensionTools = deps.createExtensionBridgeTools(bridge);
+		// Create ONE headless Office session scoped to the minimal general builtin set
+		// (OFFICE_TOOL_NAMES) with NO browser tools — neither the browser BUILTINS
+		// (navigate/click/…) nor the bridge-proxying browser CUSTOM tools, both of which
+		// would be hallucinated in a document task pane (there is no browser to drive).
+		// The document's own tools (Excel/Word/PowerPoint) arrive at runtime via
+		// set_host_tools; chat over xcsh's configured provider needs no browser tooling.
 		const { session } = await deps.createAgentSession({
 			cwd,
 			hasUI: false,
-			toolNames: [...new Set([...BROWSER_TOOL_NAMES, ...EXTENSION_AGENT_TOOL_NAMES])],
-			customTools: extensionTools,
+			toolNames: [...OFFICE_TOOL_NAMES],
+			customTools: [],
 			// Headless: no MCP/LSP/extension discovery — lean, no network/blocking prompts.
 			enableMCP: false,
 			enableLsp: false,

package/src/browser/host-profiles.ts

@@ -0,0 +1,164 @@
+/**
+ * Host-aware system prompts for the bridge chat engine.
+ *
+ * The same `hello`/`hello_ack` bridge serves two very different clients: the
+ * Chrome extension (a browser side panel driving the F5 XC console) and the
+ * Office add-in task pane (Excel / PowerPoint / Word, driving the open
+ * document). A `host` field on the handshake tells the engine which one it is,
+ * so `composeChatPrompt` can inject the RIGHT self-awareness prompt instead of
+ * unconditionally telling every client it is a Chrome browser panel.
+ *
+ * Browser-safe: pure string/data module, no node/bun imports — so it can be
+ * type-imported by the office-pane's browser bundle via the native contract.
+ */
+
+/**
+ * The client hosts the bridge can serve, as lowercase wire values. Office maps
+ * its `Office.context.host` ("Excel"|"PowerPoint"|"Word") to these; the Chrome
+ * extension is "chrome". Outlook is intentionally absent — the add-in omits the
+ * host for hosts without a document assistant, so the engine falls back to the
+ * default profile.
+ */
+export type ClientHost = "chrome" | "excel" | "powerpoint" | "word";
+
+/** Every {@link ClientHost} value, for iteration + validation. */
+export const CLIENT_HOSTS: readonly ClientHost[] = ["chrome", "excel", "powerpoint", "word"];
+
+/** Runtime guard: true when `v` is a valid {@link ClientHost} wire value. */
+export function isClientHost(v: unknown): v is ClientHost {
+	return typeof v === "string" && (CLIENT_HOSTS as readonly string[]).includes(v);
+}
+
+/**
+ * A host profile pairs a `kind` (browser vs document) with the self-awareness
+ * system prompt for that host. `kind` gates browser-only behavior in
+ * `composeChatPrompt` (interaction modes + the page-context block) — document
+ * hosts get neither.
+ */
+export interface HostProfile {
+	kind: "browser" | "document";
+	systemPrompt: string;
+}
+
+/**
+ * Chrome-extension self-awareness prompt. Injected when xcsh is serving a browser
+ * chat (not the CLI TUI). Tells the LLM it's in a Chrome side panel alongside the
+ * F5 XC console, what tools it has, and how to behave differently from the CLI.
+ */
+export const CHROME_CHAT_SYSTEM_PROMPT = `[System: You are xcsh, an AI assistant for the F5 Distributed Cloud console, running as a Chrome browser side panel — not a terminal CLI.
+
+CRITICAL: ALWAYS respond with TEXT FIRST. Do NOT jump straight to tool calls. The user sees a chat panel and expects a conversational text response, not silence while tools run in the background. For questions ("what page am I on?", "what is this?"), answer with text using the page context below — no tools needed. Only use tools when the user explicitly asks you to DO something (create, navigate, click, modify).
+
+CONTEXT: The user sees a small chat window alongside the F5 XC admin console. You receive page-aware context each turn: the current URL (interpreted as workspace/resource/CRUD operation/namespace), the API resource JSON, and the accessibility tree. USE THIS CONTEXT to answer questions — don't call tools to find information you already have.
+
+BEHAVIOR:
+- Respond concisely with markdown. The chat panel is narrow — avoid long code blocks.
+- You KNOW which page the user is on (injected below). Don't ask "what page are you on?" — tell them.
+- For questions about the page/resource: answer from the injected context. No tools.
+- If a blocking popup/survey appears, dismiss it by clicking the close button.
+- If on the LOGIN page: use the login tool to log in. The login tool handles ALL environments — production (*.console.ves.volterra.io) AND staging (*.staging.volterra.us, login-staging.volterra.us). Do NOT claim the login tool is broken, unsupported, or doesn't work for staging — it does.
+
+BROWSER AUTOMATION (when the user asks to create/modify/navigate resources):
+- You are IN a Chrome browser. The active console tab is your workspace — use IT.
+- For create/modify/delete: call catalog_workflow_runner IMMEDIATELY with ONE tool call per resource:
+  {"resource": "health-check", "operation": "create", "params": {"name": "foo", "namespace": "demo"}, "presentation": "guided"}
+  Do NOT read API specs first, do NOT create todos, do NOT orchestrate multi-step tool chains. The catalog_workflow_runner handles ALL the form navigation internally.
+- Say a brief text message BEFORE the tool call: "Creating health check **foo** — watch the browser." Then call the tool. Nothing else.
+- The human is WATCHING the form automation (fingerprint-before-click, highlights, ~1.5s/step). Do NOT use background API calls.
+- The browser may be at 85% zoom — automation handles coordinates at any zoom.
+- The console catalog has workflows for 100+ F5 XC resources.
+- Do NOT open new tabs — drive the existing console tab.
+
+MULTI-RESOURCE REQUESTS (when the user asks to create several resources in one prompt):
+- Create resources in DEPENDENCY ORDER: health checks first, then origin pools (which reference health checks), then load balancers (which reference origin pools and app firewalls).
+- After each catalog_workflow_runner call completes, IMMEDIATELY proceed to the next resource. Do NOT inspect, verify, click into, or navigate to the resource you just created. Do NOT open the JSON view. Do NOT read the page to confirm — the tool already confirmed success. Move directly to the next creation.
+- Between resources, say ONE short line: "Health check created. Now creating origin pool **bar** — watch the browser." Then call the next tool.
+- NEVER navigate to a list/detail/JSON view between creations. Stay on the automation path.
+
+SAFETY — NEVER DO THESE:
+- NEVER kill, stop, or manage processes on port 19222 — that is YOUR OWN bridge. Killing it kills you.
+- NEVER run lsof, fuser, kill, or pkill on the bridge port. You ARE the bridge.
+- NEVER use bash/shell tools to manage xcsh processes, ports, or the debugger connection.
+- NEVER run commands that would terminate your own process or the WebSocket server.]
+
+`;
+
+/**
+ * Excel task-pane self-awareness prompt. The assistant works the OPEN workbook
+ * via host tools (arriving at runtime over the bridge), thinking in cells,
+ * ranges, and formula dependencies.
+ */
+const EXCEL_CHAT_SYSTEM_PROMPT = `[System: You are xcsh, an AI assistant running as a task pane inside Microsoft Excel — not a terminal CLI. You help the user with the OPEN workbook using the Excel host tools available to you.
+
+CRITICAL: ALWAYS respond with TEXT FIRST — the user sees a chat pane and expects a conversational reply, not silence while tools run. Answer questions from the data you read; only WRITE to the workbook when the user asks you to.
+
+CONTEXT: You can only access the open workbook. Think in cells, ranges, and — above all — FORMULAS and their dependencies:
+- Preserve formula relationships. When you change a cell, let dependent cells recompute; do not overwrite a formula with its current value unless asked.
+- Warn the user before overwriting existing cell contents.
+- Cite specific cells and ranges precisely (e.g. A1, Sheet1!B2:B10) so the user can follow along.
+
+BEHAVIOR:
+- Respond concisely with markdown. The task pane is narrow — avoid long code blocks.
+- Read the workbook to answer questions about its data; do not guess.
+- Make edits only when asked, one clear change at a time, and say what you changed and where.]
+
+`;
+
+/**
+ * PowerPoint task-pane self-awareness prompt. The assistant works the OPEN
+ * presentation via host tools, thinking in slides, shapes, and the slide master.
+ */
+const POWERPOINT_CHAT_SYSTEM_PROMPT = `[System: You are xcsh, an AI assistant running as a task pane inside Microsoft PowerPoint — not a terminal CLI. You help the user with the OPEN presentation using the PowerPoint host tools available to you.
+
+CRITICAL: ALWAYS respond with TEXT FIRST — the user sees a chat pane and expects a conversational reply, not silence while tools run. Answer questions from what you read; only edit the deck when the user asks you to.
+
+CONTEXT: You can only access the open presentation. Think in slides, shapes, and the slide master:
+- Conform any new content to the deck's existing template, fonts, and colors — do not introduce a different look.
+- Make pinpoint, per-slide edits. Do NOT regenerate the whole deck to change one thing.
+- Refer to slides by number so the user can follow along.
+
+BEHAVIOR:
+- Respond concisely with markdown. The task pane is narrow — avoid long code blocks.
+- Read the presentation to answer questions about it; do not guess.
+- Make edits only when asked, one clear change at a time, and say which slide you changed.]
+
+`;
+
+/**
+ * Word task-pane self-awareness prompt. The assistant works the OPEN document
+ * via host tools, thinking in paragraphs, the selection, comments, and tracked
+ * changes.
+ */
+const WORD_CHAT_SYSTEM_PROMPT = `[System: You are xcsh, an AI assistant running as a task pane inside Microsoft Word — not a terminal CLI. You help the user with the OPEN document using the Word host tools available to you.
+
+CRITICAL: ALWAYS respond with TEXT FIRST — the user sees a chat pane and expects a conversational reply, not silence while tools run. Answer questions from what you read; only edit the document when the user asks you to.
+
+CONTEXT: You can only access the open document. Think in paragraphs, the current selection, comments, and tracked changes:
+- Preserve the document's styles and numbering — do not flatten formatting.
+- Describe your edits so the user can review them, and prefer changes the user can accept or reject.
+- When the user refers to "the selection" (or "this"), act on the current selection.
+
+BEHAVIOR:
+- Respond concisely with markdown. The task pane is narrow — avoid long code blocks.
+- Read the document to answer questions about it; do not guess.
+- Make edits only when asked, one clear change at a time, and say what you changed.]
+
+`;
+
+/** The self-awareness profile per client host. */
+export const HOST_PROFILES: Record<ClientHost, HostProfile> = {
+	chrome: { kind: "browser", systemPrompt: CHROME_CHAT_SYSTEM_PROMPT },
+	excel: { kind: "document", systemPrompt: EXCEL_CHAT_SYSTEM_PROMPT },
+	powerpoint: { kind: "document", systemPrompt: POWERPOINT_CHAT_SYSTEM_PROMPT },
+	word: { kind: "document", systemPrompt: WORD_CHAT_SYSTEM_PROMPT },
+};
+
+/** The host assumed when a client does not announce one (the Chrome extension,
+ * whose handshake predates the `host` field). */
+export const DEFAULT_HOST: ClientHost = "chrome";
+
+/** Resolve the profile for a host, falling back to the {@link DEFAULT_HOST}
+ * profile for a null/undefined host (an unannounced or non-document client). */
+export function hostProfile(host: ClientHost | null | undefined): HostProfile {
+	return HOST_PROFILES[host ?? DEFAULT_HOST];
+}

package/src/internal-urls/build-info.generated.ts

@@ -17,17 +17,17 @@ export interface BuildInfo {
 }
 
 export const BUILD_INFO: BuildInfo = {
-	"version": "19.74.2",
-	"commit": "c0ff94bc5476e1c082e31b85ab8afdd193010f33",
-	"shortCommit": "c0ff94b",
+	"version": "19.75.0",
+	"commit": "ac9635391c489c70d35c68a0e1cacdbae9f7e631",
+	"shortCommit": "ac96353",
 	"branch": "main",
-	"tag": "v19.74.2",
-	"commitDate": "2026-07-22T12:44:16Z",
-	"buildDate": "2026-07-22T13:12:17.223Z",
+	"tag": "v19.75.0",
+	"commitDate": "2026-07-22T13:46:55Z",
+	"buildDate": "2026-07-22T14:09:19.426Z",
 	"dirty": true,
 	"prNumber": "",
 	"repoUrl": "https://github.com/f5-sales-demo/xcsh",
 	"repoSlug": "f5-sales-demo/xcsh",
-	"commitUrl": "https://github.com/f5-sales-demo/xcsh/commit/c0ff94bc5476e1c082e31b85ab8afdd193010f33",
-	"releaseUrl": "https://github.com/f5-sales-demo/xcsh/releases/tag/v19.74.2"
+	"commitUrl": "https://github.com/f5-sales-demo/xcsh/commit/ac9635391c489c70d35c68a0e1cacdbae9f7e631",
+	"releaseUrl": "https://github.com/f5-sales-demo/xcsh/releases/tag/v19.75.0"
 };