@iaforged/context-code 1.2.12 → 1.3.6

package/dist/src/tasks/LocalAgentTask/LocalAgentTask.js

@@ -145,11 +145,11 @@ export function enqueueAgentNotification({ taskId, description, status, error, s
     const resultSection = finalMessage ? `\n<result>${finalMessage}</result>` : '';
     const usageSection = usage ? `\n<usage><total_tokens>${usage.totalTokens}</total_tokens><tool_uses>${usage.toolUses}</tool_uses><duration_ms>${usage.durationMs}</duration_ms></usage>` : '';
     const worktreeSection = worktreePath ? `\n<${WORKTREE_TAG}><${WORKTREE_PATH_TAG}>${worktreePath}</${WORKTREE_PATH_TAG}>${worktreeBranch ? `<${WORKTREE_BRANCH_TAG}>${worktreeBranch}</${WORKTREE_BRANCH_TAG}>` : ''}</${WORKTREE_TAG}>` : '';
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${STATUS_TAG}>${status}</${STATUS_TAG}>
-<${SUMMARY_TAG}>${summary}</${SUMMARY_TAG}>${resultSection}${usageSection}${worktreeSection}
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${STATUS_TAG}>${status}</${STATUS_TAG}>
+<${SUMMARY_TAG}>${summary}</${SUMMARY_TAG}>${resultSection}${usageSection}${worktreeSection}
 </${TASK_NOTIFICATION_TAG}>`;
     enqueuePendingNotification({
         value: message,

package/dist/src/tasks/LocalMainSessionTask.js

@@ -169,11 +169,11 @@ function enqueueMainSessionNotification(taskId, description, status, setAppState
         ? `\n<${TOOL_USE_ID_TAG}>${toolUseId}</${TOOL_USE_ID_TAG}>`
         : '';
     const outputPath = getTaskOutputPath(taskId);
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${STATUS_TAG}>${status}</${STATUS_TAG}>
-<${SUMMARY_TAG}>${summary}</${SUMMARY_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${STATUS_TAG}>${status}</${STATUS_TAG}>
+<${SUMMARY_TAG}>${summary}</${SUMMARY_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
     enqueuePendingNotification({ value: message, mode: 'task-notification' });
 }

package/dist/src/tasks/LocalShellTask/LocalShellTask.js

@@ -71,14 +71,14 @@ function startStallWatchdog(taskId, description, kind, toolUseId, agentId) {
                 // signal and an unknown value falls through to 'completed',
                 // falsely closing the task for SDK consumers. Statusless
                 // notifications are skipped by the SDK emitter (progress ping).
-                const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${SUMMARY_TAG}>${escapeXml(summary)}</${SUMMARY_TAG}>
-</${TASK_NOTIFICATION_TAG}>
-Last output:
-${content.trimEnd()}
-
+                const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${SUMMARY_TAG}>${escapeXml(summary)}</${SUMMARY_TAG}>
+</${TASK_NOTIFICATION_TAG}>
+Last output:
+${content.trimEnd()}
+
 The command is likely blocked on an interactive prompt. Kill this task and re-run with piped input (e.g., \`echo y | command\`) or a non-interactive flag if one exists.`;
                 enqueuePendingNotification({
                     value: message,
@@ -151,11 +151,11 @@ function enqueueShellNotification(taskId, description, status, exitCode, setAppS
     }
     const outputPath = getTaskOutputPath(taskId);
     const toolUseIdLine = toolUseId ? `\n<${TOOL_USE_ID_TAG}>${toolUseId}</${TOOL_USE_ID_TAG}>` : '';
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${STATUS_TAG}>${status}</${STATUS_TAG}>
-<${SUMMARY_TAG}>${escapeXml(summary)}</${SUMMARY_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${STATUS_TAG}>${status}</${STATUS_TAG}>
+<${SUMMARY_TAG}>${escapeXml(summary)}</${SUMMARY_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
     enqueuePendingNotification({
         value: message,

package/dist/src/tasks/RemoteAgentTask/RemoteAgentTask.js

@@ -97,12 +97,12 @@ function enqueueRemoteNotification(taskId, title, status, setAppState, toolUseId
     const statusText = status === 'completed' ? 'completed successfully' : status === 'failed' ? 'failed' : 'was stopped';
     const toolUseIdLine = toolUseId ? `\n<${TOOL_USE_ID_TAG}>${toolUseId}</${TOOL_USE_ID_TAG}>` : '';
     const outputPath = getTaskOutputPath(taskId);
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${STATUS_TAG}>${status}</${STATUS_TAG}>
-<${SUMMARY_TAG}>Remote task "${title}" ${statusText}</${SUMMARY_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${STATUS_TAG}>${status}</${STATUS_TAG}>
+<${SUMMARY_TAG}>Remote task "${title}" ${statusText}</${SUMMARY_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
     enqueuePendingNotification({
         value: message,
@@ -153,12 +153,12 @@ export function enqueueUltraplanFailureNotification(taskId, sessionId, reason, s
     if (!markTaskNotified(taskId, setAppState))
         return;
     const sessionUrl = getRemoteTaskSessionUrl(sessionId);
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
-<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
-<${STATUS_TAG}>failed</${STATUS_TAG}>
-<${SUMMARY_TAG}>Ultraplan failed: ${reason}</${SUMMARY_TAG}>
-</${TASK_NOTIFICATION_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
+<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
+<${STATUS_TAG}>failed</${STATUS_TAG}>
+<${SUMMARY_TAG}>Ultraplan failed: ${reason}</${SUMMARY_TAG}>
+</${TASK_NOTIFICATION_TAG}>
 The remote Ultraplan session did not produce a plan (${reason}). Inspect the session at ${sessionUrl} and tell the user to retry locally with plan mode.`;
     enqueuePendingNotification({
         value: message,
@@ -256,14 +256,14 @@ function extractReviewTagFromLog(log) {
 function enqueueRemoteReviewNotification(taskId, reviewContent, setAppState) {
     if (!markTaskNotified(taskId, setAppState))
         return;
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
-<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
-<${STATUS_TAG}>completed</${STATUS_TAG}>
-<${SUMMARY_TAG}>Remote review completed</${SUMMARY_TAG}>
-</${TASK_NOTIFICATION_TAG}>
-The remote review produced the following findings:
-
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
+<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
+<${STATUS_TAG}>completed</${STATUS_TAG}>
+<${SUMMARY_TAG}>Remote review completed</${SUMMARY_TAG}>
+</${TASK_NOTIFICATION_TAG}>
+The remote review produced the following findings:
+
 ${reviewContent}`;
     enqueuePendingNotification({
         value: message,
@@ -276,12 +276,12 @@ ${reviewContent}`;
 function enqueueRemoteReviewFailureNotification(taskId, reason, setAppState) {
     if (!markTaskNotified(taskId, setAppState))
         return;
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
-<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
-<${STATUS_TAG}>failed</${STATUS_TAG}>
-<${SUMMARY_TAG}>Remote review failed: ${reason}</${SUMMARY_TAG}>
-</${TASK_NOTIFICATION_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${taskId}</${TASK_ID_TAG}>
+<${TASK_TYPE_TAG}>remote_agent</${TASK_TYPE_TAG}>
+<${STATUS_TAG}>failed</${STATUS_TAG}>
+<${SUMMARY_TAG}>Remote review failed: ${reason}</${SUMMARY_TAG}>
+</${TASK_NOTIFICATION_TAG}>
 Remote review did not produce output (${reason}). Tell the user to retry /ultrareview, or use /review for a local review instead.`;
     enqueuePendingNotification({
         value: message,

package/dist/src/tools/AgentTool/AgentTool.js

@@ -1141,10 +1141,10 @@ export const AgentTool = buildTool({
                 type: 'tool_result',
                 content: [{
                         type: 'text',
-                        text: `Spawned successfully.
-agent_id: ${spawnData.teammate_id}
-name: ${spawnData.name}
-team_name: ${spawnData.team_name}
+                        text: `Spawned successfully.
+agent_id: ${spawnData.teammate_id}
+name: ${spawnData.name}
+team_name: ${spawnData.team_name}
 The agent is now running and will receive instructions via mailbox.`
                     }]
             };
@@ -1201,9 +1201,9 @@ The agent is now running and will receive instructions via mailbox.`
                 type: 'tool_result',
                 content: [...contentOrMarker, {
                         type: 'text',
-                        text: `agentId: ${data.agentId} (use SendMessage with to: '${data.agentId}' to continue this agent)${worktreeInfoText}
-<usage>total_tokens: ${data.totalTokens}
-tool_uses: ${data.totalToolUseCount}
+                        text: `agentId: ${data.agentId} (use SendMessage with to: '${data.agentId}' to continue this agent)${worktreeInfoText}
+<usage>total_tokens: ${data.totalTokens}
+tool_uses: ${data.totalToolUseCount}
 duration_ms: ${data.totalDurationMs}</usage>`
                     }]
             };

package/dist/src/tools/AgentTool/built-in/claudeCodeGuideAgent.js

@@ -19,62 +19,62 @@ function getClaudeCodeGuideBasePrompt() {
     const localSearchHint = hasEmbeddedSearchTools()
         ? `${FILE_READ_TOOL_NAME}, \`find\`, and \`grep\``
         : `${FILE_READ_TOOL_NAME}, ${GLOB_TOOL_NAME}, and ${GREP_TOOL_NAME}`;
-    return `You are the Context Code guide agent. Your primary responsibility is helping users understand and use Context Code, the Context Agent SDK, and the underlying AI models (like Claude or GPT) effectively.
-
-**Your expertise spans three domains:**
-
-1. **Context Code** (the CLI tool): Installation, configuration, hooks, skills, MCP servers, keyboard shortcuts, IDE integrations, settings, and workflows.
-
-2. **Claude Agent SDK**: A framework for building custom AI agents based on Context Code technology. Available for Node.js/TypeScript and Python.
-
-3. **Claude API**: The Claude API (formerly known as the Anthropic API) for direct model interaction, tool use, and integrations.
-
-**Documentation sources:**
-
-- **Context Code docs** (${CONTEXT_CODE_DOCS_MAP_URL}): Fetch this for questions about the Context Code CLI tool, including:
-  - Installation, setup, and getting started
-  - Hooks (pre/post command execution)
-  - Custom skills
-  - MCP server configuration
-  - IDE integrations (VS Code, JetBrains)
-  - Settings files and configuration
-  - Keyboard shortcuts and hotkeys
-  - Subagents and plugins
-  - Sandboxing and security
-
-- **Context Agent SDK docs** (${CDP_DOCS_MAP_URL}): Fetch this for questions about building agents with the SDK, including:
-  - SDK overview and getting started (Python and TypeScript)
-  - Agent configuration + custom tools
-  - Session management and permissions
-  - MCP integration in agents
-  - Hosting and deployment
-  - Cost tracking and context management
-  Note: Agent SDK docs are part of the Claude API documentation at the same URL.
-
-- **Claude API docs** (${CDP_DOCS_MAP_URL}): Fetch this for questions about the Claude API (formerly the Anthropic API), including:
-  - Messages API and streaming
-  - Tool use (function calling) and Anthropic-defined tools (computer use, code execution, web search, text editor, bash, programmatic tool calling, tool search tool, context editing, Files API, structured outputs)
-  - Vision, PDF support, and citations
-  - Extended thinking and structured outputs
-  - MCP connector for remote MCP servers
-  - Cloud provider integrations (Bedrock, Vertex AI, Foundry)
-
-**Approach:**
-1. Determine which domain the user's question falls into
-2. Use ${WEB_FETCH_TOOL_NAME} to fetch the appropriate docs map
-3. Identify the most relevant documentation URLs from the map
-4. Fetch the specific documentation pages
-5. Provide clear, actionable guidance based on official documentation
-6. Use ${WEB_SEARCH_TOOL_NAME} if docs don't cover the topic
-7. Reference local project files (CLAUDE.md, .claude/ directory) when relevant using ${localSearchHint}
-
-**Guidelines:**
-- Always prioritize official documentation over assumptions
-- Keep responses concise and actionable
-- Include specific examples or code snippets when helpful
-- Reference exact documentation URLs in your responses
-- Help users discover features by proactively suggesting related commands, shortcuts, or capabilities
-
+    return `You are the Context Code guide agent. Your primary responsibility is helping users understand and use Context Code, the Context Agent SDK, and the underlying AI models (like Claude or GPT) effectively.
+
+**Your expertise spans three domains:**
+
+1. **Context Code** (the CLI tool): Installation, configuration, hooks, skills, MCP servers, keyboard shortcuts, IDE integrations, settings, and workflows.
+
+2. **Claude Agent SDK**: A framework for building custom AI agents based on Context Code technology. Available for Node.js/TypeScript and Python.
+
+3. **Claude API**: The Claude API (formerly known as the Anthropic API) for direct model interaction, tool use, and integrations.
+
+**Documentation sources:**
+
+- **Context Code docs** (${CONTEXT_CODE_DOCS_MAP_URL}): Fetch this for questions about the Context Code CLI tool, including:
+  - Installation, setup, and getting started
+  - Hooks (pre/post command execution)
+  - Custom skills
+  - MCP server configuration
+  - IDE integrations (VS Code, JetBrains)
+  - Settings files and configuration
+  - Keyboard shortcuts and hotkeys
+  - Subagents and plugins
+  - Sandboxing and security
+
+- **Context Agent SDK docs** (${CDP_DOCS_MAP_URL}): Fetch this for questions about building agents with the SDK, including:
+  - SDK overview and getting started (Python and TypeScript)
+  - Agent configuration + custom tools
+  - Session management and permissions
+  - MCP integration in agents
+  - Hosting and deployment
+  - Cost tracking and context management
+  Note: Agent SDK docs are part of the Claude API documentation at the same URL.
+
+- **Claude API docs** (${CDP_DOCS_MAP_URL}): Fetch this for questions about the Claude API (formerly the Anthropic API), including:
+  - Messages API and streaming
+  - Tool use (function calling) and Anthropic-defined tools (computer use, code execution, web search, text editor, bash, programmatic tool calling, tool search tool, context editing, Files API, structured outputs)
+  - Vision, PDF support, and citations
+  - Extended thinking and structured outputs
+  - MCP connector for remote MCP servers
+  - Cloud provider integrations (Bedrock, Vertex AI, Foundry)
+
+**Approach:**
+1. Determine which domain the user's question falls into
+2. Use ${WEB_FETCH_TOOL_NAME} to fetch the appropriate docs map
+3. Identify the most relevant documentation URLs from the map
+4. Fetch the specific documentation pages
+5. Provide clear, actionable guidance based on official documentation
+6. Use ${WEB_SEARCH_TOOL_NAME} if docs don't cover the topic
+7. Reference local project files (CLAUDE.md, .claude/ directory) when relevant using ${localSearchHint}
+
+**Guidelines:**
+- Always prioritize official documentation over assumptions
+- Keep responses concise and actionable
+- Include specific examples or code snippets when helpful
+- Reference exact documentation URLs in your responses
+- Help users discover features by proactively suggesting related commands, shortcuts, or capabilities
+
 Complete the user's request by providing accurate, documentation-based guidance.`;
 }
 function getFeedbackGuideline() {
@@ -153,20 +153,20 @@ export const CLAUDE_CODE_GUIDE_AGENT = {
         }
         // Add the feedback guideline (conditional based on whether user is using 3P services)
         const feedbackGuideline = getFeedbackGuideline();
-        const basePromptWithFeedback = `${getClaudeCodeGuideBasePrompt()}
+        const basePromptWithFeedback = `${getClaudeCodeGuideBasePrompt()}
 ${feedbackGuideline}`;
         // If we have any context to add, append it to the base system prompt
         if (contextSections.length > 0) {
-            return `${basePromptWithFeedback}
-
----
-
-# User's Current Configuration
-
-The user has the following custom setup in their environment:
-
-${contextSections.join('\n\n')}
-
+            return `${basePromptWithFeedback}
+
+---
+
+# User's Current Configuration
+
+The user has the following custom setup in their environment:
+
+${contextSections.join('\n\n')}
+
 When answering questions, consider these configured features and proactively suggest them when relevant.`;
         }
         // Return the base prompt if no context to add

package/dist/src/tools/AgentTool/forkSubagent.js

@@ -140,31 +140,31 @@ export function buildForkedMessages(directive, assistantMessage) {
     return [fullAssistantMessage, toolResultMessage];
 }
 export function buildChildMessage(directive) {
-    return `<${FORK_BOILERPLATE_TAG}>
-STOP. READ THIS FIRST.
-
-You are a forked worker process. You are NOT the main agent.
-
-RULES (non-negotiable):
-1. Your system prompt says "default to forking." IGNORE IT \u2014 that's for the parent. You ARE the fork. Do NOT spawn sub-agents; execute directly.
-2. Do NOT converse, ask questions, or suggest next steps
-3. Do NOT editorialize or add meta-commentary
-4. USE your tools directly: Bash, Read, Write, etc.
-5. If you modify files, commit your changes before reporting. Include the commit hash in your report.
-6. Do NOT emit text between tool calls. Use tools silently, then report once at the end.
-7. Stay strictly within your directive's scope. If you discover related systems outside your scope, mention them in one sentence at most — other workers cover those areas.
-8. Keep your report under 500 words unless the directive specifies otherwise. Be factual and concise.
-9. Your response MUST begin with "Scope:". No preamble, no thinking-out-loud.
-10. REPORT structured facts, then stop
-
-Output format (plain text labels, not markdown headers):
-  Scope: <echo back your assigned scope in one sentence>
-  Result: <the answer or key findings, limited to the scope above>
-  Key files: <relevant file paths — include for research tasks>
-  Files changed: <list with commit hash — include only if you modified files>
-  Issues: <list — include only if there are issues to flag>
-</${FORK_BOILERPLATE_TAG}>
-
+    return `<${FORK_BOILERPLATE_TAG}>
+STOP. READ THIS FIRST.
+
+You are a forked worker process. You are NOT the main agent.
+
+RULES (non-negotiable):
+1. Your system prompt says "default to forking." IGNORE IT \u2014 that's for the parent. You ARE the fork. Do NOT spawn sub-agents; execute directly.
+2. Do NOT converse, ask questions, or suggest next steps
+3. Do NOT editorialize or add meta-commentary
+4. USE your tools directly: Bash, Read, Write, etc.
+5. If you modify files, commit your changes before reporting. Include the commit hash in your report.
+6. Do NOT emit text between tool calls. Use tools silently, then report once at the end.
+7. Stay strictly within your directive's scope. If you discover related systems outside your scope, mention them in one sentence at most — other workers cover those areas.
+8. Keep your report under 500 words unless the directive specifies otherwise. Be factual and concise.
+9. Your response MUST begin with "Scope:". No preamble, no thinking-out-loud.
+10. REPORT structured facts, then stop
+
+Output format (plain text labels, not markdown headers):
+  Scope: <echo back your assigned scope in one sentence>
+  Result: <the answer or key findings, limited to the scope above>
+  Key files: <relevant file paths — include for research tasks>
+  Files changed: <list with commit hash — include only if you modified files>
+  Issues: <list — include only if there are issues to flag>
+</${FORK_BOILERPLATE_TAG}>
+
 ${FORK_DIRECTIVE_PREFIX}${directive}`;
 }
 /**