prompt-language-shell 0.6.8 → 0.7.0

package/dist/index.js

@@ -4,6 +4,7 @@ import { existsSync, readFileSync } from 'fs';
 import { dirname, join } from 'path';
 import { fileURLToPath } from 'url';
 import { render } from 'ink';
+import { DebugLevel } from './services/configuration.js';
 import { Main } from './ui/Main.js';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
@@ -20,7 +21,7 @@ const app = {
     version: packageJson.version,
     description: packageJson.description,
     isDev,
-    isDebug: false,
+    debug: DebugLevel.None,
 };
 // Get command from command-line arguments
 const args = process.argv.slice(2);

package/dist/services/anthropic.js

@@ -1,5 +1,6 @@
 import Anthropic from '@anthropic-ai/sdk';
 import { getAvailableConfigStructure, getConfiguredKeys, } from './configuration.js';
+import { logPrompt, logResponse } from './logger.js';
 import { formatSkillsForPrompt, loadSkillsWithValidation } from './skills.js';
 import { toolRegistry } from './registry.js';
 /**
@@ -70,7 +71,7 @@ export class AnthropicService {
         if (toolName === 'config') {
             const configStructure = getAvailableConfigStructure();
             const configuredKeys = getConfiguredKeys();
-            const configSection = '\n\n## Available Configuration\n\n' +
+            const configSection = '\n## Available Configuration\n\n' +
                 'Config structure (key: description):\n' +
                 JSON.stringify(configStructure, null, 2) +
                 '\n\nConfigured keys (keys that exist in config file):\n' +
@@ -85,7 +86,15 @@ export class AnthropicService {
                 name: 'web_search',
             });
         }
+        // Collect debug components
+        const debug = [];
+        // Log prompt at Verbose level
+        const promptDebug = logPrompt(toolName, command, systemPrompt);
+        if (promptDebug) {
+            debug.push(promptDebug);
+        }
         // Call API with tool
+        const startTime = Date.now();
         const response = await this.client.messages.create({
             model: this.model,
             max_tokens: 1024,
@@ -99,6 +108,12 @@ export class AnthropicService {
                 },
             ],
         });
+        const duration = Date.now() - startTime;
+        // Log response at Verbose level
+        const responseDebug = logResponse(toolName, response, duration);
+        if (responseDebug) {
+            debug.push(responseDebug);
+        }
         // Check for truncation
         if (response.stop_reason === 'max_tokens') {
             throw new Error('Response was truncated due to length. Please simplify your request or break it into smaller parts.');
@@ -113,6 +128,7 @@ export class AnthropicService {
                     message: '',
                     tasks: [],
                     answer: cleanAnswerText(textContent.text),
+                    debug,
                 };
             }
         }
@@ -143,6 +159,7 @@ export class AnthropicService {
                 message: input.message,
                 tasks: [],
                 commands: input.commands,
+                debug,
             };
         }
         // Handle answer tool response
@@ -157,6 +174,7 @@ export class AnthropicService {
                 message: '',
                 tasks: [],
                 answer: cleanAnswerText(input.answer),
+                debug,
             };
         }
         // Handle plan and introspect tool responses
@@ -175,6 +193,7 @@ export class AnthropicService {
         return {
             message: input.message,
             tasks: input.tasks,
+            debug,
         };
     }
 }

package/dist/services/components.js

@@ -252,6 +252,17 @@ export function createMessage(text) {
         },
     };
 }
+export function createDebugDefinition(title, content, color) {
+    return {
+        id: randomUUID(),
+        name: ComponentName.Debug,
+        props: {
+            title,
+            content,
+            color,
+        },
+    };
+}
 export function createRefinement(text, onAborted) {
     return {
         id: randomUUID(),

package/dist/services/configuration.js

@@ -9,6 +9,13 @@ export var AnthropicModel;
     AnthropicModel["Opus"] = "claude-opus-4-1";
 })(AnthropicModel || (AnthropicModel = {}));
 export const SUPPORTED_MODELS = Object.values(AnthropicModel);
+export var DebugLevel;
+(function (DebugLevel) {
+    DebugLevel["None"] = "none";
+    DebugLevel["Info"] = "info";
+    DebugLevel["Verbose"] = "verbose";
+})(DebugLevel || (DebugLevel = {}));
+export const SUPPORTED_DEBUG_LEVELS = Object.values(DebugLevel);
 export var ConfigDefinitionType;
 (function (ConfigDefinitionType) {
     ConfigDefinitionType["RegExp"] = "regexp";
@@ -62,8 +69,17 @@ function validateConfig(parsed) {
     if (config.settings && typeof config.settings === 'object') {
         const settings = config.settings;
         validatedConfig.settings = {};
-        if ('debug' in settings && typeof settings.debug === 'boolean') {
-            validatedConfig.settings.debug = settings.debug;
+        if ('debug' in settings) {
+            // Handle migration from boolean to enum
+            if (typeof settings.debug === 'boolean') {
+                validatedConfig.settings.debug = settings.debug
+                    ? DebugLevel.Info
+                    : DebugLevel.None;
+            }
+            else if (typeof settings.debug === 'string' &&
+                SUPPORTED_DEBUG_LEVELS.includes(settings.debug)) {
+                validatedConfig.settings.debug = settings.debug;
+            }
         }
     }
     return validatedConfig;
@@ -139,10 +155,10 @@ export function saveDebugSetting(debug) {
 export function loadDebugSetting() {
     try {
         const config = loadConfig();
-        return config.settings?.debug ?? false;
+        return config.settings?.debug ?? DebugLevel.None;
     }
     catch {
-        return false;
+        return DebugLevel.None;
     }
 }
 /**
@@ -193,8 +209,10 @@ const coreConfigSchema = {
         description: 'Anthropic model',
     },
     'settings.debug': {
-        type: ConfigDefinitionType.Boolean,
+        type: ConfigDefinitionType.Enum,
         required: false,
+        values: SUPPORTED_DEBUG_LEVELS,
+        default: DebugLevel.None,
         description: 'Debug mode',
     },
 };

package/dist/services/logger.js

@@ -0,0 +1,64 @@
+import { createDebugDefinition } from './components.js';
+import { DebugLevel, loadDebugSetting } from './configuration.js';
+import { Palette } from './colors.js';
+/**
+ * Debug logger for the application
+ * Logs information based on the current debug level setting
+ */
+let currentDebugLevel = DebugLevel.None;
+/**
+ * Initialize the logger with the current debug level from config
+ */
+export function initializeLogger() {
+    currentDebugLevel = loadDebugSetting();
+}
+/**
+ * Set the debug level (used for testing or runtime changes)
+ */
+export function setDebugLevel(debug) {
+    currentDebugLevel = debug;
+}
+/**
+ * Get the current debug level
+ */
+export function getDebugLevel() {
+    return currentDebugLevel;
+}
+/**
+ * Create debug component for system prompts sent to the LLM
+ * Only creates at Verbose level
+ */
+export function logPrompt(toolName, command, instructions) {
+    if (currentDebugLevel !== DebugLevel.Verbose) {
+        return null;
+    }
+    const content = [
+        '',
+        `Tool: ${toolName}`,
+        `Command: ${command}`,
+        '',
+        instructions,
+    ].join('\n');
+    // Calculate stats for the instructions
+    const lines = instructions.split('\n').length;
+    const bytes = Buffer.byteLength(instructions, 'utf-8');
+    const title = `SYSTEM PROMPT (${String(lines)} lines, ${String(bytes)} bytes)`;
+    return createDebugDefinition(title, content, Palette.Gray);
+}
+/**
+ * Create debug component for LLM responses received
+ * Only creates at Verbose level
+ */
+export function logResponse(toolName, response, durationMs) {
+    if (currentDebugLevel !== DebugLevel.Verbose) {
+        return null;
+    }
+    const content = [
+        '',
+        `Tool: ${toolName}`,
+        '',
+        JSON.stringify(response, null, 2),
+    ].join('\n');
+    const title = `LLM RESPONSE (${String(durationMs)} ms)`;
+    return createDebugDefinition(title, content, Palette.AshGray);
+}

package/dist/services/messages.js

@@ -1,4 +1,4 @@
-import { loadDebugSetting } from './configuration.js';
+import { DebugLevel, loadDebugSetting } from './configuration.js';
 export { formatDuration } from './utils.js';
 /**
  * Returns a natural language confirmation message for plan execution.
@@ -96,7 +96,7 @@ export const FeedbackMessages = {
  */
 export function formatErrorMessage(error) {
     const rawMessage = error instanceof Error ? error.message : 'Unknown error occurred';
-    if (loadDebugSetting()) {
+    if (loadDebugSetting() !== DebugLevel.None) {
         return rawMessage;
     }
     // Try to extract message from Anthropic API error format

package/dist/services/refinement.js

@@ -24,6 +24,10 @@ export async function handleRefinement(selectedTasks, service, originalCommand,
         const refinedResult = await service.processWithTool(refinedCommand, 'plan');
         // Complete the Refinement component
         handlers.completeActive();
+        // Add debug components to timeline if present
+        if (refinedResult.debug && refinedResult.debug.length > 0) {
+            handlers.addToTimeline(...refinedResult.debug);
+        }
         // Route refined tasks to appropriate components
         routeTasksWithConfirm(refinedResult.tasks, refinedResult.message, service, originalCommand, handlers, false // No DEFINE tasks in refined result
         );

package/dist/services/skills.js

@@ -131,7 +131,6 @@ export function formatSkillsForPrompt(skills) {
         return '';
     }
     const header = `
-
 ## Available Skills
 
 The following skills define domain-specific workflows. When the user's
@@ -147,7 +146,7 @@ brackets for additional information. Use commas instead. For example:
 - WRONG: "Build project Alpha (the legacy version)"
 
 `;
-    const skillsContent = skills.join('\n\n');
+    const skillsContent = skills.map((s) => s.trim()).join('\n\n');
     return header + skillsContent;
 }
 /**

package/dist/skills/answer.md

@@ -5,9 +5,9 @@ command-line concierge. Your role is to **answer questions** and provide
 up-to-date information when a task with type "answer" has been planned and
 confirmed.
 
-**IMPORTANT**: Use web search to find current, accurate information. This tool
-is designed for quick answers from the terminal without needing to open a web
-browser. Always search for the latest data rather than relying solely on
+**IMPORTANT**: Use web search to find current, accurate information. This
+tool is designed for quick answers from the terminal without needing to open a
+web browser. Always search for the latest data rather than relying solely on
 training data.
 
 ## Execution Flow
@@ -60,11 +60,11 @@ TypeScript code compiles to JavaScript and runs anywhere JavaScript runs.
 
 Bad answer (too verbose):
 ```
-TypeScript is a strongly typed programming language that builds on JavaScript,
-giving you better tooling at any scale. TypeScript adds additional syntax to
-JavaScript to support a tighter integration with your editor. It catches errors
-early in development by checking types. TypeScript code converts to JavaScript
-which runs anywhere.
+TypeScript is a strongly typed programming language that builds on
+JavaScript, giving you better tooling at any scale. TypeScript adds
+additional syntax to JavaScript to support a tighter integration with your
+editor. It catches errors early in development by checking types. TypeScript
+code converts to JavaScript which runs anywhere.
 ```
 
 ### Example 2: Technical explanation
@@ -101,7 +101,8 @@ They enable cleaner, more reusable component logic.
 
 ## Guidelines
 
-1. **Be direct**: Answer the question immediately, don't introduce your answer
+1. **Be direct**: Answer the question immediately, don't introduce your
+   answer
 2. **Be accurate**: Provide correct, factual information
 3. **Be concise**: Respect the 4-line, 80-character constraints strictly
 4. **Be helpful**: Focus on what the user needs to know

package/dist/skills/config.md

@@ -1,33 +1,40 @@
 ## Overview
 
-You are the CONFIG tool for "pls" (please), a professional command-line concierge.
-Your role is to determine which configuration settings the user wants to configure
-based on their query.
+You are the CONFIG tool for "pls" (please), a professional command-line
+concierge. Your role is to determine which configuration settings the user
+wants to configure based on their query.
 
 ## Input
 
 You will receive:
-- `configStructure`: Object mapping config keys to descriptions (e.g., {"anthropic.key": "Anthropic API key", "settings.debug": "Debug mode (optional)"})
-- `configuredKeys`: Array of keys that exist in the user's config file (e.g., ["anthropic.key", "anthropic.model", "settings.debug"])
+- `configStructure`: Object mapping config keys to descriptions (e.g.,
+  {"anthropic.key": "Anthropic API key", "settings.debug": "Debug mode
+  (optional)"})
+- `configuredKeys`: Array of keys that exist in the user's config file
+  (e.g., ["anthropic.key", "anthropic.model", "settings.debug"])
 - `query`: User's request (e.g., "app", "mode", "anthropic", or empty)
 
 ## Task
 
-Determine which config keys the user wants to configure and return them as tasks.
+Determine which config keys the user wants to configure and return them
+as tasks.
 
 ## Mapping Rules
 
 ### Query: "app" or empty/unclear
 - Return all **required** config keys (those needed for the app to work)
-- Also include any keys marked as "(optional)" that appear in `configuredKeys` (optional settings that exist in user's config file)
-- Also include any keys marked as "(discovered)" (they exist in user's config file but aren't in schema)
+- Also include any keys marked as "(optional)" that appear in
+  `configuredKeys` (optional settings that exist in user's config file)
+- Also include any keys marked as "(discovered)" (they exist in user's
+  config file but aren't in schema)
 - Required keys: `anthropic.key`, `anthropic.model`
 
 ### Query: "mode"
 - Return only: `settings.debug`
 
 ### Query: "anthropic"
-- Return all keys starting with `anthropic.` (usually `anthropic.key` and `anthropic.model`)
+- Return all keys starting with `anthropic.` (usually `anthropic.key` and
+  `anthropic.model`)
 
 ### Other queries
 - Match the query against config key names and descriptions

package/dist/skills/execute.md

@@ -1,8 +1,8 @@
 ## Overview
 
-You are the execution component of "pls" (please), a professional command-line
-concierge. Your role is to **execute shell commands** and operations when tasks
-with type "execute" have been planned and confirmed.
+You are the execution component of "pls" (please), a professional
+command-line concierge. Your role is to **execute shell commands** and
+operations when tasks with type "execute" have been planned and confirmed.
 
 ## Execution Flow
 
@@ -11,23 +11,23 @@ This tool is invoked AFTER:
 2. User reviewed and confirmed the plan
 3. The execute tasks are now being executed
 
-Your task is to translate the planned actions into specific shell commands that
-can be run in the terminal.
+Your task is to translate the planned actions into specific shell commands
+that can be run in the terminal.
 
 ## Input
 
 You will receive:
 - An array of tasks with their actions and parameters
-- Each task describes what needs to be done (e.g., "Create a new file called
-  test.txt", "List files in the current directory")
+- Each task describes what needs to be done (e.g., "Create a new file
+  called test.txt", "List files in the current directory")
 - Tasks may include params with specific values (paths, filenames, etc.)
-- Tasks from user-defined skills include params.skill (skill name) and parameter
-  values that were substituted into the action
+- Tasks from user-defined skills include params.skill (skill name) and
+  parameter values that were substituted into the action
 
 ## Skill-Based Command Generation
 
-**CRITICAL**: When tasks originate from a user-defined skill, you MUST use the
-skill's **Execution** section to generate commands, NOT invent your own.
+**CRITICAL**: When tasks originate from a user-defined skill, you MUST use
+the skill's **Execution** section to generate commands, NOT invent your own.
 
 ### Understanding Skill Structure
 
@@ -35,16 +35,18 @@ User-defined skills have two key sections:
 - **Steps**: Describes WHAT to do (shown to user as task actions)
 - **Execution**: Describes HOW to do it (actual shell commands)
 
-Each line in Steps corresponds to a line in Execution at the same position.
+Each line in Steps corresponds to a line in Execution at the same
+position.
 
 ### How to Generate Commands from Skills
 
 1. **Identify skill tasks**: Check if tasks have params.skill
-2. **Find the skill**: Look up the skill in "Available Skills" section below
+2. **Find the skill**: Look up the skill in "Available Skills" section
+   below
 3. **Match tasks to Execution**: Each task action came from a Steps line;
    use the corresponding Execution line for the command
-4. **Substitute parameters**: Replace {PARAM} placeholders with actual values
-   from task params
+4. **Substitute parameters**: Replace {PARAM} placeholders with actual
+   values from task params
 
 ### Example Skill
 
@@ -59,8 +61,8 @@ Process Data
 
 ### Execution
 - curl -O https://data.example.com/{SOURCE}.csv
-- python3 transform.py --input {SOURCE}.csv --output processed.csv
-- csvtool col 1-3 processed.csv > output.{FORMAT}
+- python3 transform.py --input {SOURCE}.csv --output data.csv
+- csvtool col 1-3 data.csv > output.{FORMAT}
 ```
 
 ### Matching Process
@@ -77,9 +79,9 @@ Given tasks from this skill:
 Do NOT invent different commands - use exactly what the skill specifies,
 with parameter placeholders replaced by actual values.
 
-**CRITICAL**: Take the exact command from the ### Execution section. Do not
-modify, improve, or rewrite the command in any way. The user wrote these
-commands specifically for their environment and workflow.
+**CRITICAL**: Take the exact command from the ### Execution section. Do
+not modify, improve, or rewrite the command in any way. The user wrote
+these commands specifically for their environment and workflow.
 
 ## Response Format
 
@@ -90,9 +92,11 @@ Return a structured response with commands to execute:
 - **commands**: Array of command objects to execute sequentially
 
 **Command object structure:**
-- **description**: Brief description of what this command does (max 64 chars)
+- **description**: Brief description of what this command does (max 64
+  chars)
 - **command**: The exact shell command to run
-- **workdir**: Optional working directory for the command (defaults to current)
+- **workdir**: Optional working directory for the command (defaults to
+  current)
 - **timeout**: Optional timeout in milliseconds (defaults to 30000)
 - **critical**: Whether failure should stop execution (defaults to true)
 
@@ -101,24 +105,31 @@ Return a structured response with commands to execute:
 When generating commands:
 
 1. **Be precise**: Generate exact, runnable shell commands
-2. **Be safe**: Never generate destructive commands without explicit user intent
-3. **Use parameters**: Extract values from task params and incorporate them
+2. **Be safe**: Never generate destructive commands without explicit user
+   intent
+3. **Use parameters**: Extract values from task params and incorporate
+   them
 4. **Handle paths**: Use proper quoting for paths with spaces
 5. **Be portable**: Prefer POSIX-compatible commands when possible
 
 **Safety rules:**
 - NEVER run `rm -rf /` or any command that could delete system files
-- NEVER run commands that modify system configuration without explicit request
+- NEVER run commands that modify system configuration without explicit
+  request
 - NEVER expose sensitive information in command output
-- Always use safe defaults (e.g., prefer `rm -i` over `rm -f` for deletions)
+- Always use safe defaults (e.g., prefer `rm -i` over `rm -f` for
+  deletions)
 - For file deletions, prefer moving to trash over permanent deletion
 
 ## Examples
 
 ### Example 1: Simple file creation
 
-Task: { action: "Create a new file called test.txt", type: "execute",
-params: { filename: "test.txt" } }
+Task: {
+  action: "Create a new file called test.txt",
+  type: "execute",
+  params: { filename: "test.txt" }
+}
 
 Response:
 ```
@@ -130,7 +141,10 @@ commands:
 
 ### Example 2: Directory listing
 
-Task: { action: "Show files in the current directory", type: "execute" }
+Task: {
+  action: "Show files in the current directory",
+  type: "execute"
+}
 
 Response:
 ```
@@ -143,8 +157,11 @@ commands:
 ### Example 3: Multiple sequential commands
 
 Tasks:
-- { action: "Create project directory", type: "execute",
-    params: { path: "my-project" } }
+- {
+    action: "Create project directory",
+    type: "execute",
+    params: { path: "my-project" }
+  }
 - { action: "Initialize git repository", type: "execute" }
 - { action: "Create README file", type: "execute" }
 
@@ -164,7 +181,10 @@ commands:
 
 ### Example 4: Install dependencies
 
-Task: { action: "Install dependencies", type: "execute" }
+Task: {
+  action: "Install dependencies",
+  type: "execute"
+}
 
 Response:
 ```
@@ -177,20 +197,30 @@ commands:
 
 ### Example 5: Skill-based execution
 
-When executing from a skill like "Process Data", tasks include params.skill:
+When executing from a skill like "Process Data", tasks include
+params.skill:
 
 Tasks:
-- { action: "Load the sales dataset", type: "execute",
-    params: { skill: "Process Data", source: "sales", format: "json" } }
-- { action: "Transform the sales data", type: "execute",
-    params: { skill: "Process Data", source: "sales", format: "json" } }
-- { action: "Export the results to json", type: "execute",
-    params: { skill: "Process Data", source: "sales", format: "json" } }
+- {
+    action: "Load the sales dataset",
+    type: "execute",
+    params: { skill: "Process Data", source: "sales", format: "json" }
+  }
+- {
+    action: "Transform the sales data",
+    type: "execute",
+    params: { skill: "Process Data", source: "sales", format: "json" }
+  }
+- {
+    action: "Export the results to json",
+    type: "execute",
+    params: { skill: "Process Data", source: "sales", format: "json" }
+  }
 
 The "Process Data" skill's Execution section specifies:
 - Line 1: curl -O https://data.example.com/{SOURCE}.csv
-- Line 2: python3 transform.py --input {SOURCE}.csv --output processed.csv
-- Line 3: csvtool col 1-3 processed.csv > output.{FORMAT}
+- Line 2: python3 transform.py --input {SOURCE}.csv --output data.csv
+- Line 3: csvtool col 1-3 data.csv > output.{FORMAT}
 
 Response (using skill's Execution commands):
 ```
@@ -200,19 +230,23 @@ commands:
     command: "curl -O https://data.example.com/sales.csv"
     timeout: 60000
   - description: "Transform the sales data"
-    command: "python3 transform.py --input sales.csv --output processed.csv"
+    command: "python3 transform.py --input sales.csv --output data.csv"
     timeout: 120000
   - description: "Export the results to json"
-    command: "csvtool col 1-3 processed.csv > output.json"
+    command: "csvtool col 1-3 data.csv > output.json"
 ```
 
-Note: Commands come directly from the skill's Execution section, with {SOURCE}
-replaced by "sales" and {FORMAT} replaced by "json" from task params.
+Note: Commands come directly from the skill's Execution section, with
+{SOURCE} replaced by "sales" and {FORMAT} replaced by "json" from task
+params.
 
 ### Example 6: File operations with paths
 
-Task: { action: "Copy config to backup", type: "execute",
-params: { source: "~/.config/app", destination: "~/.config/app.backup" } }
+Task: {
+  action: "Copy config to backup",
+  type: "execute",
+  params: { source: "~/.config/app", destination: "~/.config/app.backup" }
+}
 
 Response:
 ```
@@ -224,7 +258,10 @@ commands:
 
 ### Example 7: Checking system information
 
-Task: { action: "Check disk space", type: "execute" }
+Task: {
+  action: "Check disk space",
+  type: "execute"
+}
 
 Response:
 ```
@@ -240,11 +277,12 @@ For complex multi-step operations:
 
 1. **Sequential dependencies**: Mark early commands as critical so failure
    stops the chain
-2. **Long-running processes**: Set appropriate timeouts (build processes may
-   need 10+ minutes)
-3. **Working directories**: Use workdir to ensure commands run in the right
-   location
-4. **Error handling**: For non-critical cleanup steps, set critical: false
+2. **Long-running processes**: Set appropriate timeouts (build processes
+   may need 10+ minutes)
+3. **Working directories**: Use workdir to ensure commands run in the
+   right location
+4. **Error handling**: For non-critical cleanup steps, set critical:
+   false
 
 ## Common Mistakes to Avoid