@qelos/aidev 0.5.3 → 0.6.0

package/dist/commands/run.js

@@ -403,16 +403,16 @@ async function checkNeedsClarification(task, config, provider, runners) {
         logger_1.logger.warn('No AI runner available — skipping clarification check');
         return null;
     }
-    const clarificationPrompt = `You are a senior software developer reviewing a task.
-Determine if the following task has enough information to implement without further clarification.
-
-Task name: ${task.name}
-Task description: ${task.description || '(no description)'}
-
-Respond with valid JSON only:
-{
-  "clear": true|false,
-  "question": "question to ask if not clear, or null"
+    const clarificationPrompt = `You are a senior software developer reviewing a task.
+Determine if the following task has enough information to implement without further clarification.
+
+Task name: ${task.name}
+Task description: ${task.description || '(no description)'}
+
+Respond with valid JSON only:
+{
+  "clear": true|false,
+  "question": "question to ask if not clear, or null"
 }`;
     for (const runner of availableRunners) {
         const result = await runner.run(clarificationPrompt);
@@ -440,30 +440,30 @@ Respond with valid JSON only:
     return null;
 }
 function buildConflictResolutionPrompt(task, conflictFiles, context) {
-    return `You are resolving merge conflicts in a software development task branch.
-
-The task branch has fallen behind the base branch and has merge conflicts that need to be resolved.
-
-## Task context (DO NOT break this — the task must still work after conflict resolution)
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
-## Merge conflicts
-
-The following files have merge conflicts with conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...):
-${conflictFiles.map((f) => `- ${f}`).join('\n')}
-
-## Instructions
-
-1. Open each conflicting file and resolve the conflict markers
-2. Keep BOTH the task's changes AND the base branch updates where possible
-3. If the base branch changed something the task also changed, prefer the task's intent but make sure it works with the new base branch code
-4. Remove all conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...)
-5. Make sure the code compiles and is consistent after resolution
+    return `You are resolving merge conflicts in a software development task branch.
+
+The task branch has fallen behind the base branch and has merge conflicts that need to be resolved.
+
+## Task context (DO NOT break this — the task must still work after conflict resolution)
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
+## Merge conflicts
+
+The following files have merge conflicts with conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...):
+${conflictFiles.map((f) => `- ${f}`).join('\n')}
+
+## Instructions
+
+1. Open each conflicting file and resolve the conflict markers
+2. Keep BOTH the task's changes AND the base branch updates where possible
+3. If the base branch changed something the task also changed, prefer the task's intent but make sure it works with the new base branch code
+4. Remove all conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...)
+5. Make sure the code compiles and is consistent after resolution
 6. Do NOT make any changes beyond what is needed to resolve the conflicts`;
 }
 async function resolveConflictsWithAI(task, config, provider, runners, context, hooks, vm, branchName) {
@@ -731,14 +731,14 @@ async function implementTask(task, branchName, branchExists, config, provider, r
     logger_1.logger.success(`Task implemented: branch ${branchName} pushed`);
 }
 function buildImplementPrompt(task, context) {
-    return `You are implementing a software development task. Make the necessary code changes to complete the task described below.
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
+    return `You are implementing a software development task. Make the necessary code changes to complete the task described below.
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
 Please implement the required changes. Focus on correctness and follow the existing code style in the project.`;
 }
 async function analyzeAndPlan(task, context, runners) {
@@ -747,28 +747,28 @@ async function analyzeAndPlan(task, context, runners) {
         logger_1.logger.error('No AI runner available for task analysis');
         return null;
     }
-    const analysisPrompt = `You are a senior software architect breaking down a development task into smaller, sequential implementation steps.
-
-Task name: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
-Analyze this task and break it into smaller, independently implementable sub-tasks that should be executed sequentially. Each sub-task should be a coherent unit of work that can be committed separately.
-
-Respond with valid JSON only — no markdown fences, no extra text:
-{
-  "instructions": "Detailed implementation instructions in markdown covering the full task — architecture decisions, key files to modify, edge cases to handle, testing approach",
-  "subtasks": [
-    {
-      "id": 1,
-      "title": "Short title for the sub-task",
-      "description": "Detailed description of what to implement in this step, including specific files and functions to change"
-    }
-  ]
-}
-
+    const analysisPrompt = `You are a senior software architect breaking down a development task into smaller, sequential implementation steps.
+
+Task name: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
+Analyze this task and break it into smaller, independently implementable sub-tasks that should be executed sequentially. Each sub-task should be a coherent unit of work that can be committed separately.
+
+Respond with valid JSON only — no markdown fences, no extra text:
+{
+  "instructions": "Detailed implementation instructions in markdown covering the full task — architecture decisions, key files to modify, edge cases to handle, testing approach",
+  "subtasks": [
+    {
+      "id": 1,
+      "title": "Short title for the sub-task",
+      "description": "Detailed description of what to implement in this step, including specific files and functions to change"
+    }
+  ]
+}
+
 Keep sub-tasks focused: 2-6 sub-tasks is ideal. Order them by dependency (foundation first).`;
     logger_1.logger.info('Analyzing task and creating implementation plan...');
     const result = await runner.run(analysisPrompt);
@@ -820,31 +820,31 @@ async function splitFailedSubtask(parentTask, plan, failedSubtask, runners) {
     const diagnostics = failedSubtask.lastError && failedSubtask.lastError !== '__git__'
         ? failedSubtask.lastError
         : '(no diagnostics captured)';
-    const splitPrompt = `You are a senior software architect helping recover a stalled implementation step by splitting it into exactly two smaller, sequential sub-tasks.
-
-Overall task: ${parentTask.name}
-${parentTask.description ? `\nTask description:\n${parentTask.description}\n` : ''}
-## Surrounding plan
-${siblings || '(no sibling sub-tasks)'}
-
-## Failed sub-task
-ID: ${formatSubtaskId(failedSubtask.id)}
-Title: ${failedSubtask.title}
-Description: ${failedSubtask.description}
-
-## Previous failure diagnostics
-${diagnostics}
-
-Split the failed sub-task above into exactly two smaller, independently implementable sub-tasks that together achieve the original goal. Each new sub-task should be a coherent unit of work that can be committed separately, ordered by dependency (foundation first). Take the diagnostics into account so the split actually addresses what broke.
-
-Respond with valid JSON only — no markdown fences, no extra text:
-{
-  "subtasks": [
-    { "title": "Short title for the first new sub-task", "description": "Detailed description of what to implement in this step" },
-    { "title": "Short title for the second new sub-task", "description": "Detailed description of what to implement in this step" }
-  ]
-}
-
+    const splitPrompt = `You are a senior software architect helping recover a stalled implementation step by splitting it into exactly two smaller, sequential sub-tasks.
+
+Overall task: ${parentTask.name}
+${parentTask.description ? `\nTask description:\n${parentTask.description}\n` : ''}
+## Surrounding plan
+${siblings || '(no sibling sub-tasks)'}
+
+## Failed sub-task
+ID: ${formatSubtaskId(failedSubtask.id)}
+Title: ${failedSubtask.title}
+Description: ${failedSubtask.description}
+
+## Previous failure diagnostics
+${diagnostics}
+
+Split the failed sub-task above into exactly two smaller, independently implementable sub-tasks that together achieve the original goal. Each new sub-task should be a coherent unit of work that can be committed separately, ordered by dependency (foundation first). Take the diagnostics into account so the split actually addresses what broke.
+
+Respond with valid JSON only — no markdown fences, no extra text:
+{
+  "subtasks": [
+    { "title": "Short title for the first new sub-task", "description": "Detailed description of what to implement in this step" },
+    { "title": "Short title for the second new sub-task", "description": "Detailed description of what to implement in this step" }
+  ]
+}
+
 Exactly two entries — no more, no fewer.`;
     logger_1.logger.info(`Splitting failed sub-task ${formatSubtaskId(failedSubtask.id)} into two smaller steps...`);
     const result = await runner.run(splitPrompt);
@@ -899,20 +899,20 @@ async function executeSubTask(subtask, task, plan, config, runners, reviewContex
     const retrySection = previousError && previousError !== '__git__'
         ? `\n## Previous attempt failure diagnostics\nThis step failed on a previous attempt. Diagnostics below — please take them into account and avoid repeating the same failure.\n\n${previousError}\n`
         : '';
-    const prompt = `You are implementing step ${subtask.id} of a multi-step task.
-
-Overall task: ${task.name}
-${task.description ? `\nTask description:\n${task.description}` : ''}
-
-## Full implementation instructions
-${instructions}
-${reviewContext || ''}${retrySection}
-## Progress
-${completedSteps || '(no steps completed yet)'}
-
-## Current step: ${subtask.id}. ${subtask.title}
-${subtask.description}
-
+    const prompt = `You are implementing step ${subtask.id} of a multi-step task.
+
+Overall task: ${task.name}
+${task.description ? `\nTask description:\n${task.description}` : ''}
+
+## Full implementation instructions
+${instructions}
+${reviewContext || ''}${retrySection}
+## Progress
+${completedSteps || '(no steps completed yet)'}
+
+## Current step: ${subtask.id}. ${subtask.title}
+${subtask.description}
+
 Implement ONLY this step. Focus on correctness and follow the existing code style.`;
     let implemented = false;
     let previousNotes = '';
@@ -1191,29 +1191,29 @@ function buildCompletionComment(branch, prUrl, config) {
 function buildNonCodePrompt(task, context) {
     const hasComments = context.trim().length > 0;
     if (hasComments) {
-        return `Task: ${task.name}
-
-Original description:
-${task.description || '(no description provided)'}
-${context}
-
-⚠️ CRITICAL: This is a FOLLOW-UP request. The conversation above contains new comments from the user.
-YOUR PRIMARY TASK is to address the LATEST comment at the bottom of the conversation - this is the user's current request.
-The latest comment may:
-- Ask for something completely different from the original task
-- Request modifications to what was already done
-- Add new requirements
-
-DO NOT repeat what was already done. DO NOT re-execute the original task unless explicitly asked.
-Focus ENTIRELY on addressing the latest comment as your main instruction.
-
+        return `Task: ${task.name}
+
+Original description:
+${task.description || '(no description provided)'}
+${context}
+
+⚠️ CRITICAL: This is a FOLLOW-UP request. The conversation above contains new comments from the user.
+YOUR PRIMARY TASK is to address the LATEST comment at the bottom of the conversation - this is the user's current request.
+The latest comment may:
+- Ask for something completely different from the original task
+- Request modifications to what was already done
+- Add new requirements
+
+DO NOT repeat what was already done. DO NOT re-execute the original task unless explicitly asked.
+Focus ENTIRELY on addressing the latest comment as your main instruction.
+
 Please provide a clear, detailed response to the LATEST comment. Your response will be posted as a comment on the task ticket, so write it as a direct answer or explanation addressed to the person who wrote the latest comment.`;
     }
-    return `Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-
+    return `Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+
 Please provide a clear, detailed response to this task. Your response will be posted as a comment on the task ticket, so write it as a direct answer or explanation addressed to the person who created the task.`;
 }
 function buildNonCodeCompletionComment(config, agentResponse) {
@@ -1523,22 +1523,22 @@ async function implementReviewTask(task, branchName, config, provider, runners,
     logger_1.logger.success(`Review comments addressed for: ${task.name}`);
 }
 function buildReviewPrompt(task, threads) {
-    let prompt = `You are addressing code review comments on a pull request for a software development task.
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-
-## Unresolved Code Review Threads
-
-The following review threads need to be addressed. For each thread, either:
-- Fix the code as requested (make the changes directly in the files)
-- Or, if it's a discussion/question that doesn't require code changes, output a REPLY block:
-  <!-- AIDEV-REPLY thread_id -->Your reply here<!-- /AIDEV-REPLY -->
-
-Replace "thread_id" with the actual thread ID shown below.
-
+    let prompt = `You are addressing code review comments on a pull request for a software development task.
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+
+## Unresolved Code Review Threads
+
+The following review threads need to be addressed. For each thread, either:
+- Fix the code as requested (make the changes directly in the files)
+- Or, if it's a discussion/question that doesn't require code changes, output a REPLY block:
+  <!-- AIDEV-REPLY thread_id -->Your reply here<!-- /AIDEV-REPLY -->
+
+Replace "thread_id" with the actual thread ID shown below.
+
 `;
     for (const thread of threads) {
         const location = thread.line
@@ -1550,12 +1550,12 @@ Replace "thread_id" with the actual thread ID shown below.
         }
         prompt += '\n';
     }
-    prompt += `## Instructions
-
-1. Read each review thread carefully
-2. For code change requests: make the fix directly in the relevant file(s)
-3. For questions or discussions: output a REPLY block with a clear, helpful response
-4. You may handle multiple threads — some with code fixes, others with replies
+    prompt += `## Instructions
+
+1. Read each review thread carefully
+2. For code change requests: make the fix directly in the relevant file(s)
+3. For questions or discussions: output a REPLY block with a clear, helpful response
+4. You may handle multiple threads — some with code fixes, others with replies
 5. Focus on correctness and follow the existing code style`;
     return prompt;
 }

package/dist/commands/schedule.d.ts

@@ -1,4 +1,17 @@
-export declare function buildUnixCronLine(cronExpr: string, cwd: string, nodeBin: string, aidevBin: string): string;
+/**
+ * Quotes an arg for embedding inside a single-quoted shell command
+ * (e.g. inside `zsh -c '…'`). Inside the outer single quotes the inner
+ * string is parsed as shell, so we use double quotes and escape `\ $ ` "`.
+ * Single quotes are not supported (would close the outer quote).
+ */
+export declare function shQuoteForCron(s: string): string;
+/** Tokenises a shell-style arg string we generated (unquoted or double-quoted). */
+export declare function tokenizeShellArgs(s: string): string[];
+/** Quotes an arg for embedding into a Windows schtasks /tr command string. */
+export declare function cmdQuoteForSchtasks(s: string): string;
+export declare function buildUnixCronLine(cronExpr: string, cwd: string, nodeBin: string, aidevBin: string, extraArgs?: string[]): string;
+/** Extracts the extra args (after `aidev run`) from an existing cron line. */
+export declare function extractUnixCronArgs(line: string): string[];
 export type LaunchdSchedule = {
     key: 'StartInterval';
     seconds: number;
@@ -12,7 +25,9 @@ export type LaunchdSchedule = {
  * Supports the same subset as cronToSchtasksArgs.
  */
 export declare function cronToLaunchdSchedule(cron: string): LaunchdSchedule | null;
-export declare function buildLaunchAgentPlist(label: string, nodeBin: string, aidevBin: string, cwd: string, schedule: LaunchdSchedule): string;
+export declare function buildLaunchAgentPlist(label: string, nodeBin: string, aidevBin: string, cwd: string, schedule: LaunchdSchedule, extraArgs?: string[]): string;
+/** Extracts the user-supplied extra args from an existing LaunchAgent plist. */
+export declare function extractLaunchAgentArgs(xml: string): string[];
 /**
  * Converts a cron expression to schtasks /sc + /mo + /st arguments.
  * Supports the subset used by the preset list.
@@ -22,7 +37,7 @@ export declare function cronToSchtasksArgs(cron: string): string[] | null;
 export declare function windowsTaskName(cwd: string, cronExpr?: string): string;
 /** Extracts the launchd schedule object from a plist XML string. */
 export declare function extractLaunchdSchedule(xml: string): LaunchdSchedule | null;
-export declare function scheduleSetCommand(cronExpr?: string): Promise<void>;
+export declare function scheduleSetCommand(cronExpr?: string, extraArgs?: string[]): Promise<void>;
 export declare function scheduleGetCommand(): Promise<void>;
 export declare function scheduleRemoveCommand(id?: number): Promise<void>;
 export declare function scheduleFixCommand(): void;

package/dist/commands/schedule.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"schedule.d.ts","sourceRoot":"","sources":["../../src/commands/schedule.ts"],"names":[],"mappings":"AA4DA,wBAAgB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CAG1G;AAoJD,MAAM,MAAM,eAAe,GACvB;IAAE,GAAG,EAAE,eAAe,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GACzC;IAAE,GAAG,EAAE,uBAAuB,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC;AAEnE;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,MAAM,GAAG,eAAe,GAAG,IAAI,CAiB1E;AAED,wBAAgB,qBAAqB,CACnC,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,EACX,QAAQ,EAAE,eAAe,GACxB,MAAM,CAiDR;AAsKD;;;GAGG;AACH,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,IAAI,CAiBhE;AAED,wFAAwF;AACxF,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,MAAM,CAKtE;AAqID,oEAAoE;AACpE,wBAAgB,sBAAsB,CAAC,GAAG,EAAE,MAAM,GAAG,eAAe,GAAG,IAAI,CAc1E;AAkFD,wBAAsB,kBAAkB,CAAC,QAAQ,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAKzE;AAED,wBAAsB,kBAAkB,IAAI,OAAO,CAAC,IAAI,CAAC,CAIxD;AAED,wBAAsB,qBAAqB,CAAC,EAAE,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAItE;AAED,wBAAgB,kBAAkB,IAAI,IAAI,CAIzC"}
+{"version":3,"file":"schedule.d.ts","sourceRoot":"","sources":["../../src/commands/schedule.ts"],"names":[],"mappings":"AAgDA;;;;;GAKG;AACH,wBAAgB,cAAc,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,CAMhD;AAED,mFAAmF;AACnF,wBAAgB,iBAAiB,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,EAAE,CAYrD;AAED,8EAA8E;AAC9E,wBAAgB,mBAAmB,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,CAGrD;AAgBD,wBAAgB,iBAAiB,CAC/B,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,EACX,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,MAAM,EAChB,SAAS,GAAE,MAAM,EAAO,GACvB,MAAM,CAIR;AAED,8EAA8E;AAC9E,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,CAM1D;AAiKD,MAAM,MAAM,eAAe,GACvB;IAAE,GAAG,EAAE,eAAe,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GACzC;IAAE,GAAG,EAAE,uBAAuB,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC;AAEnE;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,MAAM,GAAG,eAAe,GAAG,IAAI,CAiB1E;AAED,wBAAgB,qBAAqB,CACnC,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,EACX,QAAQ,EAAE,eAAe,EACzB,SAAS,GAAE,MAAM,EAAO,GACvB,MAAM,CAkDR;AAiDD,gFAAgF;AAChF,wBAAgB,sBAAsB,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,EAAE,CAO5D;AA2HD;;;GAGG;AACH,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,IAAI,CAiBhE;AAED,wFAAwF;AACxF,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,MAAM,CAKtE;AAsID,oEAAoE;AACpE,wBAAgB,sBAAsB,CAAC,GAAG,EAAE,MAAM,GAAG,eAAe,GAAG,IAAI,CAc1E;AAkFD,wBAAsB,kBAAkB,CAAC,QAAQ,CAAC,EAAE,MAAM,EAAE,SAAS,GAAE,MAAM,EAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAKnG;AAED,wBAAsB,kBAAkB,IAAI,OAAO,CAAC,IAAI,CAAC,CAIxD;AAED,wBAAsB,qBAAqB,CAAC,EAAE,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAItE;AAED,wBAAgB,kBAAkB,IAAI,IAAI,CAIzC"}