genaicode 0.15.0 → 2.0.0

package/dist/prompt/steps/step-codegen-planning.js

@@ -1,147 +0,0 @@
-import { ModelType } from '../../ai-service/common-types.js';
-import { getFunctionDefs } from '../function-calling.js';
-import { putSystemMessage } from '../../main/common/content-bus.js';
-import { StepResult } from './steps-types.js';
-import { executeStepEnsureContext } from './step-ensure-context.js';
-import { getRegisteredPlanningPreHooks, getRegisteredPlanningPostHooks } from '../../main/plugin-loader.js';
-export const PLANNING_PROMPT = `Please analyze the conversation so far and help plan the implementation:
-
-1. Review the conversation history and requirements
-2. Thoughtfully analyze the problem
-3. Create a step-by-step implementation plan
-4. List all files that will be affected during implementation
-
-Remember to:
-- Consider both direct and indirect dependencies
-- Think about how changes in one file might affect others
-- Include all necessary file paths
-- Explain your reasoning for each step
-- Consider edge cases and potential issues
-
-Output the plan using \`codegenPlanning\` function provding all the required fields.`;
-/**
- * Execute the codegen planning step
- * This step analyzes the conversation and produces a detailed implementation plan
- * before proceeding with actual code generation
- */
-export async function executeStepCodegenPlanning(generateContentFn, prompt, options) {
-    putSystemMessage('Starting codegen planning phase...');
-    // Execute pre-hooks to potentially modify the planning prompt
-    const modifiedPlanningPrompt = await executePlanningPreHooks(PLANNING_PROMPT, options);
-    // Add the planning prompt to the conversation
-    if (prompt.slice(-1)[0].type === 'user') {
-        prompt.slice(-1)[0].text += '\n\n' + modifiedPlanningPrompt;
-    }
-    else {
-        prompt.push({ type: 'user', text: modifiedPlanningPrompt });
-    }
-    const planningRequest = [
-        prompt,
-        {
-            functionDefs: getFunctionDefs(),
-            requiredFunctionName: 'codegenPlanning',
-            temperature: options.temperature ?? 0.7,
-            modelType: options.cheap ? ModelType.CHEAP : ModelType.DEFAULT,
-            expectedResponseType: {
-                text: false,
-                functionCall: true,
-                media: false,
-            },
-        },
-        options,
-    ];
-    try {
-        const planningResult = (await generateContentFn(...planningRequest))
-            .filter((item) => item.type === 'functionCall')
-            .map((item) => item.functionCall);
-        let codegenPlanningRequest = planningResult.find((call) => call.name === 'codegenPlanning');
-        if (codegenPlanningRequest) {
-            // Execute post-hooks to potentially modify the planning result
-            codegenPlanningRequest = await executePlanningPostHooks(codegenPlanningRequest, modifiedPlanningPrompt, options);
-            putSystemMessage('Planning phase completed, ensuring context completeness...');
-            // Ensure all necessary files are in context
-            const contextResult = await executeStepEnsureContext(prompt, codegenPlanningRequest, options);
-            if (contextResult === StepResult.BREAK) {
-                putSystemMessage('Failed to ensure context completeness during planning phase');
-                return StepResult.BREAK;
-            }
-            const planningResponseItem = {
-                type: 'assistant',
-                functionCalls: planningResult,
-            };
-            putSystemMessage('Planning phase completed successfully', codegenPlanningRequest, undefined, undefined, planningResponseItem);
-            // Store the planning response in conversation history
-            prompt.push(planningResponseItem);
-            prompt.push({
-                type: 'user',
-                functionResponses: planningResult.map((call) => ({ name: call.name, call_id: call.id })),
-                cache: true,
-            });
-            return StepResult.CONTINUE;
-        }
-        else {
-            putSystemMessage('Did not receive codegen planning result');
-            return StepResult.BREAK;
-        }
-    }
-    catch (error) {
-        putSystemMessage('Error during planning phase: ' + error.message);
-        return StepResult.BREAK;
-    }
-}
-/**
- * Execute registered planning pre-hooks
- * Returns modified prompt if any hook provides one, otherwise returns the original prompt
- */
-async function executePlanningPreHooks(originalPrompt, options) {
-    let modifiedPrompt = originalPrompt;
-    const preHooks = getRegisteredPlanningPreHooks();
-    if (preHooks.length > 0) {
-        putSystemMessage(`Executing ${preHooks.length} planning pre-hooks...`);
-        for (const hook of preHooks) {
-            try {
-                const result = await hook({
-                    prompt: modifiedPrompt,
-                    options,
-                });
-                if (result) {
-                    modifiedPrompt = result;
-                }
-            }
-            catch (error) {
-                putSystemMessage(`Error in planning pre-hook: ${error.message}`);
-                console.error('Planning pre-hook error:', error);
-            }
-        }
-    }
-    return modifiedPrompt;
-}
-/**
- * Execute registered planning post-hooks
- * Returns modified result if any hook provides one, otherwise returns the original result
- */
-async function executePlanningPostHooks(originalResult, originalPrompt, options) {
-    let modifiedResult = originalResult;
-    const postHooks = getRegisteredPlanningPostHooks();
-    if (postHooks.length > 0) {
-        putSystemMessage(`Executing ${postHooks.length} planning post-hooks...`);
-        for (const hook of postHooks) {
-            try {
-                const result = await hook({
-                    prompt: originalPrompt,
-                    options,
-                    result: modifiedResult,
-                });
-                if (result) {
-                    modifiedResult = result;
-                }
-            }
-            catch (error) {
-                putSystemMessage(`Error in planning post-hook: ${error.message}`);
-                console.error('Planning post-hook error:', error);
-            }
-        }
-    }
-    return modifiedResult;
-}
-//# sourceMappingURL=step-codegen-planning.js.map

package/dist/prompt/steps/step-codegen-planning.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"step-codegen-planning.js","sourceRoot":"","sources":["../../../src/prompt/steps/step-codegen-planning.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,SAAS,EAAE,MAAM,kCAAkC,CAAC;AAE7D,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAAE,gBAAgB,EAAE,MAAM,kCAAkC,CAAC;AACpE,OAAO,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAC9C,OAAO,EAAE,wBAAwB,EAAE,MAAM,0BAA0B,CAAC;AACpE,OAAO,EAAE,6BAA6B,EAAE,8BAA8B,EAAE,MAAM,6BAA6B,CAAC;AAE5G,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;qFAcsD,CAAC;AAEtF;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,0BAA0B,CAC9C,iBAA0C,EAC1C,MAAoB,EACpB,OAAuB;IAEvB,gBAAgB,CAAC,oCAAoC,CAAC,CAAC;IAEvD,8DAA8D;IAC9D,MAAM,sBAAsB,GAAG,MAAM,uBAAuB,CAAC,eAAe,EAAE,OAAO,CAAC,CAAC;IAEvF,8CAA8C;IAC9C,IAAI,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,KAAK,MAAM,EAAE,CAAC;QACxC,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,IAAI,MAAM,GAAG,sBAAsB,CAAC;IAC9D,CAAC;SAAM,CAAC;QACN,MAAM,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,sBAAsB,EAAE,CAAC,CAAC;IAC9D,CAAC;IAED,MAAM,eAAe,GAAwB;QAC3C,MAAM;QACN;YACE,YAAY,EAAE,eAAe,EAAE;YAC/B,oBAAoB,EAAE,iBAAiB;YACvC,WAAW,EAAE,OAAO,CAAC,WAAW,IAAI,GAAG;YACvC,SAAS,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC,CAAC,SAAS,CAAC,OAAO;YAC9D,oBAAoB,EAAE;gBACpB,IAAI,EAAE,KAAK;gBACX,YAAY,EAAE,IAAI;gBAClB,KAAK,EAAE,KAAK;aACb;SACF;QACD,OAAO;KACR,CAAC;IAEF,IAAI,CAAC;QACH,MAAM,cAAc,GAAG,CAAC,MAAM,iBAAiB,CAAC,GAAG,eAAe,CAAC,CAAC;aACjE,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,cAAc,CAAC;aAC9C,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;QAEpC,IAAI,sBAAsB,GAAG,cAAc,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,iBAAiB,CAAC,CAAC;QAE5F,IAAI,sBAAsB,EAAE,CAAC;YAC3B,+DAA+D;YAC/D,sBAAsB,GAAG,MAAM,wBAAwB,CACrD,sBAA2D,EAC3D,sBAAsB,EACtB,OAAO,CACR,CAAC;YAEF,gBAAgB,CAAC,4DAA4D,CAAC,CAAC;YAE/E,4CAA4C;YAC5C,MAAM,aAAa,GAAG,MAAM,wBAAwB,CAAC,MAAM,EAAE,sBAAsB,EAAE,OAAO,CAAC,CAAC;YAC9F,IAAI,aAAa,KAAK,UAAU,CAAC,KAAK,EAAE,CAAC;gBACvC,gBAAgB,CAAC,6DAA6D,CAAC,CAAC;gBAChF,OAAO,UAAU,CAAC,KAAK,CAAC;YAC1B,CAAC;YAED,MAAM,oBAAoB,GAAe;gBACvC,IAAI,EAAE,WAAW;gBACjB,aAAa,EAAE,cAAc;aAC9B,CAAC;YAEF,gBAAgB,CACd,uCAAuC,EACvC,sBAAsB,EACtB,SAAS,EACT,SAAS,EACT,oBAAoB,CACrB,CAAC;YAEF,sDAAsD;YACtD,MAAM,CAAC,IAAI,CAAC,oBAAoB,CAAC,CAAC;YAClC,MAAM,CAAC,IAAI,CAAC;gBACV,IAAI,EAAE,MAAM;gBACZ,iBAAiB,EAAE,cAAc,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,OAAO,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC;gBACxF,KAAK,EAAE,IAAI;aACZ,CAAC,CAAC;YAEH,OAAO,UAAU,CAAC,QAAQ,CAAC;QAC7B,CAAC;aAAM,CAAC;YACN,gBAAgB,CAAC,yCAAyC,CAAC,CAAC;YAC5D,OAAO,UAAU,CAAC,KAAK,CAAC;QAC1B,CAAC;IACH,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,gBAAgB,CAAC,+BAA+B,GAAI,KAAe,CAAC,OAAO,CAAC,CAAC;QAC7E,OAAO,UAAU,CAAC,KAAK,CAAC;IAC1B,CAAC;AACH,CAAC;AAED;;;GAGG;AACH,KAAK,UAAU,uBAAuB,CAAC,cAAsB,EAAE,OAAuB;IACpF,IAAI,cAAc,GAAG,cAAc,CAAC;IACpC,MAAM,QAAQ,GAAG,6BAA6B,EAAE,CAAC;IAEjD,IAAI,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACxB,gBAAgB,CAAC,aAAa,QAAQ,CAAC,MAAM,wBAAwB,CAAC,CAAC;QAEvE,KAAK,MAAM,IAAI,IAAI,QAAQ,EAAE,CAAC;YAC5B,IAAI,CAAC;gBACH,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC;oBACxB,MAAM,EAAE,cAAc;oBACtB,OAAO;iBACR,CAAC,CAAC;gBACH,IAAI,MAAM,EAAE,CAAC;oBACX,cAAc,GAAG,MAAM,CAAC;gBAC1B,CAAC;YACH,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACf,gBAAgB,CAAC,+BAAgC,KAAe,CAAC,OAAO,EAAE,CAAC,CAAC;gBAC5E,OAAO,CAAC,KAAK,CAAC,0BAA0B,EAAE,KAAK,CAAC,CAAC;YACnD,CAAC;QACH,CAAC;IACH,CAAC;IAED,OAAO,cAAc,CAAC;AACxB,CAAC;AAED;;;GAGG;AACH,KAAK,UAAU,wBAAwB,CACrC,cAAiD,EACjD,cAAsB,EACtB,OAAuB;IAEvB,IAAI,cAAc,GAAG,cAAc,CAAC;IACpC,MAAM,SAAS,GAAG,8BAA8B,EAAE,CAAC;IAEnD,IAAI,SAAS,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACzB,gBAAgB,CAAC,aAAa,SAAS,CAAC,MAAM,yBAAyB,CAAC,CAAC;QAEzE,KAAK,MAAM,IAAI,IAAI,SAAS,EAAE,CAAC;YAC7B,IAAI,CAAC;gBACH,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC;oBACxB,MAAM,EAAE,cAAc;oBACtB,OAAO;oBACP,MAAM,EAAE,cAAc;iBACvB,CAAC,CAAC;gBACH,IAAI,MAAM,EAAE,CAAC;oBACX,cAAc,GAAG,MAAM,CAAC;gBAC1B,CAAC;YACH,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACf,gBAAgB,CAAC,gCAAiC,KAAe,CAAC,OAAO,EAAE,CAAC,CAAC;gBAC7E,OAAO,CAAC,KAAK,CAAC,2BAA2B,EAAE,KAAK,CAAC,CAAC;YACpD,CAAC;QACH,CAAC;IACH,CAAC;IAED,OAAO,cAAc,CAAC;AACxB,CAAC"}

package/dist/prompt/steps/step-context-compression.d.ts

@@ -1,8 +0,0 @@
-import { GenerateContentFunction, PromptItem } from '../../ai-service/common-types.js';
-import { CodegenOptions } from '../../main/codegen-types.js';
-import { StepResult } from './steps-types.js';
-export declare const CONTEXT_COMPRESSION_PROMPT = "Analyze the conversation history and source code dependencies to create a comprehensive context summary that preserves essential information while maintaining reasonable token efficiency.\n\nKey Principles:\n1. Preserve Rich Context: Maintain detailed information about the conversation, especially for expensive operations like reasoning inference, code analysis, or complex decision-making.\n2. Token Efficiency: Target a 50-80% reduction in tokens while preserving critical information. For example:\n   - Long conversations (>50k tokens): Aim for 75-80% reduction\n   - Medium conversations (10k-50k tokens): Aim for 60-75% reduction\n   - Short conversations (<10k tokens): Aim for 50-60% reduction\n3. File Handling: Do not include file contents in the summary - use filePaths array for this purpose.\n4. Temporal Context: Preserve chronological progression of important decisions and changes.\n\nRequired Information to Preserve:\n\n1. Conversation Flow:\n   **High Priority:**\n   - Initial problem statement and core requirements\n   - Results of expensive operations (reasoning inference, analysis)\n   - Key architectural and design decisions with rationale\n   - Critical constraints or requirements\n   - Major changes in direction or approach\n\n   **Medium Priority:**\n   - Important clarifying questions and answers\n   - User preferences affecting implementation\n   - Significant technical discussions\n   - Error handling requirements\n\n   **Optional:**\n   - General feedback or observations\n   - Minor clarifications\n   - Non-critical issues encountered\n   - Routine confirmations\n\n2. Technical Details:\n   **High Priority:**\n   - Specific code changes proposed or implemented\n   - Critical architectural decisions\n   - Security considerations\n   - Performance requirements\n   - Core dependencies and their relationships\n\n   **Medium Priority:**\n   - Testing requirements\n   - Code organization decisions\n   - Implementation patterns chosen\n   - File structure changes\n\n   **Optional:**\n   - Alternative approaches considered\n   - Code style preferences\n   - Non-critical optimizations\n   - Documentation suggestions\n\n3. Implementation Status:\n   **High Priority:**\n   - Current development stage\n   - Blocking issues or challenges\n   - Critical validation results\n   - Required next steps\n\n   **Medium Priority:**\n   - Completed steps\n   - Pending tasks\n   - Test results\n\n   **Optional:**\n   - Nice-to-have features\n   - Non-blocking improvements\n   - Future considerations\n\nPriority Conflict Resolution:\n1. When multiple items compete for inclusion:\n   - Always preserve items marked as \"High Priority\"\n   - Include \"Medium Priority\" items if they directly relate to \"High Priority\" items\n   - Include \"Optional\" items only if they provide crucial context for \"High Priority\" items\n2. When facing token limits:\n   - First, compress or remove \"Optional\" items\n   - Then, selectively compress \"Medium Priority\" items\n   - Finally, if necessary, compress (but never remove) \"High Priority\" items\n3. When items span multiple categories:\n   - Preserve items that appear in multiple \"High Priority\" sections\n   - Combine related items to reduce redundancy while maintaining context\n\nDeduplication Guidance:\n1. Identify and remove redundant information:\n   Example - Before:\n   \"User asked about error handling. Assistant explained error handling approach. User requested clarification about error handling. Assistant provided more details about error handling.\"\n   After:\n   \"Discussion of error handling approach: Initial explanation followed by clarification of specific details.\"\n\n2. Merge related technical decisions:\n   Example - Before:\n   \"Decided to use async/await. Later discussed error handling with try/catch. Then added discussion about Promise rejection handling.\"\n   After:\n   \"Implemented asynchronous operations using async/await pattern, incorporating comprehensive error handling (try/catch and Promise rejections).\"\n\n3. Combine similar requirements:\n   Example - Before:\n   \"Need to handle network errors. Should retry failed requests. Must implement timeout for requests. Should handle offline mode.\"\n   After:\n   \"Network handling requirements: Error recovery with retries, request timeouts, and offline mode support.\"\n\nFile Path Inclusion Criteria:\n1. Always Include:\n   - Files directly targeted for modification\n   - Files containing code being analyzed or referenced\n   - Critical dependencies of modified files\n   - Configuration files affecting the changes\n\n2. Include Based on Context:\n   - Files containing relevant examples or patterns\n   - Test files for affected components\n   - Related documentation files\n\n3. Do Not Include:\n   - Files only mentioned in passing\n   - Deprecated or unused files\n   - Files from rejected approaches\n   - Files outside the current task scope\n\nHandling Complex Technical Discussions:\n1. For Code Analysis:\n   - Preserve detailed reasoning about algorithmic choices\n   - Keep performance considerations and trade-offs\n   - Maintain security-related discussions\n   - Retain architectural decisions and their rationale\n\n2. For Multi-File Dependencies:\n   - Document relationships between files\n   - Preserve dependency chain reasoning\n   - Keep critical implementation order requirements\n   - Maintain context about shared components\n\n3. For Technical Decisions:\n   - Preserve core decision points and rationale\n   - Keep relevant constraints and requirements\n   - Maintain important trade-off discussions\n   - Retain technical debt considerations\n\nFormat your response as a structured JSON object with:\n- conversationSummary: Detailed summary preserving rich context of the conversation's progression and key decisions\n- filePaths: Array of file paths that are critical for the task (no file contents, just paths)\n\nExample of good summary structure:\n{\n  \"conversationSummary\": \"Started: User requested CONTEXT_COMPRESSION_PROMPT improvement. Analysis: Current compression too aggressive (100k->100 tokens). Key Decision: Allow larger summaries (5k tokens ok). Reasoning inference revealed importance of preserving expensive operation results. Implementation: Updating compression logic in step-context-compression.ts. Requirements: 1) Less aggressive compression, 2) Rich conversation preservation, 3) No file contents in summary.\",\n  \"filePaths\": [\"/path/to/relevant/files\"]\n}\n\nFocus on creating a summary that:\n1. Is comprehensive enough for the AI to understand the full context\n2. Preserves expensive computation results\n3. Maintains chronological flow of decisions\n4. Captures technical details and requirements\n5. Excludes file contents but includes critical file paths";
-/**
- * Executes the context compression step
- */
-export declare function executeStepContextCompression(generateContentFn: GenerateContentFunction, prompt: PromptItem[], options: CodegenOptions): Promise<StepResult>;

package/dist/prompt/steps/step-context-compression.js

@@ -1,231 +0,0 @@
-import { ModelType } from '../../ai-service/common-types.js';
-import { putSystemMessage } from '../../main/common/content-bus.js';
-import { getFunctionDefs } from '../function-calling.js';
-import { StepResult } from './steps-types.js';
-import { executeStepEnsureContext } from './step-ensure-context.js';
-export const CONTEXT_COMPRESSION_PROMPT = `Analyze the conversation history and source code dependencies to create a comprehensive context summary that preserves essential information while maintaining reasonable token efficiency.
-
-Key Principles:
-1. Preserve Rich Context: Maintain detailed information about the conversation, especially for expensive operations like reasoning inference, code analysis, or complex decision-making.
-2. Token Efficiency: Target a 50-80% reduction in tokens while preserving critical information. For example:
-   - Long conversations (>50k tokens): Aim for 75-80% reduction
-   - Medium conversations (10k-50k tokens): Aim for 60-75% reduction
-   - Short conversations (<10k tokens): Aim for 50-60% reduction
-3. File Handling: Do not include file contents in the summary - use filePaths array for this purpose.
-4. Temporal Context: Preserve chronological progression of important decisions and changes.
-
-Required Information to Preserve:
-
-1. Conversation Flow:
-   **High Priority:**
-   - Initial problem statement and core requirements
-   - Results of expensive operations (reasoning inference, analysis)
-   - Key architectural and design decisions with rationale
-   - Critical constraints or requirements
-   - Major changes in direction or approach
-
-   **Medium Priority:**
-   - Important clarifying questions and answers
-   - User preferences affecting implementation
-   - Significant technical discussions
-   - Error handling requirements
-
-   **Optional:**
-   - General feedback or observations
-   - Minor clarifications
-   - Non-critical issues encountered
-   - Routine confirmations
-
-2. Technical Details:
-   **High Priority:**
-   - Specific code changes proposed or implemented
-   - Critical architectural decisions
-   - Security considerations
-   - Performance requirements
-   - Core dependencies and their relationships
-
-   **Medium Priority:**
-   - Testing requirements
-   - Code organization decisions
-   - Implementation patterns chosen
-   - File structure changes
-
-   **Optional:**
-   - Alternative approaches considered
-   - Code style preferences
-   - Non-critical optimizations
-   - Documentation suggestions
-
-3. Implementation Status:
-   **High Priority:**
-   - Current development stage
-   - Blocking issues or challenges
-   - Critical validation results
-   - Required next steps
-
-   **Medium Priority:**
-   - Completed steps
-   - Pending tasks
-   - Test results
-
-   **Optional:**
-   - Nice-to-have features
-   - Non-blocking improvements
-   - Future considerations
-
-Priority Conflict Resolution:
-1. When multiple items compete for inclusion:
-   - Always preserve items marked as "High Priority"
-   - Include "Medium Priority" items if they directly relate to "High Priority" items
-   - Include "Optional" items only if they provide crucial context for "High Priority" items
-2. When facing token limits:
-   - First, compress or remove "Optional" items
-   - Then, selectively compress "Medium Priority" items
-   - Finally, if necessary, compress (but never remove) "High Priority" items
-3. When items span multiple categories:
-   - Preserve items that appear in multiple "High Priority" sections
-   - Combine related items to reduce redundancy while maintaining context
-
-Deduplication Guidance:
-1. Identify and remove redundant information:
-   Example - Before:
-   "User asked about error handling. Assistant explained error handling approach. User requested clarification about error handling. Assistant provided more details about error handling."
-   After:
-   "Discussion of error handling approach: Initial explanation followed by clarification of specific details."
-
-2. Merge related technical decisions:
-   Example - Before:
-   "Decided to use async/await. Later discussed error handling with try/catch. Then added discussion about Promise rejection handling."
-   After:
-   "Implemented asynchronous operations using async/await pattern, incorporating comprehensive error handling (try/catch and Promise rejections)."
-
-3. Combine similar requirements:
-   Example - Before:
-   "Need to handle network errors. Should retry failed requests. Must implement timeout for requests. Should handle offline mode."
-   After:
-   "Network handling requirements: Error recovery with retries, request timeouts, and offline mode support."
-
-File Path Inclusion Criteria:
-1. Always Include:
-   - Files directly targeted for modification
-   - Files containing code being analyzed or referenced
-   - Critical dependencies of modified files
-   - Configuration files affecting the changes
-
-2. Include Based on Context:
-   - Files containing relevant examples or patterns
-   - Test files for affected components
-   - Related documentation files
-
-3. Do Not Include:
-   - Files only mentioned in passing
-   - Deprecated or unused files
-   - Files from rejected approaches
-   - Files outside the current task scope
-
-Handling Complex Technical Discussions:
-1. For Code Analysis:
-   - Preserve detailed reasoning about algorithmic choices
-   - Keep performance considerations and trade-offs
-   - Maintain security-related discussions
-   - Retain architectural decisions and their rationale
-
-2. For Multi-File Dependencies:
-   - Document relationships between files
-   - Preserve dependency chain reasoning
-   - Keep critical implementation order requirements
-   - Maintain context about shared components
-
-3. For Technical Decisions:
-   - Preserve core decision points and rationale
-   - Keep relevant constraints and requirements
-   - Maintain important trade-off discussions
-   - Retain technical debt considerations
-
-Format your response as a structured JSON object with:
-- conversationSummary: Detailed summary preserving rich context of the conversation's progression and key decisions
-- filePaths: Array of file paths that are critical for the task (no file contents, just paths)
-
-Example of good summary structure:
-{
-  "conversationSummary": "Started: User requested CONTEXT_COMPRESSION_PROMPT improvement. Analysis: Current compression too aggressive (100k->100 tokens). Key Decision: Allow larger summaries (5k tokens ok). Reasoning inference revealed importance of preserving expensive operation results. Implementation: Updating compression logic in step-context-compression.ts. Requirements: 1) Less aggressive compression, 2) Rich conversation preservation, 3) No file contents in summary.",
-  "filePaths": ["/path/to/relevant/files"]
-}
-
-Focus on creating a summary that:
-1. Is comprehensive enough for the AI to understand the full context
-2. Preserves expensive computation results
-3. Maintains chronological flow of decisions
-4. Captures technical details and requirements
-5. Excludes file contents but includes critical file paths`;
-/**
- * Executes the context compression step
- */
-export async function executeStepContextCompression(generateContentFn, prompt, options) {
-    const initialPromptIndex = prompt.findIndex((item) => item.itemId === 'INITIAL_PROMPT');
-    if (initialPromptIndex === -1) {
-        putSystemMessage('Could not find initial prompt, something is wrong.');
-        return StepResult.CONTINUE;
-    }
-    try {
-        putSystemMessage('Context compression is starting...');
-        const compressContextCall = await compressConversationHistory(generateContentFn, prompt.slice(initialPromptIndex, prompt.length), options);
-        if (!compressContextCall) {
-            putSystemMessage('Context compression did not return a result');
-            return StepResult.BREAK;
-        }
-        if (!compressContextCall.args) {
-            putSystemMessage('Context compression returned invalid result (missing args)');
-            return StepResult.BREAK;
-        }
-        // Replace the initial prompt with the context compression call response
-        prompt.splice(initialPromptIndex, prompt.length - initialPromptIndex);
-        // Add compression result to prompt
-        prompt.push({
-            type: 'user',
-            itemId: 'INITIAL_PROMPT',
-            text: 'This is summary of our conversation:\n\n' + compressContextCall.args.conversationSummary,
-        });
-        // Ensure context
-        await executeStepEnsureContext(prompt, compressContextCall, options);
-        putSystemMessage('Context compression completed successfully.', compressContextCall.args);
-        return StepResult.CONTINUE;
-    }
-    catch (error) {
-        putSystemMessage('An unexpected error occurred during context compression', { error });
-        console.error('Context compression error details:', error);
-        return StepResult.BREAK;
-    }
-}
-/**
- * Compresses the conversation history using the AI model
- */
-async function compressConversationHistory(generateContentFn, prompt, options) {
-    const summaryPrompt = [
-        {
-            type: 'systemPrompt',
-            systemPrompt: CONTEXT_COMPRESSION_PROMPT,
-        },
-        ...prompt,
-    ];
-    const request = [
-        summaryPrompt,
-        {
-            functionDefs: getFunctionDefs(),
-            requiredFunctionName: 'compressContext',
-            temperature: 0.3, // Use a lower temperature for more focused summaries
-            modelType: ModelType.CHEAP,
-            expectedResponseType: {
-                text: false,
-                functionCall: true,
-                media: false,
-            },
-        },
-        options,
-    ];
-    const result = (await generateContentFn(...request))
-        .filter((item) => item.type === 'functionCall')
-        .map((item) => item.functionCall);
-    return result[0];
-}
-//# sourceMappingURL=step-context-compression.js.map

package/dist/prompt/steps/step-context-compression.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"step-context-compression.js","sourceRoot":"","sources":["../../../src/prompt/steps/step-context-compression.ts"],"names":[],"mappings":"AAAA,OAAO,EAA4D,SAAS,EAAE,MAAM,kCAAkC,CAAC;AAEvH,OAAO,EAAE,gBAAgB,EAAE,MAAM,kCAAkC,CAAC;AACpE,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAE9C,OAAO,EAAE,wBAAwB,EAAE,MAAM,0BAA0B,CAAC;AAEpE,MAAM,CAAC,MAAM,0BAA0B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2DA0JiB,CAAC;AAE5D;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,6BAA6B,CACjD,iBAA0C,EAC1C,MAAoB,EACpB,OAAuB;IAEvB,MAAM,kBAAkB,GAAG,MAAM,CAAC,SAAS,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,gBAAgB,CAAC,CAAC;IACxF,IAAI,kBAAkB,KAAK,CAAC,CAAC,EAAE,CAAC;QAC9B,gBAAgB,CAAC,oDAAoD,CAAC,CAAC;QACvE,OAAO,UAAU,CAAC,QAAQ,CAAC;IAC7B,CAAC;IAED,IAAI,CAAC;QACH,gBAAgB,CAAC,oCAAoC,CAAC,CAAC;QACvD,MAAM,mBAAmB,GAAG,MAAM,2BAA2B,CAC3D,iBAAiB,EACjB,MAAM,CAAC,KAAK,CAAC,kBAAkB,EAAE,MAAM,CAAC,MAAM,CAAC,EAC/C,OAAO,CACR,CAAC;QAEF,IAAI,CAAC,mBAAmB,EAAE,CAAC;YACzB,gBAAgB,CAAC,6CAA6C,CAAC,CAAC;YAChE,OAAO,UAAU,CAAC,KAAK,CAAC;QAC1B,CAAC;QAED,IAAI,CAAC,mBAAmB,CAAC,IAAI,EAAE,CAAC;YAC9B,gBAAgB,CAAC,4DAA4D,CAAC,CAAC;YAC/E,OAAO,UAAU,CAAC,KAAK,CAAC;QAC1B,CAAC;QAED,wEAAwE;QACxE,MAAM,CAAC,MAAM,CAAC,kBAAkB,EAAE,MAAM,CAAC,MAAM,GAAG,kBAAkB,CAAC,CAAC;QAEtE,mCAAmC;QACnC,MAAM,CAAC,IAAI,CAAC;YACV,IAAI,EAAE,MAAM;YACZ,MAAM,EAAE,gBAAgB;YACxB,IAAI,EAAE,0CAA0C,GAAG,mBAAmB,CAAC,IAAI,CAAC,mBAAmB;SAChG,CAAC,CAAC;QAEH,iBAAiB;QACjB,MAAM,wBAAwB,CAAC,MAAM,EAAE,mBAAmB,EAAE,OAAO,CAAC,CAAC;QAErE,gBAAgB,CAAC,6CAA6C,EAAE,mBAAmB,CAAC,IAAI,CAAC,CAAC;QAE1F,OAAO,UAAU,CAAC,QAAQ,CAAC;IAC7B,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,gBAAgB,CAAC,yDAAyD,EAAE,EAAE,KAAK,EAAE,CAAC,CAAC;QACvF,OAAO,CAAC,KAAK,CAAC,oCAAoC,EAAE,KAAK,CAAC,CAAC;QAC3D,OAAO,UAAU,CAAC,KAAK,CAAC;IAC1B,CAAC;AACH,CAAC;AAED;;GAEG;AACH,KAAK,UAAU,2BAA2B,CACxC,iBAA0C,EAC1C,MAAoB,EACpB,OAAuB;IAEvB,MAAM,aAAa,GAAiB;QAClC;YACE,IAAI,EAAE,cAAc;YACpB,YAAY,EAAE,0BAA0B;SACzC;QACD,GAAG,MAAM;KACV,CAAC;IAEF,MAAM,OAAO,GAAwB;QACnC,aAAa;QACb;YACE,YAAY,EAAE,eAAe,EAAE;YAC/B,oBAAoB,EAAE,iBAAiB;YACvC,WAAW,EAAE,GAAG,EAAE,qDAAqD;YACvE,SAAS,EAAE,SAAS,CAAC,KAAK;YAC1B,oBAAoB,EAAE;gBACpB,IAAI,EAAE,KAAK;gBACX,YAAY,EAAE,IAAI;gBAClB,KAAK,EAAE,KAAK;aACb;SACF;QACD,OAAO;KACR,CAAC;IAEF,MAAM,MAAM,GAAG,CAAC,MAAM,iBAAiB,CAAC,GAAG,OAAO,CAAC,CAAC;SACjD,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,cAAc,CAAC;SAC9C,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,YAAY,CAA6B,CAAC;IAChE,OAAO,MAAM,CAAC,CAAC,CAAC,CAAC;AACnB,CAAC"}

package/dist/prompt/steps/step-context-optimization.d.ts

@@ -1,8 +0,0 @@
-import { GenerateContentFunction } from '../../ai-service/common-types.js';
-import { PromptItem } from '../../ai-service/common-types.js';
-import { CodegenOptions } from '../../main/codegen-types.js';
-import { StepResult } from './steps-types.js';
-export declare const OPTIMIZATION_PROMPT = "You need to analyze the provided source code files and determine their relevance to the user's prompt. You will then call the `optimizeContext` function with the results.\n\n**Crucially, only include files in the `optimizedContext` array of the `optimizeContext` function call if their calculated relevance score is 0.5 or greater.**\n\nHere are the detailed steps:\n\n1. **Relevance Assessment (Scores from 0.0 to 1.0):**\n   - Evaluate the relevance of each file to the user's prompt based on the following scale:\n     - 0.0 \u2013 0.3: Not Relevant\n     - 0.3 \u2013 0.7: Somewhat Relevant\n     - 0.7 \u2013 0.9: Moderately Relevant\n     - 0.9 \u2013 1.0: Highly Relevant\n   - Consider:\n     - Directly implements the core logic required to address the prompt's features.\n     - Role in dependency chains of relevant files.\n     - Keyword matches with the prompt.\n     - Importance as a dependency.\n\n2. **Dependency Consideration:**\n   - Understand how files depend on each other.\n   - Prioritize files that are directly relevant or are dependencies of highly relevant files.\n   - When evaluating a file, consider its position within dependency chains, but **do not include a file in the `optimizedContext` if its individual relevance score is below 0.5, even if it's part of a dependency chain of a relevant file.**\n\n3. **Token Awareness:**\n   - Be mindful of token usage, but **relevance (specifically a score of 0.5 or higher) is the primary criterion for inclusion in `optimizedContext`.**\n\n4. **Function Call - `optimizeContext`:**\n   - Call the `optimizeContext` function with the following arguments:\n     - `\"userPrompt\"`: The original user prompt.\n     - `\"reasoning\"`: A detailed, step-by-step explanation of the thought process used to determine the optimized context.\n     - `\"optimizedContext\"`: **An array containing ONLY files with a relevance score of 0.5 or higher.** Each object in the array should have:\n       - `\"reasoning\"`:  Specific reasoning for why *this particular file* is relevant and has a score of 0.5 or higher.\n       - `\"filePath\"`: Absolute file path.\n       - `\"relevance\"`: The calculated relevance score (0.5 to 1.0).\n\n**Important Guidelines:**\n\n- **Strict Filtering:** **Only files with a relevance score of 0.5 or more should be included in the `optimizedContext` array.**\n- **No Guessing:** Only use files provided in the `getSourceCode` response.\n- **Evaluate Individually and in Chains:** Consider both individual relevance and dependencies, but the 0.5 threshold is paramount for inclusion.\n- **Proper JSON:** Ensure the `optimizeContext` call is valid JSON.\n- **Full Paths:** Use absolute file paths.\n- **Focus on 0.5+:** The `optimizedContext` array should be exclusively populated with files meeting the relevance criteria.\n- **Handling Codebase-Wide Operations:**\n    - If the user prompt indicates a codebase-wide operation, choose one of the following `optimizeContext` strategies:\n        - **Empty Context:** For operations applying to all files simultaneously, call `optimizeContext` with an empty `optimizedContext` and explain in the `reasoning`.\n        - **Main Entry Points:** For operations starting with key files, identify main entry points and call `optimizeContext` with these files (relevance=1.0), explaining in the `reasoning`.\n- **Data Flow Consideration**: Consider the entire lifecycle of the data involved in the user's request, from the user interface to the database and back. Include files involved in handling, storing, and transmitting this data.\n- **Intent and Contribution Analysis:**  For each file, evaluate its purpose and how it contributes to fulfilling the user's prompt. Consider the flow of logic and data. Which files are essential for the requested outcome, not just tangentially related?\n- **Functional Web Analysis:**  Think of the codebase as a web of interconnected functionalities. Identify the key functional areas involved in the user's prompt and trace the connections between files within these areas.\n- **Core Responsibility Assessment:**  Identify the files that are primarily responsible for managing the lifecycle, data, or logic of the entities involved in the `userPrompt`. These files are likely to be highly relevant.\n- **Data Flow Mapping:**  Trace the flow of data related to the user's request. Identify the files involved in creating, storing, transforming, and retrieving this data.\n\nNow, analyze the source code and call the `optimizeContext` function accordingly.";
-export declare const OPTIMIZATION_TRIGGER_PROMPT = "Thank you for describing the task, I have noticed you have provided a very large context for your question. The amount of source code is very big in particular. Can we do something about it?";
-export declare const CONTEXT_OPTIMIZATION_TEMPERATURE = 0.2;
-export declare function executeStepContextOptimization(generateContentFn: GenerateContentFunction, prompt: PromptItem[], options: CodegenOptions): Promise<StepResult>;