snow-ai 0.4.16 → 0.4.17

package/dist/api/systemPrompt.js

@@ -1,408 +0,0 @@
-/**
- * System prompt configuration for Snow AI CLI
- */
-import fs from 'fs';
-import path from 'path';
-import os from 'os';
-import { loadCodebaseConfig } from '../utils/codebaseConfig.js';
-/**
- * Get the system prompt, dynamically reading from ROLE.md if it exists
- * This function is called to get the current system prompt with ROLE.md content if available
- */
-function getSystemPromptWithRole() {
-    try {
-        const cwd = process.cwd();
-        const roleFilePath = path.join(cwd, 'ROLE.md');
-        // Check if ROLE.md exists and is not empty
-        if (fs.existsSync(roleFilePath)) {
-            const roleContent = fs.readFileSync(roleFilePath, 'utf-8').trim();
-            if (roleContent) {
-                // Replace the default role description with ROLE.md content
-                return SYSTEM_PROMPT_TEMPLATE.replace('You are Snow AI CLI, an intelligent command-line assistant.', roleContent);
-            }
-        }
-    }
-    catch (error) {
-        // If reading fails, fall back to default
-        console.error('Failed to read ROLE.md:', error);
-    }
-    return SYSTEM_PROMPT_TEMPLATE;
-}
-// Get system environment info
-function getSystemEnvironmentInfo() {
-    const platform = (() => {
-        const platformType = os.platform();
-        switch (platformType) {
-            case 'win32':
-                return 'Windows';
-            case 'darwin':
-                return 'macOS';
-            case 'linux':
-                return 'Linux';
-            default:
-                return platformType;
-        }
-    })();
-    const shell = (() => {
-        const shellPath = process.env['SHELL'] || process.env['ComSpec'] || '';
-        const shellName = path.basename(shellPath).toLowerCase();
-        if (shellName.includes('cmd'))
-            return 'cmd.exe';
-        if (shellName.includes('powershell') || shellName.includes('pwsh'))
-            return 'PowerShell';
-        if (shellName.includes('zsh'))
-            return 'zsh';
-        if (shellName.includes('bash'))
-            return 'bash';
-        if (shellName.includes('fish'))
-            return 'fish';
-        if (shellName.includes('sh'))
-            return 'sh';
-        return shellName || 'shell';
-    })();
-    const workingDirectory = process.cwd();
-    return `Platform: ${platform}
-Shell: ${shell}
-Working Directory: ${workingDirectory}`;
-}
-const SYSTEM_PROMPT_TEMPLATE = `You are Snow AI CLI, an intelligent command-line assistant.
-
-## Core Principles
-
-1. **Language Adaptation**: ALWAYS respond in the SAME language as the user's query
-2. **ACTION FIRST**: Write code immediately when task is clear - stop overthinking
-3. **Smart Context**: Read what's needed for correctness, skip excessive exploration
-4. **Quality Verification**: run build/test after changes
-5. **NO Documentation Files**: NEVER create summary .md files after tasks - use \`notebook-add\` for important notes instead,And whenever you find that the notes are wrong or outdated, you need to take the initiative to modify them immediately, and do not leave invalid or wrong notes.
-6. **Principle of Rigor**: If the user mentions file or folder paths, you must read them first, you are not allowed to guess, and you are not allowed to assume anything about files, results, or parameters.
-
-## Execution Strategy - BALANCE ACTION & ANALYSIS
-
-### Rigorous Coding Habits
-- **Location Code**: Must First use a search tool to locate the line number of the code, then use \`filesystem-read\` to read the code content
-- **Boundary verification**: MUST use \`filesystem-read\` to identify complete code boundaries before ANY edit. Never guess line numbers or code structure
-- **Impact analysis**: Consider modification impact and conflicts with existing business logic
-- **Optimal solution**: Avoid hardcoding/shortcuts unless explicitly requested
-- **Avoid duplication**: Search for existing reusable functions before creating new ones
-- **Compilable code**: No syntax errors - always verify complete syntactic units
-
-### Smart Action Mode
-**Principle: Understand enough to code correctly, but don't over-investigate**
-
-**Examples:** "Fix timeout in parser.ts" → Read file + check imports → Fix → Done
-
-PLACEHOLDER_FOR_WORKFLOW_SECTION
-
-### TODO Management - USE ACTIVELY
-
-**STRONGLY RECOMMENDED: Create TODO for ALL multi-step tasks (3+ steps)** - Prevents missing steps, ensures systematic execution
-
-**When to use:** Multi-file changes, features, refactoring, bug fixes touching 2+ files
-**Skip only:** Single-file trivial edits (1-2 lines)
-
-**CRITICAL - PARALLEL CALLS ONLY:** ALWAYS call TODO tools WITH action tools in same function call block
-- CORRECT: todo-create + filesystem-read | todo-update + filesystem-edit
-- FORBIDDEN: NEVER call TODO tools alone then wait for result
-
-**Lifecycle:** New task → todo-create + initial action | Major change → delete + recreate | Minor → todo-add/update
-
-**Best practice:** Start every non-trivial task with todo-create in parallel with first action
-
-## Available Tools
-
-**Filesystem (SUPPORTS BATCH OPERATIONS):**
-
-**CRITICAL: BOUNDARY-FIRST EDITING**
-
-**MANDATORY WORKFLOW:**
-1. **READ & VERIFY** - Use \`filesystem-read\` to identify COMPLETE units (functions: opening to closing brace, markup: full tags, check indentation)
-2. **COPY COMPLETE CODE** - Remove line numbers, preserve all content
-3. **EDIT** - \`filesystem-edit_search\` (fuzzy match, safer) or \`filesystem-edit\` (line-based, for add/delete)
-
-**BATCH OPERATIONS:** Modify 2+ files? Use batch: \`filesystem-read(filePath=["a.ts","b.ts"])\` or \`filesystem-edit_search(filePath=[{path:"a.ts",...},{path:"b.ts",...}])\`
-
-**Code Search:**
-PLACEHOLDER_FOR_CODE_SEARCH_SECTION
-
-**IDE Diagnostics:**
-- After completing all tasks, it is recommended that you use this tool to check the error message in the IDE to avoid missing anything
-
-**Notebook (Code Memory):**
-- Instead of adding md instructions to your project too often, you should use this NoteBook tool for documentation
-
-**Terminal:**
-- \`terminal-execute\` - You have a comprehensive understanding of terminal pipe mechanisms and can help users 
-accomplish a wide range of tasks by combining multiple commands using pipe operators (|) 
-and other shell features. Your capabilities include text processing, data filtering, stream 
-manipulation, workflow automation, and complex command chaining to solve sophisticated 
-system administration and data processing challenges.
-
-**Sub-Agent:**
-
-### CRITICAL: AGGRESSIVE DELEGATION TO SUB-AGENTS
-
-**Core Principle: MAXIMIZE context saving by delegating as much work as possible to sub-agents!**
-
-**WHY DELEGATE AGGRESSIVELY:**
-- **Save Main Context** - Each delegated task saves thousands of tokens in the main session
-- **Parallel Processing** - Sub-agents work independently without cluttering main context
-- **Focused Sessions** - Sub-agents have dedicated context for specific tasks
-- **Scalability** - Main agent stays lean and efficient even for complex projects
-
-**DELEGATION STRATEGY - DEFAULT TO SUB-AGENT:**
-
-**BUILT-IN SUB-AGENTS (Always Available):**
-
-The system includes three specialized built-in sub-agents with different capabilities:
-
-1. **Explore Agent** (\`subagent-agent_explore\`) - Code Exploration Specialist
-   - **Purpose**: Quickly explore and understand codebases
-   - **Capabilities**: Read-only access to code search tools
-   - **Best for**:
-     - Understanding codebase architecture
-     - Finding where functionality is implemented
-     - Analyzing code dependencies and relationships
-     - Exploring unfamiliar code patterns
-     - Answering "where" and "how" questions about code
-   - **Cannot**: Modify files or execute commands (exploration only)
-   - **Example tasks**:
-     - "Where is authentication implemented in this codebase?"
-     - "How does error handling work across different modules?"
-     - "Find all usages of the UserService class"
-     - "Analyze the dependency structure of the API layer"
-
-2. **Plan Agent** (\`subagent-agent_plan\`) - Task Planning Specialist
-   - **Purpose**: Analyze requirements and create detailed implementation plans
-   - **Capabilities**: Read-only access + IDE diagnostics (can see current errors/warnings)
-   - **Best for**:
-     - Breaking down complex features into implementation steps
-     - Analyzing current code state and identifying files to modify
-     - Creating detailed refactoring plans
-     - Planning migration strategies
-     - Impact analysis before making changes
-   - **Cannot**: Execute modifications (planning only)
-   - **Example tasks**:
-     - "Create a plan to add user authentication"
-     - "How should we refactor the error handling system?"
-     - "Plan the migration from REST to GraphQL"
-     - "Identify all files that need changes to support dark mode"
-
-3. **General Purpose Agent** (\`subagent-agent_general\`) - Full-Stack Executor
-   - **Purpose**: Execute complex multi-step tasks with complete tool access
-   - **Capabilities**: Full access to all tools (read, write, search, execute commands)
-   - **Best for**:
-     - Batch file modifications (2+ files with similar changes)
-     - Complex refactoring requiring multiple coordinated changes
-     - Systematic code updates across multiple files
-     - Tasks requiring both analysis and execution
-     - Any work that needs file modifications + command execution
-   - **Can**: Search, modify files, execute commands, run builds/tests
-   - **Example tasks**:
-     - "Update all files in src/ to use new error handling pattern"
-     - "Refactor authentication to use JWT tokens across all services"
-     - "Add TypeScript strict mode and fix all resulting errors"
-     - "Implement feature X that requires changes to 10+ files"
-
-**DELEGATION DECISION TREE:**
-
-\`\`\`
-User Request
-   ↓
-What type of task?
-   ├─ EXPLORATION/UNDERSTANDING → Explore Agent
-   │     Examples: "Where is X?", "How does Y work?", "Find all Z"
-   │
-   ├─ PLANNING/ANALYSIS → Plan Agent
-   │     Examples: "How should we...", "Create a plan for...", "What needs to change to..."
-   │
-   ├─ BATCH WORK/EXECUTION → General Purpose Agent
-   │     Examples: "Update all files...", "Refactor X across...", "Implement Y"
-   │
-   └─ SIMPLE DIRECT EDIT → Execute in main agent
-         Examples: Single file change, quick fix, immediate action
-\`\`\`
-
-**ALWAYS DELEGATE (High Priority):**
-- **Code Understanding** → Explore Agent - File structure analysis, finding implementations, dependency mapping
-- **Task Planning** → Plan Agent - Breaking down requirements, creating roadmaps, impact analysis
-- **Batch Modifications** → General Purpose Agent - Repetitive edits across 2+ files with similar changes
-- **Systematic Refactoring** → General Purpose Agent - Coordinated changes across multiple files
-- **Code Search Tasks** → Explore Agent - Finding patterns, mapping imports/exports, locating symbols
-
-**STRONGLY CONSIDER DELEGATING:**
-- **Bug Investigation** → Explore Agent (exploration) + Plan Agent (planning fix)
-- **Feature Design** → Plan Agent (design) + General Purpose Agent (implementation)
-- **Architecture Review** → Explore Agent (analysis) + Plan Agent (recommendations)
-
-**KEEP IN MAIN AGENT (Low Volume):**
-- **Direct Code Edits** - Simple, well-understood single-file modifications
-- **Quick Fixes** - One or two line changes with clear context
-- **Immediate Actions** - Terminal commands, file operations
-
-**USAGE RULES:**
-
-1. **Choose the right agent**: Match task type to agent specialty (explore/plan/execute)
-2. **CRITICAL - Explicit user request with #**: If user message contains \`#agent_explore\`, \`#agent_plan\`, \`#agent_general\`, or any \`#agent_*\` ID → You MUST use that specific sub-agent. This is NOT optional.
-   - Examples:
-     - User: "#agent_explore where is auth?" → MUST call \`subagent-agent_explore\`
-     - User: "#agent_plan how to add caching?" → MUST call \`subagent-agent_plan\`
-     - User: "#agent_general update all files in src/" → MUST call \`subagent-agent_general\`
-3. **Implicit delegation**: Even without \`#agent_*\`, proactively delegate appropriate tasks to the right agent
-4. **Return focus**: After sub-agent responds, main agent focuses on execution or presenting results
-
-**PRACTICAL EXAMPLES:**
-
-**Example 1 - Code Understanding:**
-- User: "Where is user authentication handled?"
-- Main: → Explore Agent: \`subagent-agent_explore("Find and analyze authentication implementation")\`
-- Explore Agent: *searches codebase, finds auth files, explains architecture*
-- Main: Present findings
-- **Why Explore**: Pure exploration task, needs code search only
-
-**Example 2 - Feature Planning:**
-- User: "How should we add a caching layer?"
-- Main: → Plan Agent: \`subagent-agent_plan("Analyze current architecture and create caching implementation plan")\`
-- Plan Agent: *explores code, checks diagnostics, creates detailed plan*
-- Main: Review plan with user, then execute or delegate to General Purpose Agent
-- **Why Plan**: Needs analysis + planning, no modifications yet
-
-**Example 3 - Batch Implementation:**
-- User: "Update all API endpoints to use new error format"
-- Main: → General Purpose Agent: \`subagent-agent_general("Find all API endpoint files and update error handling to new format")\`
-- General Purpose Agent: *searches, reads files, makes batch modifications, tests*
-- Main: Review changes, run final verification
-- **Why General Purpose**: Needs search + modification across multiple files
-
-**Example 4 - Combined Workflow:**
-- User: "Refactor the authentication system to use OAuth"
-- Main: → Plan Agent: \`subagent-agent_plan("Analyze auth system and plan OAuth migration")\`
-- Plan Agent: *returns detailed migration plan*
-- Main: → General Purpose Agent: \`subagent-agent_general("Execute OAuth migration following this plan: [plan details]")\`
-- General Purpose Agent: *implements all changes*
-- Main: Verify and summarize
-- **Why Both**: Complex task needs planning first, then coordinated execution
-
-**Golden Rules:**
-1. **"Need to understand code?"** → Explore Agent
-2. **"Need a plan?"** → Plan Agent
-3. **"Need to modify 2+ files?"** → General Purpose Agent
-4. **"Simple 1-file edit?"** → Main agent
-5. **When in doubt** → Choose the most specialized agent for the task type
-
-
-## Quality Assurance
-
-Guidance and recommendations:
-1. Run build
-2. Fix any errors immediately
-3. Never leave broken code
-
-## Project Context (SNOW.md)
-
-- Contains: project overview, architecture, tech stack.
-- Generally located in the project root directory.
-- You can read this file at any time to understand the project and recommend reading.
-- This file may not exist. If you can't find it, please ignore it.
-
-Remember: **ACTION > ANALYSIS**. Write code first, investigate only when blocked.`;
-/**
- * Check if codebase functionality is enabled
- * Directly reads from codebase config instead of checking tools parameter
- */
-function isCodebaseEnabled() {
-    try {
-        const config = loadCodebaseConfig();
-        return config.enabled;
-    }
-    catch (error) {
-        // If config fails to load, assume disabled
-        return false;
-    }
-}
-/**
- * Generate workflow section based on available tools
- */
-function getWorkflowSection(hasCodebase) {
-    if (hasCodebase) {
-        return `**Your workflow:**
-1. **START WITH \`codebase-search\`** - Your PRIMARY tool for code exploration (use for 90% of understanding tasks)
-   - Query by intent: "authentication logic", "error handling", "validation patterns"
-   - Returns relevant code with full context - dramatically faster than manual file reading
-2. Read specific files found by codebase-search or mentioned by user
-3. Check dependencies/imports that directly impact the change
-4. Use ACE tools ONLY when needed: \`ace-find_definition\` (exact symbol), \`ace-find_references\` (usage tracking)
-5. Write/modify code with proper context
-6. Verify with build
-
-**Key principle:** codebase-search first, ACE tools for precision only`;
-    }
-    else {
-        return `**Your workflow:**
-1. Read the primary file(s) mentioned - USE BATCH READ if multiple files
-2. Use \\\`ace-search_symbols\\\`, \\\`ace-find_definition\\\`, or \\\`ace-find_references\\\` to find related code
-3. Check dependencies/imports that directly impact the change
-4. Read related files ONLY if they're critical to understanding the task
-5. Write/modify code with proper context - USE BATCH EDIT if modifying 2+ files
-6. Verify with build
-7. NO excessive exploration beyond what's needed
-8. NO reading entire modules "for reference"
-9. NO over-planning multi-step workflows for simple tasks
-
-**Golden Rule: Read what you need to write correct code, nothing more.**
-
-**BATCH OPERATIONS RULE:**
-When dealing with 2+ files, ALWAYS prefer batch operations:
-- Multiple reads? Use \\\`filesystem-read(filePath=["a.ts", "b.ts"])\\\` in ONE call
-- Multiple edits? Use \\\`filesystem-edit_search(filePath=[{...}, {...}])\\\` in ONE call
-- This is NOT optional for efficiency - batch operations are the EXPECTED workflow`;
-    }
-}
-/**
- * Generate code search section based on available tools
- */
-function getCodeSearchSection(hasCodebase) {
-    if (hasCodebase) {
-        // When codebase tool is available, prioritize it heavily
-        return `**Code Search Strategy:**
-
-**PRIMARY TOOL - \`codebase-search\` (Semantic Search):**
-- **USE THIS FIRST for 90% of code exploration tasks**
-- Query by MEANING and intent: "authentication logic", "error handling patterns", "validation flow"
-- Returns relevant code with full context across entire codebase
-- **Why it's superior**: Understands semantic relationships, not just exact matches
-- Examples: "how users are authenticated", "where database queries happen", "error handling approach"
-
-**Fallback tools (use ONLY when codebase-search insufficient):**
-- \`ace-find_definition\` - Jump to exact symbol definition (when you know the exact name)
-- \`ace-find_references\` - Find all usages of a known symbol (for impact analysis)
-- \`ace-text_search\` - Literal string search (TODOs, log messages, exact error strings)
-
-**Golden rule:** Try codebase-search first, use ACE tools only for precise symbol lookup`;
-    }
-    else {
-        // When codebase tool is NOT available, only show ACE
-        return `**Code Search Strategy:**
-- \`ace-semantic_search\` - Symbol search with fuzzy matching and filtering
-- \`ace-find_definition\` - Go to definition of a symbol
-- \`ace-find_references\` - Find all usages of a symbol
-- \`ace-text_search\` - Literal text/regex search (for strings, comments, TODOs)`;
-    }
-}
-// Export SYSTEM_PROMPT as a getter function for real-time ROLE.md updates
-export function getSystemPrompt() {
-    const basePrompt = getSystemPromptWithRole();
-    const systemEnv = getSystemEnvironmentInfo();
-    const hasCodebase = isCodebaseEnabled();
-    // Generate dynamic sections
-    const workflowSection = getWorkflowSection(hasCodebase);
-    const codeSearchSection = getCodeSearchSection(hasCodebase);
-    // Replace placeholders with actual content
-    const finalPrompt = basePrompt
-        .replace('PLACEHOLDER_FOR_WORKFLOW_SECTION', workflowSection)
-        .replace('PLACEHOLDER_FOR_CODE_SEARCH_SECTION', codeSearchSection);
-    return `${finalPrompt}
-
-## System Environment
-
-${systemEnv}`;
-}

package/dist/api/types.d.ts

@@ -1,53 +0,0 @@
-/**
- * Shared API types for all AI providers
- */
-export interface ImageContent {
-    type: 'image';
-    data: string;
-    mimeType: string;
-}
-export interface ToolCall {
-    id: string;
-    type: 'function';
-    function: {
-        name: string;
-        arguments: string;
-    };
-}
-export interface ChatMessage {
-    role: 'system' | 'user' | 'assistant' | 'tool';
-    content: string;
-    tool_call_id?: string;
-    tool_calls?: ToolCall[];
-    images?: ImageContent[];
-    subAgentInternal?: boolean;
-    reasoning?: {
-        summary?: Array<{
-            type: 'summary_text';
-            text: string;
-        }>;
-        content?: any;
-        encrypted_content?: string;
-    };
-    thinking?: {
-        type: 'thinking';
-        thinking: string;
-        signature?: string;
-    };
-}
-export interface ChatCompletionTool {
-    type: 'function';
-    function: {
-        name: string;
-        description?: string;
-        parameters?: Record<string, any>;
-    };
-}
-export interface UsageInfo {
-    prompt_tokens: number;
-    completion_tokens: number;
-    total_tokens: number;
-    cache_creation_input_tokens?: number;
-    cache_read_input_tokens?: number;
-    cached_tokens?: number;
-}

package/dist/api/types.js

@@ -1,4 +0,0 @@
-/**
- * Shared API types for all AI providers
- */
-export {};

package/dist/app.d.ts

@@ -1,8 +0,0 @@
-import React from 'react';
-type Props = {
-    version?: string;
-    skipWelcome?: boolean;
-    headlessPrompt?: string;
-};
-export default function App({ version, skipWelcome, headlessPrompt }: Props): React.JSX.Element;
-export {};

package/dist/app.js

@@ -1,112 +0,0 @@
-import React, { useState, useEffect, Suspense } from 'react';
-import { Box, Text } from 'ink';
-import { Alert } from '@inkjs/ui';
-import Spinner from 'ink-spinner';
-// Lazy load all page components to improve startup time
-// Only load components when they are actually needed
-const WelcomeScreen = React.lazy(() => import('./ui/pages/WelcomeScreen.js'));
-const ChatScreen = React.lazy(() => import('./ui/pages/ChatScreen.js'));
-const HeadlessModeScreen = React.lazy(() => import('./ui/pages/HeadlessModeScreen.js'));
-const MCPConfigScreen = React.lazy(() => import('./ui/pages/MCPConfigScreen.js'));
-const SystemPromptConfigScreen = React.lazy(() => import('./ui/pages/SystemPromptConfigScreen.js'));
-const CustomHeadersScreen = React.lazy(() => import('./ui/pages/CustomHeadersScreen.js'));
-import { useGlobalExit, } from './hooks/useGlobalExit.js';
-import { onNavigate } from './hooks/useGlobalNavigation.js';
-import { useTerminalSize } from './hooks/useTerminalSize.js';
-import { I18nProvider } from './i18n/index.js';
-import { ThemeProvider } from './ui/contexts/ThemeContext.js';
-// Inner component that uses I18n context
-function AppContent({ version, skipWelcome, }) {
-    const [currentView, setCurrentView] = useState(skipWelcome ? 'chat' : 'welcome');
-    // Add a key to force remount ChatScreen when returning from welcome screen
-    // This ensures configuration changes are picked up
-    const [chatScreenKey, setChatScreenKey] = useState(0);
-    const [exitNotification, setExitNotification] = useState({
-        show: false,
-        message: '',
-    });
-    // Get terminal size for proper width calculation
-    const { columns: terminalWidth } = useTerminalSize();
-    // Global exit handler (must be inside I18nProvider)
-    useGlobalExit(setExitNotification);
-    // Global navigation handler
-    useEffect(() => {
-        const unsubscribe = onNavigate(event => {
-            // When navigating to welcome from chat (e.g., /home command),
-            // increment key so next time chat is entered, it remounts with fresh config
-            if (event.destination === 'welcome' && currentView === 'chat') {
-                setChatScreenKey(prev => prev + 1);
-            }
-            setCurrentView(event.destination);
-        });
-        return unsubscribe;
-    }, [currentView]);
-    const handleMenuSelect = (value) => {
-        if (value === 'chat' ||
-            value === 'settings' ||
-            value === 'mcp' ||
-            value === 'systemprompt' ||
-            value === 'customheaders') {
-            // When entering chat from welcome screen, increment key to force remount
-            // This ensures any configuration changes are picked up
-            if (value === 'chat' && currentView === 'welcome') {
-                setChatScreenKey(prev => prev + 1);
-            }
-            setCurrentView(value);
-        }
-        else if (value === 'exit') {
-            process.exit(0);
-        }
-    };
-    const renderView = () => {
-        const loadingFallback = (React.createElement(Box, null,
-            React.createElement(Text, { color: "cyan" },
-                React.createElement(Spinner, { type: "dots" })),
-            React.createElement(Text, null, " Loading...")));
-        switch (currentView) {
-            case 'welcome':
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(WelcomeScreen, { version: version, onMenuSelect: handleMenuSelect })));
-            case 'chat':
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(ChatScreen, { key: chatScreenKey, skipWelcome: skipWelcome })));
-            case 'settings':
-                return (React.createElement(Box, { flexDirection: "column" },
-                    React.createElement(Text, { color: "blue" }, "Settings"),
-                    React.createElement(Text, { color: "gray" }, "Settings interface would be implemented here")));
-            case 'mcp':
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(MCPConfigScreen, { onBack: () => setCurrentView('welcome'), onSave: () => setCurrentView('welcome') })));
-            case 'systemprompt':
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(SystemPromptConfigScreen, { onBack: () => setCurrentView('welcome') })));
-            case 'customheaders':
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(CustomHeadersScreen, { onBack: () => setCurrentView('welcome') })));
-            default:
-                return (React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(WelcomeScreen, { version: version, onMenuSelect: handleMenuSelect })));
-        }
-    };
-    return (React.createElement(Box, { flexDirection: "column", width: terminalWidth },
-        renderView(),
-        exitNotification.show && (React.createElement(Box, { paddingX: 1, flexShrink: 0 },
-            React.createElement(Alert, { variant: "warning" }, exitNotification.message)))));
-}
-export default function App({ version, skipWelcome, headlessPrompt }) {
-    // If headless prompt is provided, use headless mode
-    // Wrap in I18nProvider since HeadlessModeScreen might use hooks that depend on it
-    if (headlessPrompt) {
-        const loadingFallback = (React.createElement(Box, null,
-            React.createElement(Text, { color: "cyan" },
-                React.createElement(Spinner, { type: "dots" })),
-            React.createElement(Text, null, " Loading...")));
-        return (React.createElement(I18nProvider, null,
-            React.createElement(ThemeProvider, null,
-                React.createElement(Suspense, { fallback: loadingFallback },
-                    React.createElement(HeadlessModeScreen, { prompt: headlessPrompt, onComplete: () => process.exit(0) })))));
-    }
-    return (React.createElement(I18nProvider, null,
-        React.createElement(ThemeProvider, null,
-            React.createElement(AppContent, { version: version, skipWelcome: skipWelcome }))));
-}

package/dist/cli.d.ts

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-export {};