@iaforged/context-code 1.2.12 → 1.3.6

package/dist/src/utils/advisor.js

@@ -59,19 +59,19 @@ export function getAdvisorUsage(usage) {
     }
     return iterations.filter(it => it.type === 'advisor_message');
 }
-export const ADVISOR_TOOL_INSTRUCTIONS = `# Advisor Tool
-
-You have access to an \`advisor\` tool backed by a stronger reviewer model. It takes NO parameters -- when you call it, your entire conversation history is automatically forwarded. The advisor sees the task, every tool call you've made, every result you've seen.
-
-Call advisor BEFORE substantive work -- before writing code, before committing to an interpretation, before building on an assumption. If the task requires orientation first (finding files, reading code, seeing what's there), do that, then call advisor. Orientation is not substantive work. Writing, editing, and declaring an answer are.
-
-Also call advisor:
-- When you believe the task is complete. BEFORE this call, make your deliverable durable: write the file, stage the change, save the result. The advisor call takes time; if the session ends during it, a durable result persists and an unwritten one doesn't.
-- When stuck -- errors recurring, approach not converging, results that don't fit.
-- When considering a change of approach.
-
-On tasks longer than a few steps, call advisor at least once before committing to an approach and once before declaring done. On short reactive tasks where the next action is dictated by tool output you just read, you don't need to keep calling -- the advisor adds most of its value on the first call, before the approach crystallizes.
-
-Give the advice serious weight. If you follow a step and it fails empirically, or you have primary-source evidence that contradicts a specific claim (the file says X, the code does Y), adapt. A passing self-test is not evidence the advice is wrong -- it's evidence your test doesn't check what the advice is checking.
-
+export const ADVISOR_TOOL_INSTRUCTIONS = `# Advisor Tool
+
+You have access to an \`advisor\` tool backed by a stronger reviewer model. It takes NO parameters -- when you call it, your entire conversation history is automatically forwarded. The advisor sees the task, every tool call you've made, every result you've seen.
+
+Call advisor BEFORE substantive work -- before writing code, before committing to an interpretation, before building on an assumption. If the task requires orientation first (finding files, reading code, seeing what's there), do that, then call advisor. Orientation is not substantive work. Writing, editing, and declaring an answer are.
+
+Also call advisor:
+- When you believe the task is complete. BEFORE this call, make your deliverable durable: write the file, stage the change, save the result. The advisor call takes time; if the session ends during it, a durable result persists and an unwritten one doesn't.
+- When stuck -- errors recurring, approach not converging, results that don't fit.
+- When considering a change of approach.
+
+On tasks longer than a few steps, call advisor at least once before committing to an approach and once before declaring done. On short reactive tasks where the next action is dictated by tool output you just read, you don't need to keep calling -- the advisor adds most of its value on the first call, before the approach crystallizes.
+
+Give the advice serious weight. If you follow a step and it fails empirically, or you have primary-source evidence that contradicts a specific claim (the file says X, the code does Y), adapt. A passing self-test is not evidence the advice is wrong -- it's evidence your test doesn't check what the advice is checking.
+
 If you've already retrieved data pointing one way and the advisor points another: don't silently switch. Surface the conflict in one more advisor call -- "I found X, you suggest Y, which constraint breaks the tie?" The advisor saw your evidence but may have underweighted it; a reconcile call is cheaper than committing to the wrong branch.`;

package/dist/src/utils/api.js

@@ -348,8 +348,8 @@ export function prependUserContext(messages, context) {
         createUserMessage({
             content: `<system-reminder>\nAs you answer the user's questions, you can use the following context:\n${Object.entries(context)
                 .map(([key, value]) => `# ${key}\n${value}`)
-                .join('\n')}
-
+                .join('\n')}
+
       IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n`,
             isMeta: true,
         }),

package/dist/src/utils/claudeInChrome/setup.js

@@ -246,15 +246,15 @@ async function createWrapperScript(command) {
         ? join(chromeDir, 'chrome-native-host.bat')
         : join(chromeDir, 'chrome-native-host');
     const scriptContent = platform === 'windows'
-        ? `@echo off
-REM Chrome native host wrapper script
-REM Generated by Context Code - do not edit manually
-${command}
+        ? `@echo off
+REM Chrome native host wrapper script
+REM Generated by Context Code - do not edit manually
+${command}
 `
-        : `#!/bin/sh
-# Chrome native host wrapper script
-# Generated by Context Code - do not edit manually
-exec ${command}
+        : `#!/bin/sh
+# Chrome native host wrapper script
+# Generated by Context Code - do not edit manually
+exec ${command}
 `;
     // Check if content matches to avoid unnecessary writes
     const existingContent = await readFile(wrapperPath, 'utf-8').catch(() => null);

package/dist/src/utils/computerControlMcp/common.js

@@ -0,0 +1,24 @@
+/**
+ * Constants for the Computer Control MCP server.
+ */
+export const COMPUTER_CONTROL_MCP_SERVER_NAME = 'computer-control';
+export function isComputerControlMCPServer(name) {
+    return name === COMPUTER_CONTROL_MCP_SERVER_NAME;
+}
+export const COMPUTER_CONTROL_MCP_TOOLS = [
+    'click_screen',
+    'get_screen_size',
+    'type_text',
+    'take_screenshot',
+    'take_screenshot_with_ocr',
+    'move_mouse',
+    'mouse_down',
+    'mouse_up',
+    'drag_mouse',
+    'key_down',
+    'key_up',
+    'press_keys',
+    'list_windows',
+    'wait_milliseconds',
+    'activate_window'
+];

package/dist/src/utils/computerControlMcp/mcpServer.js

@@ -0,0 +1,22 @@
+import { spawn } from 'child_process';
+import { join } from 'path';
+import { getCwd } from '../cwd.js';
+import { COMPUTER_CONTROL_MCP_SERVER_NAME } from './common.js';
+export function runComputerControlMcpServer() {
+    const serverPath = join(getCwd(), 'CLI', 'src', 'utils', 'computerControlMcp', 'server');
+    // We assume 'uv' or 'python' is available and configured
+    // The README says 'uvx computer-control-mcp@latest' but since we have the code locally:
+    const pythonCommand = process.platform === 'win32' ? 'py' : 'python3';
+    const child = spawn(pythonCommand, ['-m', 'computer_control_mcp.server'], {
+        cwd: serverPath,
+        stdio: 'inherit',
+        env: {
+            ...process.env,
+            PYTHONPATH: join(serverPath, 'src')
+        }
+    });
+    child.on('error', (err) => {
+        console.error(`Failed to start ${COMPUTER_CONTROL_MCP_SERVER_NAME} server:`, err);
+    });
+    return child;
+}

package/dist/src/utils/computerControlMcp/setup.js

@@ -0,0 +1,26 @@
+import { join } from 'node:path';
+import { COMPUTER_CONTROL_MCP_SERVER_NAME, COMPUTER_CONTROL_MCP_TOOLS } from './common.js';
+import { buildMcpToolName } from '../../services/mcp/mcpStringUtils.js';
+import { getCwd } from '../cwd.js';
+/**
+ * Setup the Computer Control MCP server.
+ */
+export function setupComputerControlMCP() {
+    const allowedTools = COMPUTER_CONTROL_MCP_TOOLS.map(tool => buildMcpToolName(COMPUTER_CONTROL_MCP_SERVER_NAME, tool));
+    const serverPath = join(getCwd(), 'CLI', 'src', 'utils', 'computerControlMcp', 'server');
+    const pythonCommand = process.platform === 'win32' ? 'py' : 'python3';
+    return {
+        mcpConfig: {
+            [COMPUTER_CONTROL_MCP_SERVER_NAME]: {
+                type: 'stdio',
+                command: pythonCommand,
+                args: ['-m', 'computer_control_mcp.server'],
+                env: {
+                    PYTHONPATH: join(serverPath, 'src')
+                },
+                scope: 'dynamic',
+            },
+        },
+        allowedTools,
+    };
+}

package/dist/src/utils/heapDumpService.js

@@ -137,10 +137,10 @@ export async function performHeapDump(trigger = 'manual', dumpNumber = 0) {
         // the heap dump itself allocates memory and would skew the numbers.
         const diagnostics = await captureMemoryDiagnostics(trigger, dumpNumber);
         const toGB = (bytes) => (bytes / 1024 / 1024 / 1024).toFixed(3);
-        logForDebugging(`[HeapDump] Memory state:
-  heapUsed: ${toGB(diagnostics.memoryUsage.heapUsed)} GB (in snapshot)
-  external: ${toGB(diagnostics.memoryUsage.external)} GB (NOT in snapshot)
-  rss: ${toGB(diagnostics.memoryUsage.rss)} GB (total process)
+        logForDebugging(`[HeapDump] Memory state:
+  heapUsed: ${toGB(diagnostics.memoryUsage.heapUsed)} GB (in snapshot)
+  external: ${toGB(diagnostics.memoryUsage.external)} GB (NOT in snapshot)
+  rss: ${toGB(diagnostics.memoryUsage.rss)} GB (total process)
   ${diagnostics.analysis.recommendation}`);
         const dumpDir = getDesktopPath();
         await getFsImplementation().mkdir(dumpDir);

package/dist/src/utils/hooks/execAgentHook.js

@@ -65,13 +65,13 @@ _messages, agentName) {
                 structuredOutputTool,
             ];
             const systemPrompt = asSystemPrompt([
-                `You are verifying a stop condition in Context Code. Your task is to verify that the agent completed the given plan. The conversation transcript is available at: ${transcriptPath}\nYou can read this file to analyze the conversation history if needed.
-
-Use the available tools to inspect the codebase and verify the condition.
-Use as few steps as possible - be efficient and direct.
-
-When done, return your result using the ${SYNTHETIC_OUTPUT_TOOL_NAME} tool with:
-- ok: true if the condition is met
+                `You are verifying a stop condition in Context Code. Your task is to verify that the agent completed the given plan. The conversation transcript is available at: ${transcriptPath}\nYou can read this file to analyze the conversation history if needed.
+
+Use the available tools to inspect the codebase and verify the condition.
+Use as few steps as possible - be efficient and direct.
+
+When done, return your result using the ${SYNTHETIC_OUTPUT_TOOL_NAME} tool with:
+- ok: true if the condition is met
 - ok: false with reason if the condition is not met`,
             ]);
             const model = hook.model ?? getSmallFastModel();

package/dist/src/utils/hooks/execPromptHook.js

@@ -35,10 +35,10 @@ export async function execPromptHook(hook, hookName, hookEvent, jsonInput, signa
             const response = await queryModelWithoutStreaming({
                 messages: messagesToQuery,
                 systemPrompt: asSystemPrompt([
-                    `You are evaluating a hook in Context Code.
-
-Your response must be a JSON object matching one of the following schemas:
-1. If the condition is met, return: {"ok": true}
+                    `You are evaluating a hook in Context Code.
+
+Your response must be a JSON object matching one of the following schemas:
+1. If the condition is met, return: {"ok": true}
 2. If the condition is not met, return: {"ok": false, "reason": "Reason for why it is not met"}`,
                 ]),
                 thinkingConfig: { type: 'disabled' },

package/dist/src/utils/hooks/skillImprovement.js

@@ -69,27 +69,27 @@ function createSkillImprovementHook() {
             lastAnalyzedIndex = context.messages.length;
             return [
                 createUserMessage({
-                    content: `You are analyzing a conversation where a user is executing a skill (a repeatable process).
-Your job: identify if the user's recent messages contain preferences, requests, or corrections that should be permanently added to the skill definition for future runs.
-
-<skill_definition>
-${projectSkill.content}
-</skill_definition>
-
-<recent_messages>
-${formatRecentMessages(newMessages)}
-</recent_messages>
-
-Look for:
-- Requests to add, change, or remove steps: "can you also ask me X", "please do Y too", "don't do Z"
-- Preferences about how steps should work: "ask me about energy levels", "note the time", "use a casual tone"
-- Corrections: "no, do X instead", "always use Y", "make sure to..."
-
-Ignore:
-- Routine conversation that doesn't generalize (one-time answers, chitchat)
-- Things the skill already does
-
-Output a JSON array inside <updates> tags. Each item: {"section": "which step/section to modify or 'new step'", "change": "what to add/modify", "reason": "which user message prompted this"}.
+                    content: `You are analyzing a conversation where a user is executing a skill (a repeatable process).
+Your job: identify if the user's recent messages contain preferences, requests, or corrections that should be permanently added to the skill definition for future runs.
+
+<skill_definition>
+${projectSkill.content}
+</skill_definition>
+
+<recent_messages>
+${formatRecentMessages(newMessages)}
+</recent_messages>
+
+Look for:
+- Requests to add, change, or remove steps: "can you also ask me X", "please do Y too", "don't do Z"
+- Preferences about how steps should work: "ask me about energy levels", "note the time", "use a casual tone"
+- Corrections: "no, do X instead", "always use Y", "make sure to..."
+
+Ignore:
+- Routine conversation that doesn't generalize (one-time answers, chitchat)
+- Things the skill already does
+
+Output a JSON array inside <updates> tags. Each item: {"section": "which step/section to modify or 'new step'", "change": "what to add/modify", "reason": "which user message prompted this"}.
 Output <updates>[]</updates> if no updates are needed.`,
                 }),
             ];
@@ -160,21 +160,21 @@ export async function applySkillImprovement(skillName, updates) {
     const response = await queryModelWithoutStreaming({
         messages: [
             createUserMessage({
-                content: `You are editing a skill definition file. Apply the following improvements to the skill.
-
-<current_skill_file>
-${currentContent}
-</current_skill_file>
-
-<improvements>
-${updateList}
-</improvements>
-
-Rules:
-- Integrate the improvements naturally into the existing structure
-- Preserve frontmatter (--- block) exactly as-is
-- Preserve the overall format and style
-- Do not remove existing content unless an improvement explicitly replaces it
+                content: `You are editing a skill definition file. Apply the following improvements to the skill.
+
+<current_skill_file>
+${currentContent}
+</current_skill_file>
+
+<improvements>
+${updateList}
+</improvements>
+
+Rules:
+- Integrate the improvements naturally into the existing structure
+- Preserve frontmatter (--- block) exactly as-is
+- Preserve the overall format and style
+- Do not remove existing content unless an improvement explicitly replaces it
 - Output the complete updated file inside <updated_file> tags`,
             }),
         ],

package/dist/src/utils/mcp/dateTimeParser.js

@@ -40,15 +40,15 @@ export async function parseNaturalLanguageDateTime(input, format, signal) {
     const formatDescription = format === 'date'
         ? 'YYYY-MM-DD (date only, no time)'
         : `YYYY-MM-DDTHH:MM:SS${timezone} (full date-time with timezone)`;
-    const userPrompt = `Current context:
-- Current date and time: ${currentDateTime} (UTC)
-- Local timezone: ${timezone}
-- Day of week: ${dayOfWeek}
-
-User input: "${input}"
-
-Output format: ${formatDescription}
-
+    const userPrompt = `Current context:
+- Current date and time: ${currentDateTime} (UTC)
+- Local timezone: ${timezone}
+- Day of week: ${dayOfWeek}
+
+User input: "${input}"
+
+Output format: ${formatDescription}
+
 Parse the user's input into ISO 8601 format. Return ONLY the formatted string, or "INVALID" if the input is incomplete or unparseable.`;
     try {
         const result = await queryHaiku({

package/dist/src/utils/mcpValidation.js

@@ -57,8 +57,8 @@ function getMaxMcpOutputChars() {
     return getMaxMcpOutputTokens() * 4;
 }
 function getTruncationMessage() {
-    return `\n\n[OUTPUT TRUNCATED - exceeded ${getMaxMcpOutputTokens()} token limit]
-
+    return `\n\n[OUTPUT TRUNCATED - exceeded ${getMaxMcpOutputTokens()} token limit]
+
 The tool output was truncated. If this MCP server provides pagination or filtering tools, use them to retrieve specific portions of the data. If pagination is not available, inform the user that you are working with truncated output and results may be incomplete.`;
 }
 function truncateString(content, maxChars) {