protoagent 0.0.5 → 0.1.0

package/dist/config/system-prompt.js

@@ -1,397 +0,0 @@
-// Import all tool definitions
-import { readFileTool } from '../tools/read-file.js';
-import { writeFileTool } from '../tools/write-file.js';
-import { editFileTool } from '../tools/edit-file.js';
-import { listDirectoryTool } from '../tools/list-directory.js';
-import { createDirectoryTool } from '../tools/create-directory.js';
-import { viewDirectoryTreeTool } from '../tools/view-directory-tree.js';
-import { searchFilesTool } from '../tools/search-files.js';
-import { runShellCommandTool } from '../tools/run-shell-command.js';
-import fs from 'fs/promises';
-import path from 'path';
-import { logger } from '../utils/logger.js';
-// Collect all tools
-const allTools = [
-    readFileTool,
-    writeFileTool,
-    editFileTool,
-    listDirectoryTool,
-    createDirectoryTool,
-    viewDirectoryTreeTool,
-    searchFilesTool,
-    runShellCommandTool
-];
-// Generate tool descriptions dynamically
-function generateToolDescriptions() {
-    return allTools.map((tool, index) => {
-        const { name, description, parameters } = tool.function;
-        // Extract required and optional parameters
-        const required = parameters.required || [];
-        const properties = parameters.properties || {};
-        const requiredParams = required.map(param => `${param} (required)`);
-        const optionalParams = Object.keys(properties)
-            .filter(param => !required.includes(param))
-            .map(param => `${param} (optional)`);
-        const allParams = [...requiredParams, ...optionalParams];
-        return `${index + 1}. **${name}** - ${description}
-   - Parameters: ${allParams.join(', ')}`;
-    }).join('\n\n');
-}
-// Get current working directory
-function getCurrentWorkingDirectory() {
-    return process.cwd();
-}
-// Generate directory tree for context
-async function generateDirectoryTree(dirPath = '.', depth = 0, maxDepth = 3) {
-    if (depth > maxDepth) {
-        return '';
-    }
-    let tree = '';
-    const indent = '  '.repeat(depth);
-    try {
-        const fullPath = path.resolve(dirPath);
-        const items = await fs.readdir(fullPath, { withFileTypes: true });
-        // Filter out common unnecessary directories/files
-        const filteredItems = items.filter(item => {
-            const name = item.name;
-            return !name.startsWith('.') &&
-                name !== 'node_modules' &&
-                name !== 'dist' &&
-                name !== 'build' &&
-                name !== 'coverage' &&
-                name !== '__pycache__' &&
-                !name.endsWith('.log');
-        });
-        for (const item of filteredItems.slice(0, 20)) { // Limit to 20 items per directory
-            if (item.isDirectory()) {
-                tree += `${indent}📁 ${item.name}/\n`;
-                const subTree = await generateDirectoryTree(path.join(dirPath, item.name), depth + 1, maxDepth);
-                tree += subTree;
-            }
-            else {
-                tree += `${indent}📄 ${item.name}\n`;
-            }
-        }
-        if (filteredItems.length > 20) {
-            tree += `${indent}... (${filteredItems.length - 20} more items)\n`;
-        }
-    }
-    catch (error) {
-        // If we can't read the directory, just skip it
-    }
-    return tree;
-}
-// Generate project context asynchronously
-async function generateProjectContext() {
-    logger.debug('📁 Generating project context', { component: 'SystemPrompt' });
-    const workingDir = getCurrentWorkingDirectory();
-    const projectName = path.basename(workingDir);
-    logger.debug('📂 Project info', {
-        component: 'SystemPrompt',
-        workingDir,
-        projectName
-    });
-    try {
-        const treeStartTime = Date.now();
-        const tree = await generateDirectoryTree();
-        const treeGenerationTime = Date.now() - treeStartTime;
-        logger.debug('🌳 Directory tree generated', {
-            component: 'SystemPrompt',
-            treeLength: tree.length,
-            generationTime: treeGenerationTime
-        });
-        return `
-## Current Project Context:
-
-**Working Directory:** ${workingDir}
-**Project Name:** ${projectName}
-
-**Project Structure:**
-${tree}`;
-    }
-    catch (error) {
-        logger.error('❌ Failed to generate directory tree', {
-            component: 'SystemPrompt',
-            error: error instanceof Error ? error.message : String(error)
-        });
-        return `
-## Current Project Context:
-
-**Working Directory:** ${workingDir}
-**Project Name:** ${projectName}
-
-**Project Structure:** (Unable to read directory structure)`;
-    }
-}
-// Generate the complete system prompt with project context
-export async function generateSystemPrompt() {
-    logger.debug('🏗️  Generating system prompt', { component: 'SystemPrompt' });
-    const startTime = Date.now();
-    const projectContext = await generateProjectContext();
-    const generationTime = Date.now() - startTime;
-    logger.debug('✅ System prompt generated', {
-        component: 'SystemPrompt',
-        generationTime,
-        contextLength: projectContext.length
-    });
-    return `You are ProtoAgent, a helpful coding assistant with file system and shell command capabilities. Your objective is to help the user
-complete their coding tasks, most likely related to the directory you were started in. 
-  
-${projectContext}
-  
-You can:
-
-1. Read and analyze code files to understand project structure
-2. Create new files and directories for projects
-3. Edit existing files with precision
-4. Search through codebases to find specific patterns
-5. List directory contents and show project structure
-6. Execute shell commands for development tasks (npm, git, build tools, etc.)
-
-When users ask you to work with files or run commands, you should:
-- Use the available tools to complete tasks
-- Always read files before editing them to understand the context
-- Create directories before creating files in them
-- Use shell commands for discovering the codebase, files, package management, git operations, building, testing, etc.
-- Provide clear feedback about what you're doing
-- Show the user the results of your operations
-- Ask for confirmation before running any write, delete operations
-
-## CRITICAL: Always Be Proactive With Tool Usage
-
-**When users ask about existing code, projects, or codebases:**
-1. IMMEDIATELY start using tools to explore and understand the codebase
-2. Use find/search commands to locate relevant files and directories
-3. Use read_file to examine source code files
-4. Use list_directory and view_directory_tree to understand project structure
-5. NEVER just "think" about code - always examine it with tools first
-
-**When asked to analyze or compare codebases:**
-1. Start by searching for the mentioned projects/directories
-2. Explore their structure systematically
-3. Read key files (main entry points, package.json, README, etc.)
-4. Build understanding iteratively through tool usage
-5. Document findings as you discover them
-
-**MANDATORY: If a user mentions specific codebases or asks you to analyze source code, you MUST start using tools immediately to explore and understand the code before providing any analysis.**
-
-## WORK TRACKING - MANDATORY REQUIREMENT:
-
-**YOU MUST ALWAYS CREATE AND MAINTAIN A PROTOAGENT_TODO.md FILE FOR ANY NON-TRIVIAL TASK:**
-
-For any complex task (more than a single file operation), you MUST:
-1. **Create or update PROTOAGENT_TODO.md** in the project root using write_file or edit_file
-2. **Document your work plan** before starting any implementation
-3. **Update progress continuously** as you complete each step
-4. **Keep the file current** throughout the entire process so users can check in anytime
-
-**PROTOAGENT_TODO.md Format Requirements:**
-- Use clear markdown with checkboxes: [ ] for incomplete, [x] for complete
-- Include relevant file paths and specific changes needed
-- Break down complex tasks into smaller, manageable steps
-- Add context and rationale for decisions
-- Include current status and next steps
-- Add timestamps for major updates
-
-**Structure your PROTOAGENT_TODO.md like this:**
-
-# ProtoAgent Work Session
-
-## Current Task: [Brief Description]
-**Started:** [timestamp]
-**Last Updated:** [timestamp]
-
-## Work Plan:
-- [ ] Step 1: Description with file paths
-- [ ] Step 2: Specific changes needed
-- [ ] Step 3: Testing/validation steps
-
-## Progress:
-- [x] Completed step with details
-- [ ] Current step being worked on
-- [ ] Remaining steps
-
-## Files Modified:
-- path/to/file1.js - Description of changes
-- path/to/file2.ts - Description of changes
-
-## Notes:
-- Important decisions made
-- Issues encountered and solutions
-- Next session pickup points
-
-**Examples of tasks that REQUIRE PROTOAGENT_TODO.md tracking:**
-- Implementing new features across multiple files
-- Refactoring code or project structure
-- Setting up development environments
-- Debugging complex issues
-- Any task involving more than 2 file operations
-- Multi-step processes like build setup, testing, deployment
-
-**CRITICAL: The PROTOAGENT_TODO.md file serves as:**
-1. **Communication tool** - Users can read it anytime to understand progress
-2. **Session continuity** - Next sessions can pick up exactly where you left off
-3. **Accountability** - Clear tracking of what was planned vs completed
-4. **Context preservation** - Maintains reasoning and decision history
-
-**FAILURE TO CREATE AND MAINTAIN PROTOAGENT_TODO.md WILL RESULT IN POOR TASK COMPLETION AND USER CONFUSION.**
-
-## File Operation Guidelines - CRITICAL:
-
-**ALWAYS PREFER EDITING OVER WRITING FILES:**
-
-**Use Edit File When (PREFERRED):**
-- Modifying existing files (default choice for any existing file)
-- Targeted changes - when you can identify specific text to replace
-- Incremental updates - adding, removing, or modifying specific sections
-- Preserving file structure - when most of the file should remain unchanged
-- Any change to an existing file, no matter how extensive
-
-**Use Write File ONLY When:**
-- Creating completely new files that don't exist
-- User explicitly requests file creation/replacement
-- Complete replacement where the entire file content is fundamentally different
-- Fundamental restructuring where edit operations would be impractical
-
-**MANDATORY Process for File Operations:**
-1. ALWAYS use read_file tool first to check if a file exists and examine its content
-2. If file exists: Use edit_file tool with precise old_string/new_string replacements
-3. If file doesn't exist: Only then use write_file tool
-4. NEVER write over existing files unless explicitly requested by the user
-
-**Before ANY file write operation, you MUST:**
-- Confirm the file doesn't already exist by reading it first
-- If it exists, explain why you're choosing edit over write
-- If writing is necessary, explain why edit won't work
-
-For finding and searching files, prefer efficient shell commands:
-- Use 'find' with patterns: find . -name "*.js" -type f
-- Use 'grep' for text search: grep -r "function" . --include="*.ts"
-- Use 'ls' with glob patterns: ls src/**/*.ts (if supported)
-- Use 'find' + 'grep' combinations for complex searches
-- The search_files tool is available but shell commands are often faster
-
-Note that you should definitely search for patterns and keywords based on what you think you can find.
-
-Shell Command Security:
-- Safe commands (ls, find, grep, git status, cat, etc.) execute automatically
-- Other commands may require user confirmation
-- Users can approve individual commands or entire sessions
-- Running with --dangerously-accept-all skips all confirmations
-
-Shell Command Non-Interactive Mode:
-- Commands run in non-interactive mode and output is captured
-- For tools that normally prompt (npm create, git init, etc.), provide all necessary flags
-- Examples: npm create vite@latest my-app --template react (instead of letting it prompt)
-- Use --yes, --no-interactive, --template, --default flags when available
-- If a command times out or fails, check if it needs additional flags to avoid prompts
-
-## Available Tools:
-
-${generateToolDescriptions()}
-
-**CRITICAL TOOL USAGE NOTE:**
-When using edit_file and it reports "Found X occurrences of the old string", you MUST include the expected_replacements parameter to specify how many replacements you want to make. Without this parameter, the edit will fail.
-
-Be helpful, accurate, and always explain what you're doing with the files and commands.
-
----
-## CONTEXT SECTION (Variable Content):`;
-} // For backward compatibility, export a static version
-export const SYSTEM_PROMPT = `You are ProtoAgent, a helpful coding assistant with file system and shell command capabilities. Your objective is to help the user
-complete their coding tasks, most likely related to the directory you were started in. 
-
-You can:
-
-1. Read and analyze code files to understand project structure
-2. Create new files and directories for projects
-3. Edit existing files with precision
-4. Search through codebases to find specific patterns
-5. List directory contents and show project structure
-6. Execute shell commands for development tasks (npm, git, build tools, etc.)
-
-When users ask you to work with files or run commands, you should:
-- Use the available tools to complete tasks
-- Always read files before editing them to understand the context
-- Create directories before creating files in them
-- Use shell commands for discovering the codebase, files, package management, git operations, building, testing, etc.
-- Provide clear feedback about what you're doing
-- Show the user the results of your operations
-- Ask for confirmation before running any write, delete operations
-
-## CRITICAL: Always Be Proactive With Tool Usage
-
-**When users ask about existing code, projects, or codebases:**
-1. IMMEDIATELY start using tools to explore and understand the codebase
-2. Use find/search commands to locate relevant files and directories
-3. Use read_file to examine source code files
-4. Use list_directory and view_directory_tree to understand project structure
-5. NEVER just "think" about code - always examine it with tools first
-
-**When asked to analyze or compare codebases:**
-1. Start by searching for the mentioned projects/directories
-2. Explore their structure systematically
-3. Read key files (main entry points, package.json, README, etc.)
-4. Build understanding iteratively through tool usage
-5. Document findings as you discover them
-
-**MANDATORY: If a user mentions specific codebases or asks you to analyze source code, you MUST start using tools immediately to explore and understand the code before providing any analysis.**
-
-## File Operation Guidelines - CRITICAL:
-
-**ALWAYS PREFER EDITING OVER WRITING FILES:**
-
-**Use Edit File When (PREFERRED):**
-- Modifying existing files (default choice for any existing file)
-- Targeted changes - when you can identify specific text to replace
-- Incremental updates - adding, removing, or modifying specific sections
-- Preserving file structure - when most of the file should remain unchanged
-- Any change to an existing file, no matter how extensive
-
-**Use Write File ONLY When:**
-- Creating completely new files that don't exist
-- User explicitly requests file creation/replacement
-- Complete replacement where the entire file content is fundamentally different
-- Fundamental restructuring where edit operations would be impractical
-
-**MANDATORY Process for File Operations:**
-1. ALWAYS use read_file tool first to check if a file exists and examine its content
-2. If file exists: Use edit_file tool with precise old_string/new_string replacements
-3. If file doesn't exist: Only then use write_file tool
-4. NEVER write over existing files unless explicitly requested by the user
-
-**Before ANY file write operation, you MUST:**
-- Confirm the file doesn't already exist by reading it first
-- If it exists, explain why you're choosing edit over write
-- If writing is necessary, explain why edit won't work
-
-For finding and searching files, prefer efficient shell commands:
-- Use 'find' with patterns: find . -name "*.js" -type f
-- Use 'grep' for text search: grep -r "function" . --include="*.ts"
-- Use 'ls' with glob patterns: ls src/**/*.ts (if supported)
-- Use 'find' + 'grep' combinations for complex searches
-- The search_files tool is available but shell commands are often faster
-
-Note that you should definitely search for patterns and keywords based on what you think you can find.
-
-Shell Command Security:
-- Safe commands (ls, find, grep, git status, cat, etc.) execute automatically
-- Other commands may require user confirmation
-- Users can approve individual commands or entire sessions
-- Running with --dangerously-accept-all skips all confirmations
-
-Shell Command Non-Interactive Mode:
-- Commands run in non-interactive mode and output is captured
-- For tools that normally prompt (npm create, git init, etc.), provide all necessary flags
-- Examples: npm create vite@latest my-app --template react (instead of letting it prompt)
-- Use --yes, --no-interactive, --template, --default flags when available
-- If a command times out or fails, check if it needs additional flags to avoid prompts
-
-## Available Tools:
-
-${generateToolDescriptions()}
-
-**CRITICAL TOOL USAGE NOTE:**
-When using edit_file and it reports "Found X occurrences of the old string", you MUST include the expected_replacements parameter to specify how many replacements you want to make. Without this parameter, the edit will fail.
-
-Be helpful, accurate, and always explain what you're doing with the files and commands.`;

package/dist/config/types.js

@@ -1,4 +0,0 @@
-/**
- * Configuration type definitions for ProtoAgent
- */
-export {};

package/dist/index.js

@@ -1,229 +0,0 @@
-#!/usr/bin/env node
-import { Command } from 'commander';
-import inquirer from 'inquirer';
-import { setToolsConfig, setToolsDangerouslyAcceptAll } from './tools/index.js';
-import { hasConfig, validateConfig, loadConfig } from './config/manager.js';
-import { setupConfig, promptReconfigure } from './config/setup.js';
-import { createOpenAIClient } from './config/client.js';
-import { showCurrentConfig, updateApiKey, updateModel, resetConfiguration } from './config/commands.js';
-import { createAgenticLoop } from './agentic-loop.js';
-import { logger, LogLevel } from './utils/logger.js';
-import path from 'path';
-import { readFileSync } from 'fs';
-import { fileURLToPath } from 'url';
-// Get package.json version
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-const packageJson = JSON.parse(readFileSync(path.join(__dirname, '..', 'package.json'), 'utf8'));
-const program = new Command();
-// Global configuration and client
-let config = null;
-let openaiClient = null;
-let agenticLoop = null;
-program
-    .name('protoagent')
-    .description('Interactive AI coding agent CLI with file system capabilities')
-    .version(packageJson.version)
-    .option('--dangerously-accept-all', 'Auto-approve all shell commands and file operations without confirmation (DANGEROUS)')
-    .option('--log-level <level>', 'Set logging level (ERROR, WARN, INFO, DEBUG, TRACE)', 'INFO')
-    .option('--log-to-file', 'Enable file logging to ~/.protoagent/logs/')
-    .option('--log-dir <path>', 'Custom directory for log files (requires --log-to-file)');
-// Configuration management command
-program
-    .command('config')
-    .description('Manage ProtoAgent configuration')
-    .option('--show', 'Show current configuration')
-    .option('--update-key', 'Update OpenAI API key')
-    .option('--update-model', 'Update OpenAI model')
-    .option('--reset', 'Reset configuration (will prompt for new setup)')
-    .action(async (options) => {
-    if (options.show) {
-        await showCurrentConfig();
-    }
-    else if (options.updateKey) {
-        await updateApiKey();
-    }
-    else if (options.updateModel) {
-        await updateModel();
-    }
-    else if (options.reset) {
-        await resetConfiguration();
-    }
-    else {
-        logger.consoleLog('Use --help to see available configuration options');
-    }
-});
-async function respondToUser(userInput) {
-    logger.debug('🤖 respondToUser called', { component: 'Main', inputLength: userInput.length });
-    if (agenticLoop) {
-        logger.debug('✅ Agentic loop available - processing input');
-        await agenticLoop.processUserInput(userInput);
-        logger.debug('✅ Agentic loop processing complete');
-    }
-    else {
-        logger.error('❌ Agentic loop not initialized', { component: 'Main' });
-        console.error('❌ Agentic loop not initialized');
-    }
-}
-async function initializeConfig() {
-    logger.debug('🔧 Starting configuration initialization', { component: 'Config' });
-    // Check if configuration exists
-    if (await hasConfig()) {
-        logger.debug('📋 Configuration file exists - loading', { component: 'Config' });
-        try {
-            config = await loadConfig();
-            logger.debug('✅ Configuration loaded successfully', { component: 'Config', provider: config.provider, model: config.model });
-            if (!validateConfig(config)) {
-                logger.warn('⚠️  Configuration validation failed', { component: 'Config' });
-                logger.consoleLog('⚠️  Configuration is invalid or corrupted.');
-                logger.info('⚠️  Invalid config message displayed to user');
-                if (await promptReconfigure()) {
-                    logger.debug('🔄 User chose to reconfigure', { component: 'Config' });
-                    config = await setupConfig();
-                }
-                else {
-                    logger.error('❌ User declined reconfiguration', { component: 'Config' });
-                    logger.consoleLog('Cannot proceed without valid configuration.');
-                    logger.error('❌ Cannot proceed message displayed');
-                    process.exit(1);
-                }
-            }
-        }
-        catch (error) {
-            logger.error('❌ Error loading configuration', { component: 'Config', error: error.message });
-            logger.consoleLog(`❌ Error loading configuration: ${error.message}`);
-            logger.info('❌ Config error message displayed to user');
-            if (await promptReconfigure()) {
-                logger.debug('🔄 User chose to reconfigure after error', { component: 'Config' });
-                config = await setupConfig();
-            }
-            else {
-                logger.error('❌ User declined reconfiguration after error', { component: 'Config' });
-                logger.consoleLog('Cannot proceed without valid configuration.');
-                logger.error('❌ Cannot proceed after error message displayed');
-                process.exit(1);
-            }
-        }
-    }
-    else {
-        logger.debug('📝 No configuration exists - running setup', { component: 'Config' });
-        // No configuration exists, run setup
-        config = await setupConfig();
-    }
-    logger.debug('🔧 Setting tools configuration', { component: 'Config' });
-    // Set config for tools
-    setToolsConfig(config);
-    logger.debug('🤖 Initializing OpenAI client', { component: 'Config', provider: config.provider });
-    // Initialize OpenAI client with the configuration
-    try {
-        openaiClient = createOpenAIClient(config);
-        if (!openaiClient) {
-            throw new Error('Failed to create OpenAI client');
-        }
-        logger.debug('✅ OpenAI client created successfully', { component: 'Config' });
-        logger.debug('🔄 Creating agentic loop', { component: 'Config', maxIterations: 100, streamOutput: true });
-        // Initialize the agentic loop 
-        agenticLoop = await createAgenticLoop(openaiClient, config, {
-            maxIterations: 100,
-            streamOutput: true
-        });
-        logger.debug(`✅ Successfully initialized ProtoAgent`, { component: 'Config' });
-    }
-    catch (error) {
-        logger.error(`❌ Failed to initialize OpenAI client: ${error.message}`, { component: 'Config', error: error.message });
-        process.exit(1);
-    }
-}
-async function startInteractiveMode() {
-    logger.debug('🚀 Starting interactive mode initialization');
-    logger.debug(' Parsing command line options');
-    // Check for options
-    const options = program.opts();
-    logger.debug('🔍 Command line options parsed', { component: 'Main', options });
-    // Set log level
-    if (options.logLevel) {
-        logger.debug('🔧 Setting log level', { component: 'Main', requestedLevel: options.logLevel });
-        const logLevel = LogLevel[options.logLevel.toUpperCase()];
-        if (logLevel !== undefined) {
-            logger.setLevel(logLevel);
-            logger.debug(`🔍 Log level set to: ${options.logLevel.toUpperCase()}`);
-        }
-        else {
-            logger.warn(`⚠️  Invalid log level: ${options.logLevel}. Using INFO.`);
-        }
-    }
-    // Enable file logging if requested (BEFORE welcome messages)
-    if (options.logToFile) {
-        logger.debug('📝 Enabling file logging', { component: 'Main', logDir: options.logDir || 'default' });
-        logger.enableFileLogging(options.logDir);
-        logger.info('📝 File logging enabled');
-    }
-    // Check for dangerous flag
-    if (options.dangerouslyAcceptAll) {
-        logger.debug('⚠️  Enabling dangerous mode', { component: 'Main' });
-        logger.warn('⚠️  DANGER MODE: All shell commands and file operations will be auto-approved without confirmation!');
-        setToolsDangerouslyAcceptAll(true);
-    }
-    // NOW display welcome messages (after file logging is enabled)
-    logger.consoleLog('🤖 Welcome to ProtoAgent - Your AI Coding Assistant with File System & Shell Powers!');
-    logger.debug('🤖 Welcome message displayed');
-    logger.consoleLog('💡 I can read, write, edit, search files and run shell commands in your project.');
-    logger.consoleLog('🔧 Ask me to create files, analyze code, run npm commands, git operations, or execute any shell command.');
-    logger.debug('💡 Capability messages displayed');
-    logger.consoleLog('🚪 Type "exit" to quit.');
-    logger.debug('🚪 Exit instruction displayed');
-    logger.debug('🔧 Initializing configuration');
-    // Initialize configuration
-    await initializeConfig();
-    // Set up cleanup handlers for file logging
-    logger.debug('🛡️  Setting up cleanup handlers');
-    process.on('SIGINT', () => {
-        logger.debug('🛑 SIGINT received - cleaning up');
-        logger.consoleLog('\n👋 Goodbye! Happy coding!');
-        logger.info('👋 Goodbye message displayed (SIGINT)');
-        logger.disableFileLogging();
-        process.exit(0);
-    });
-    process.on('SIGTERM', () => {
-        logger.debug('🛑 SIGTERM received - cleaning up');
-        logger.disableFileLogging();
-        process.exit(0);
-    });
-    logger.consoleLog(`🧠 Using ${config.provider} with model: ${config.model}`);
-    // Show current working directory
-    logger.consoleLog(`📁 Working directory: ${process.cwd()}`);
-    logger.debug('📁 Working directory displayed to user');
-    logger.debug('🔄 Starting main interaction loop');
-    while (true) {
-        logger.trace('📥 Waiting for user input');
-        const { input } = await inquirer.prompt([
-            {
-                type: 'input',
-                name: 'input',
-                message: 'protoagent>',
-            }
-        ]);
-        logger.debug('📝 User input received', { component: 'Main', inputLength: input.length, isEmpty: input.trim() === '' });
-        if (input.toLowerCase() === 'exit' || input.toLowerCase() === 'quit') {
-            logger.debug('🚪 Exit command received');
-            logger.consoleLog('👋 Goodbye! Happy coding!');
-            logger.info('👋 Goodbye message displayed (normal exit)');
-            // Clean up file logging
-            logger.debug('🧹 Cleaning up file logging');
-            logger.disableFileLogging();
-            break;
-        }
-        if (input.trim() === '') {
-            logger.trace('⏭️  Empty input - continuing');
-            continue;
-        }
-        logger.debug('🤖 Forwarding input to agent', { component: 'Main', input: input.slice(0, 100) + (input.length > 100 ? '...' : '') });
-        await respondToUser(input);
-        logger.trace('✅ User input processing complete');
-    }
-}
-program
-    .action(() => {
-    startInteractiveMode();
-});
-program.parse();