@iaforged/context-code 1.2.9 → 1.2.10

package/dist/src/tools/ListMcpResourcesTool/prompt.js

@@ -1,18 +1,18 @@
 export const LIST_MCP_RESOURCES_TOOL_NAME = 'ListMcpResourcesTool';
-export const DESCRIPTION = `
-Lists available resources from configured MCP servers.
-Each resource object includes a 'server' field indicating which server it's from.
-
-Usage examples:
-- List all resources from all servers: \`listMcpResources\`
-- List resources from a specific server: \`listMcpResources({ server: "myserver" })\`
+export const DESCRIPTION = `
+Lists available resources from configured MCP servers.
+Each resource object includes a 'server' field indicating which server it's from.
+
+Usage examples:
+- List all resources from all servers: \`listMcpResources\`
+- List resources from a specific server: \`listMcpResources({ server: "myserver" })\`
 `;
-export const PROMPT = `
-List available resources from configured MCP servers.
-Each returned resource will include all standard MCP resource fields plus a 'server' field 
-indicating which server the resource belongs to.
-
-Parameters:
-- server (optional): The name of a specific MCP server to get resources from. If not provided,
-  resources from all servers will be returned.
+export const PROMPT = `
+List available resources from configured MCP servers.
+Each returned resource will include all standard MCP resource fields plus a 'server' field 
+indicating which server the resource belongs to.
+
+Parameters:
+- server (optional): The name of a specific MCP server to get resources from. If not provided,
+  resources from all servers will be returned.
 `;

package/dist/src/tools/PowerShellTool/PowerShellTool.js

@@ -3,6 +3,8 @@ import { jsx as _jsx } from "react/jsx-runtime";
 import { copyFile, stat as fsStat, truncate as fsTruncate, link } from 'fs/promises';
 import { z } from 'zod/v4';
 import { getKairosActive } from '../../bootstrap/state.js';
+import { isCoreToolsEnabled } from '../../core/tools/contracts.js';
+import { startCoreShellCommand } from '../../core/tools/shellCore.js';
 import { TOOL_SUMMARY_MAX_LENGTH } from '../../constants/toolLimits.js';
 import { logEvent } from '../../services/analytics/index.js';
 import { buildTool } from '../../Tool.js';
@@ -640,9 +642,30 @@ async function* runPowerShellCommand({ input, abortController, setAppState, setT
             interrupted: false
         };
     }
+    const powershellExecOptions = {
+        timeout: timeoutMs,
+        onProgress(lastLines, allLines, totalLines, totalBytes, isIncomplete) {
+            lastProgressOutput = lastLines;
+            fullOutput = allLines;
+            lastTotalLines = totalLines;
+            lastTotalBytes = isIncomplete ? totalBytes : 0;
+        },
+        preventCwdChanges,
+        // Sandbox works on Linux/macOS/WSL2 — pwsh there is a native binary and
+        // SandboxManager.wrapWithSandbox wraps it same as bash (Shell.ts uses
+        // /bin/sh for the outer spawn to parse the POSIX-quoted bwrap/sandbox-exec
+        // string). On Windows native, sandbox is unsupported; shouldUseSandbox()
+        // returns false via isSandboxingEnabled() → isSupportedPlatform() → false.
+        // The explicit platform check is redundant-but-obvious.
+        shouldUseSandbox: getPlatform() === 'windows' ? false : shouldUseSandbox({
+            command,
+            dangerouslyDisableSandbox
+        }),
+        shouldAutoBackground
+    };
     let shellCommand;
     try {
-        shellCommand = await exec(command, abortController.signal, 'powershell', {
+        shellCommand = await (isCoreToolsEnabled() ? startCoreShellCommand({ command, timeoutMs, shellType: 'powershell', execOptions: powershellExecOptions }, { abortSignal: abortController.signal }) : exec(command, abortController.signal, 'powershell', {
             timeout: timeoutMs,
             onProgress(lastLines, allLines, totalLines, totalBytes, isIncomplete) {
                 lastProgressOutput = lastLines;
@@ -662,7 +685,7 @@ async function* runPowerShellCommand({ input, abortController, setAppState, setT
                 dangerouslyDisableSandbox
             }),
             shouldAutoBackground
-        });
+        }));
     }
     catch (e) {
         logError(e);

package/dist/src/tools/ReadMcpResourceTool/prompt.js

@@ -1,15 +1,15 @@
-export const DESCRIPTION = `
-Reads a specific resource from an MCP server.
-- server: The name of the MCP server to read from
-- uri: The URI of the resource to read
-
-Usage examples:
-- Read a resource from a server: \`readMcpResource({ server: "myserver", uri: "my-resource-uri" })\`
+export const DESCRIPTION = `
+Reads a specific resource from an MCP server.
+- server: The name of the MCP server to read from
+- uri: The URI of the resource to read
+
+Usage examples:
+- Read a resource from a server: \`readMcpResource({ server: "myserver", uri: "my-resource-uri" })\`
 `;
-export const PROMPT = `
-Reads a specific resource from an MCP server, identified by server name and resource URI.
-
-Parameters:
-- server (required): The name of the MCP server from which to read the resource
-- uri (required): The URI of the resource to read
+export const PROMPT = `
+Reads a specific resource from an MCP server, identified by server name and resource URI.
+
+Parameters:
+- server (required): The name of the MCP server from which to read the resource
+- uri (required): The URI of the resource to read
 `;

package/dist/src/tools/SendMessageTool/prompt.js

@@ -2,46 +2,46 @@ import { feature } from '../../recovery/bunBundleShim.js';
 export const DESCRIPTION = 'Send a message to another agent';
 export function getPrompt() {
     const udsRow = feature('UDS_INBOX')
-        ? `\n| \`"uds:/path/to.sock"\` | Local Claude session's socket (same machine; use \`ListPeers\`) |
+        ? `\n| \`"uds:/path/to.sock"\` | Local Claude session's socket (same machine; use \`ListPeers\`) |
 | \`"bridge:session_..."\` | Remote Control peer session (cross-machine; use \`ListPeers\`) |`
         : '';
     const udsSection = feature('UDS_INBOX')
-        ? `\n\n## Cross-session
-
-Use \`ListPeers\` to discover targets, then:
-
-\`\`\`json
-{"to": "uds:/tmp/cc-socks/1234.sock", "message": "check if tests pass over there"}
-{"to": "bridge:session_01AbCd...", "message": "what branch are you on?"}
-\`\`\`
-
+        ? `\n\n## Cross-session
+
+Use \`ListPeers\` to discover targets, then:
+
+\`\`\`json
+{"to": "uds:/tmp/cc-socks/1234.sock", "message": "check if tests pass over there"}
+{"to": "bridge:session_01AbCd...", "message": "what branch are you on?"}
+\`\`\`
+
 A listed peer is alive and will process your message — no "busy" state; messages enqueue and drain at the receiver's next tool round. Your message arrives wrapped as \`<cross-session-message from="...">\`. **To reply to an incoming message, copy its \`from\` attribute as your \`to\`.**`
         : '';
-    return `
-# SendMessage
-
-Send a message to another agent.
-
-\`\`\`json
-{"to": "researcher", "summary": "assign task 1", "message": "start on task #1"}
-\`\`\`
-
-| \`to\` | |
-|---|---|
-| \`"researcher"\` | Teammate by name |
-| \`"*"\` | Broadcast to all teammates — expensive (linear in team size), use only when everyone genuinely needs it |${udsRow}
-
-Your plain text output is NOT visible to other agents — to communicate, you MUST call this tool. Messages from teammates are delivered automatically; you don't check an inbox. Refer to teammates by name, never by UUID. When relaying, don't quote the original — it's already rendered to the user.${udsSection}
-
-## Protocol responses (legacy)
-
-If you receive a JSON message with \`type: "shutdown_request"\` or \`type: "plan_approval_request"\`, respond with the matching \`_response\` type — echo the \`request_id\`, set \`approve\` true/false:
-
-\`\`\`json
-{"to": "team-lead", "message": {"type": "shutdown_response", "request_id": "...", "approve": true}}
-{"to": "researcher", "message": {"type": "plan_approval_response", "request_id": "...", "approve": false, "feedback": "add error handling"}}
-\`\`\`
-
-Approving shutdown terminates your process. Rejecting plan sends the teammate back to revise. Don't originate \`shutdown_request\` unless asked. Don't send structured JSON status messages — use TaskUpdate.
+    return `
+# SendMessage
+
+Send a message to another agent.
+
+\`\`\`json
+{"to": "researcher", "summary": "assign task 1", "message": "start on task #1"}
+\`\`\`
+
+| \`to\` | |
+|---|---|
+| \`"researcher"\` | Teammate by name |
+| \`"*"\` | Broadcast to all teammates — expensive (linear in team size), use only when everyone genuinely needs it |${udsRow}
+
+Your plain text output is NOT visible to other agents — to communicate, you MUST call this tool. Messages from teammates are delivered automatically; you don't check an inbox. Refer to teammates by name, never by UUID. When relaying, don't quote the original — it's already rendered to the user.${udsSection}
+
+## Protocol responses (legacy)
+
+If you receive a JSON message with \`type: "shutdown_request"\` or \`type: "plan_approval_request"\`, respond with the matching \`_response\` type — echo the \`request_id\`, set \`approve\` true/false:
+
+\`\`\`json
+{"to": "team-lead", "message": {"type": "shutdown_response", "request_id": "...", "approve": true}}
+{"to": "researcher", "message": {"type": "plan_approval_response", "request_id": "...", "approve": false, "feedback": "add error handling"}}
+\`\`\`
+
+Approving shutdown terminates your process. Rejecting plan sends the teammate back to revise. Don't originate \`shutdown_request\` unless asked. Don't send structured JSON status messages — use TaskUpdate.
 `.trim();
 }

package/dist/src/tools/SkillTool/prompt.js

@@ -126,27 +126,27 @@ export function formatCommandsWithinBudget(commands, contextWindowTokens) {
         .join('\n');
 }
 export const getPrompt = memoize(async (_cwd) => {
-    return `Execute a skill within the main conversation
-
-When users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge.
-
-When users reference a "slash command" or "/<something>" (e.g., "/commit", "/review-pr"), they are referring to a skill. Use this tool to invoke it.
-
-How to invoke:
-- Use this tool with the skill name and optional arguments
-- Examples:
-  - \`skill: "pdf"\` - invoke the pdf skill
-  - \`skill: "commit", args: "-m 'Fix bug'"\` - invoke with arguments
-  - \`skill: "review-pr", args: "123"\` - invoke with arguments
-  - \`skill: "ms-office-suite:pdf"\` - invoke using fully qualified name
-
-Important:
-- Available skills are listed in system-reminder messages in the conversation
-- When a skill matches the user's request, this is a BLOCKING REQUIREMENT: invoke the relevant Skill tool BEFORE generating any other response about the task
-- NEVER mention a skill without actually calling this tool
-- Do not invoke a skill that is already running
-- Do not use this tool for built-in CLI commands (like /help, /clear, etc.)
-- If you see a <${COMMAND_NAME_TAG}> tag in the current conversation turn, the skill has ALREADY been loaded - follow the instructions directly instead of calling this tool again
+    return `Execute a skill within the main conversation
+
+When users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge.
+
+When users reference a "slash command" or "/<something>" (e.g., "/commit", "/review-pr"), they are referring to a skill. Use this tool to invoke it.
+
+How to invoke:
+- Use this tool with the skill name and optional arguments
+- Examples:
+  - \`skill: "pdf"\` - invoke the pdf skill
+  - \`skill: "commit", args: "-m 'Fix bug'"\` - invoke with arguments
+  - \`skill: "review-pr", args: "123"\` - invoke with arguments
+  - \`skill: "ms-office-suite:pdf"\` - invoke using fully qualified name
+
+Important:
+- Available skills are listed in system-reminder messages in the conversation
+- When a skill matches the user's request, this is a BLOCKING REQUIREMENT: invoke the relevant Skill tool BEFORE generating any other response about the task
+- NEVER mention a skill without actually calling this tool
+- Do not invoke a skill that is already running
+- Do not use this tool for built-in CLI commands (like /help, /clear, etc.)
+- If you see a <${COMMAND_NAME_TAG}> tag in the current conversation turn, the skill has ALREADY been loaded - follow the instructions directly instead of calling this tool again
 `;
 });
 export async function getSkillToolInfo(cwd) {

package/dist/src/tools/SleepTool/prompt.js

@@ -1,14 +1,14 @@
 import { TICK_TAG } from '../../constants/xml.js';
 export const SLEEP_TOOL_NAME = 'Sleep';
 export const DESCRIPTION = 'Wait for a specified duration';
-export const SLEEP_TOOL_PROMPT = `Wait for a specified duration. The user can interrupt the sleep at any time.
-
-Use this when the user tells you to sleep or rest, when you have nothing to do, or when you're waiting for something.
-
-You may receive <${TICK_TAG}> prompts — these are periodic check-ins. Look for useful work to do before sleeping.
-
-You can call this concurrently with other tools — it won't interfere with them.
-
-Prefer this over \`Bash(sleep ...)\` — it doesn't hold a shell process.
-
+export const SLEEP_TOOL_PROMPT = `Wait for a specified duration. The user can interrupt the sleep at any time.
+
+Use this when the user tells you to sleep or rest, when you have nothing to do, or when you're waiting for something.
+
+You may receive <${TICK_TAG}> prompts — these are periodic check-ins. Look for useful work to do before sleeping.
+
+You can call this concurrently with other tools — it won't interfere with them.
+
+Prefer this over \`Bash(sleep ...)\` — it doesn't hold a shell process.
+
 Each wake-up costs an API call, but the prompt cache expires after 5 minutes of inactivity — balance accordingly.`;

package/dist/src/tools/TaskCreateTool/prompt.js

@@ -5,48 +5,48 @@ export function getPrompt() {
         ? ' and potentially assigned to teammates'
         : '';
     const teammateTips = isAgentSwarmsEnabled()
-        ? `- Include enough detail in the description for another agent to understand and complete the task
-- New tasks are created with status 'pending' and no owner - use TaskUpdate with the \`owner\` parameter to assign them
+        ? `- Include enough detail in the description for another agent to understand and complete the task
+- New tasks are created with status 'pending' and no owner - use TaskUpdate with the \`owner\` parameter to assign them
 `
         : '';
-    return `Use this tool to create a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
-It also helps the user understand the progress of the task and overall progress of their requests.
-
-## When to Use This Tool
-
-Use this tool proactively in these scenarios:
-
-- Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
-- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations${teammateContext}
-- Plan mode - When using plan mode, create a task list to track the work
-- User explicitly requests todo list - When the user directly asks you to use the todo list
-- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
-- After receiving new instructions - Immediately capture user requirements as tasks
-- When you start working on a task - Mark it as in_progress BEFORE beginning work
-- After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
-
-## When NOT to Use This Tool
-
-Skip using this tool when:
-- There is only a single, straightforward task
-- The task is trivial and tracking it provides no organizational benefit
-- The task can be completed in less than 3 trivial steps
-- The task is purely conversational or informational
-
-NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
-
-## Task Fields
-
-- **subject**: A brief, actionable title in imperative form (e.g., "Fix authentication bug in login flow")
-- **description**: What needs to be done
-- **activeForm** (optional): Present continuous form shown in the spinner when the task is in_progress (e.g., "Fixing authentication bug"). If omitted, the spinner shows the subject instead.
-
-All tasks are created with status \`pending\`.
-
-## Tips
-
-- Create tasks with clear, specific subjects that describe the outcome
-- After creating tasks, use TaskUpdate to set up dependencies (blocks/blockedBy) if needed
-${teammateTips}- Check TaskList first to avoid creating duplicate tasks
+    return `Use this tool to create a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
+It also helps the user understand the progress of the task and overall progress of their requests.
+
+## When to Use This Tool
+
+Use this tool proactively in these scenarios:
+
+- Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations${teammateContext}
+- Plan mode - When using plan mode, create a task list to track the work
+- User explicitly requests todo list - When the user directly asks you to use the todo list
+- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+- After receiving new instructions - Immediately capture user requirements as tasks
+- When you start working on a task - Mark it as in_progress BEFORE beginning work
+- After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
+
+## When NOT to Use This Tool
+
+Skip using this tool when:
+- There is only a single, straightforward task
+- The task is trivial and tracking it provides no organizational benefit
+- The task can be completed in less than 3 trivial steps
+- The task is purely conversational or informational
+
+NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
+
+## Task Fields
+
+- **subject**: A brief, actionable title in imperative form (e.g., "Fix authentication bug in login flow")
+- **description**: What needs to be done
+- **activeForm** (optional): Present continuous form shown in the spinner when the task is in_progress (e.g., "Fixing authentication bug"). If omitted, the spinner shows the subject instead.
+
+All tasks are created with status \`pending\`.
+
+## Tips
+
+- Create tasks with clear, specific subjects that describe the outcome
+- After creating tasks, use TaskUpdate to set up dependencies (blocks/blockedBy) if needed
+${teammateTips}- Check TaskList first to avoid creating duplicate tasks
 `;
 }

package/dist/src/tools/TaskGetTool/prompt.js

@@ -1,23 +1,23 @@
 export const DESCRIPTION = 'Get a task by ID from the task list';
-export const PROMPT = `Use this tool to retrieve a task by its ID from the task list.
-
-## When to Use This Tool
-
-- When you need the full description and context before starting work on a task
-- To understand task dependencies (what it blocks, what blocks it)
-- After being assigned a task, to get complete requirements
-
-## Output
-
-Returns full task details:
-- **subject**: Task title
-- **description**: Detailed requirements and context
-- **status**: 'pending', 'in_progress', or 'completed'
-- **blocks**: Tasks waiting on this one to complete
-- **blockedBy**: Tasks that must complete before this one can start
-
-## Tips
-
-- After fetching a task, verify its blockedBy list is empty before beginning work.
-- Use TaskList to see all tasks in summary form.
+export const PROMPT = `Use this tool to retrieve a task by its ID from the task list.
+
+## When to Use This Tool
+
+- When you need the full description and context before starting work on a task
+- To understand task dependencies (what it blocks, what blocks it)
+- After being assigned a task, to get complete requirements
+
+## Output
+
+Returns full task details:
+- **subject**: Task title
+- **description**: Detailed requirements and context
+- **status**: 'pending', 'in_progress', or 'completed'
+- **blocks**: Tasks waiting on this one to complete
+- **blockedBy**: Tasks that must complete before this one can start
+
+## Tips
+
+- After fetching a task, verify its blockedBy list is empty before beginning work.
+- Use TaskList to see all tasks in summary form.
 `;

package/dist/src/tools/TaskListTool/prompt.js

@@ -2,43 +2,43 @@ import { isAgentSwarmsEnabled } from '../../utils/agentSwarmsEnabled.js';
 export const DESCRIPTION = 'List all tasks in the task list';
 export function getPrompt() {
     const teammateUseCase = isAgentSwarmsEnabled()
-        ? `- Before assigning tasks to teammates, to see what's available
+        ? `- Before assigning tasks to teammates, to see what's available
 `
         : '';
     const idDescription = isAgentSwarmsEnabled()
         ? '- **id**: Task identifier (use with TaskGet, TaskUpdate)'
         : '- **id**: Task identifier (use with TaskGet, TaskUpdate)';
     const teammateWorkflow = isAgentSwarmsEnabled()
-        ? `
-## Teammate Workflow
-
-When working as a teammate:
-1. After completing your current task, call TaskList to find available work
-2. Look for tasks with status 'pending', no owner, and empty blockedBy
-3. **Prefer tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
-4. Claim an available task using TaskUpdate (set \`owner\` to your name), or wait for leader assignment
-5. If blocked, focus on unblocking tasks or notify the team lead
+        ? `
+## Teammate Workflow
+
+When working as a teammate:
+1. After completing your current task, call TaskList to find available work
+2. Look for tasks with status 'pending', no owner, and empty blockedBy
+3. **Prefer tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
+4. Claim an available task using TaskUpdate (set \`owner\` to your name), or wait for leader assignment
+5. If blocked, focus on unblocking tasks or notify the team lead
 `
         : '';
-    return `Use this tool to list all tasks in the task list.
-
-## When to Use This Tool
-
-- To see what tasks are available to work on (status: 'pending', no owner, not blocked)
-- To check overall progress on the project
-- To find tasks that are blocked and need dependencies resolved
-${teammateUseCase}- After completing a task, to check for newly unblocked work or claim the next available task
-- **Prefer working on tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
-
-## Output
-
-Returns a summary of each task:
-${idDescription}
-- **subject**: Brief description of the task
-- **status**: 'pending', 'in_progress', or 'completed'
-- **owner**: Agent ID if assigned, empty if available
-- **blockedBy**: List of open task IDs that must be resolved first (tasks with blockedBy cannot be claimed until dependencies resolve)
-
-Use TaskGet with a specific task ID to view full details including description and comments.
+    return `Use this tool to list all tasks in the task list.
+
+## When to Use This Tool
+
+- To see what tasks are available to work on (status: 'pending', no owner, not blocked)
+- To check overall progress on the project
+- To find tasks that are blocked and need dependencies resolved
+${teammateUseCase}- After completing a task, to check for newly unblocked work or claim the next available task
+- **Prefer working on tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
+
+## Output
+
+Returns a summary of each task:
+${idDescription}
+- **subject**: Brief description of the task
+- **status**: 'pending', 'in_progress', or 'completed'
+- **owner**: Agent ID if assigned, empty if available
+- **blockedBy**: List of open task IDs that must be resolved first (tasks with blockedBy cannot be claimed until dependencies resolve)
+
+Use TaskGet with a specific task ID to view full details including description and comments.
 ${teammateWorkflow}`;
 }

package/dist/src/tools/TaskOutputTool/TaskOutputTool.js

@@ -135,14 +135,14 @@ export const TaskOutputTool = buildTool({
         return input.task_id;
     },
     async prompt() {
-        return `DEPRECATED: Prefer using the Read tool on the task's output file path instead. Background tasks return their output file path in the tool result, and you receive a <task-notification> with the same path when the task completes — Read that file directly.
-
-- Retrieves output from a running or completed task (background shell, agent, or remote session)
-- Takes a task_id parameter identifying the task
-- Returns the task output along with status information
-- Use block=true (default) to wait for task completion
-- Use block=false for non-blocking check of current status
-- Task IDs can be found using the /tasks command
+        return `DEPRECATED: Prefer using the Read tool on the task's output file path instead. Background tasks return their output file path in the tool result, and you receive a <task-notification> with the same path when the task completes — Read that file directly.
+
+- Retrieves output from a running or completed task (background shell, agent, or remote session)
+- Takes a task_id parameter identifying the task
+- Returns the task output along with status information
+- Use block=true (default) to wait for task completion
+- Use block=false for non-blocking check of current status
+- Task IDs can be found using the /tasks command
 - Works with all task types: background shells, async agents, and remote sessions`;
     },
     async validateInput({ task_id }, { getAppState }) {

package/dist/src/tools/TaskStopTool/prompt.js

@@ -1,7 +1,7 @@
 export const TASK_STOP_TOOL_NAME = 'TaskStop';
-export const DESCRIPTION = `
-- Stops a running background task by its ID
-- Takes a task_id parameter identifying the task to stop
-- Returns a success or failure status
-- Use this tool when you need to terminate a long-running task
+export const DESCRIPTION = `
+- Stops a running background task by its ID
+- Takes a task_id parameter identifying the task to stop
+- Returns a success or failure status
+- Use this tool when you need to terminate a long-running task
 `;