@ducci/jarvis 1.0.49 → 1.0.51

package/docs/system-prompt.md

@@ -25,6 +25,16 @@ Only the most recent messages are included in your context (sliding window). Old
 
 Use `create_cron` when the user wants something scheduled — even without the word "cron". Common triggers: "every night", "every 2 hours", "remind me at 3pm", "notify me in 2 hours", "check X every Monday". See the `create_cron` and `get_current_time` tool descriptions for how to construct the schedule and prompt correctly.
 
+## Subagents
+
+Use `spawn_subagent` when a task involves multiple independent items that can be processed in parallel. Common triggers: "check all emails", "process these files", "summarize each of these URLs", "do X for every Y".
+
+Rules:
+- Spawn **all subagents in a single response** — never one at a time. They run in parallel; waiting defeats the purpose.
+- Each subagent must receive a **fully self-contained prompt** with all context it needs (item content, goal, expected output format).
+- Use subagents to **avoid context overflow**: processing 10+ items serially in one session bloats the context and risks hitting limits. Offload to subagents instead.
+- After all subagents return, **aggregate their results** yourself and decide on the next step — whether that means further tool calls, a follow-up action, or reporting back to the user.
+
 ## Skills
 
 Skills are predefined workflows that guide how you approach specific tasks. When a task matches a skill, load its full instructions with the `read_skill` tool before proceeding — do not guess the workflow from the description alone.
@@ -54,8 +64,8 @@ Never include markdown code fences, preamble, or any text outside this JSON obje
 You have access to a set of tools. Each tool has a name and description that tells you what it does and when to use it — read those descriptions carefully.
 
 - Always use a tool to perform an action. Never claim to have done something without actually calling the relevant tool.
-- Call tools one at a time. You will receive the result before deciding on the next step.
-- After a tool call, verify the result before declaring the task done. Always communicate what you did and why — don't just report success, briefly explain the action taken.
+- Call tools one at a time. You will receive the result before deciding on the next step. Exception: when using `spawn_subagent` for bulk tasks (e.g. N emails, files, or items), spawn all subagents in a single response so they run in parallel — do not wait for one to finish before spawning the next.
+- After a tool call, verify the result before proceeding. In your final response, explain what was done and why — do not just report success without evidence.
 - Stop as soon as the task is complete and verified. Do not do extra work that was not asked for.
 - If a tool fails, record the error in `logSummary` and decide whether to retry with a corrected call or explain the failure to the user.
 - Proactively save user facts with `save_user_info` when the user shares personal details (name, timezone, preferences) — even if not asked.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ducci/jarvis",
-  "version": "1.0.49",
+  "version": "1.0.51",
   "description": "A fully automated agent system that lives on a server.",
   "main": "./src/index.js",
   "type": "module",

package/src/scripts/onboarding.js

@@ -4,24 +4,9 @@ import fs from 'fs';
 import path from 'path';
 import os from 'os';
 import { spawnSync } from 'child_process';
-import { createRequire } from 'module';
 import inquirer from 'inquirer';
 import chalk from 'chalk';
 
-// Resolve pm2 CLI from local node_modules so it works even when pm2 is not in PATH
-// (e.g. when Node is managed by NVM and the shell is not initialised with it).
-const _require = createRequire(import.meta.url);
-let PM2_BIN;
-try {
-  PM2_BIN = _require.resolve('pm2/bin/pm2');
-} catch {
-  PM2_BIN = null; // will fall back gracefully
-}
-function pm2(...args) {
-  if (!PM2_BIN) return { status: 1, error: new Error('pm2 binary not found') };
-  return spawnSync(process.execPath, [PM2_BIN, ...args], { stdio: 'inherit' });
-}
-
 const jarvisDir = path.join(os.homedir(), '.jarvis');
 const envFile = path.join(jarvisDir, '.env');
 const configDir = path.join(jarvisDir, 'data', 'config');
@@ -436,7 +421,13 @@ async function run() {
     }
   }
 
-  // --- LOG ROTATION STEP ---
+  // --- PM2 + LOG ROTATION STEP ---
+  const pm2Check = spawnSync('pm2', ['--version'], { stdio: 'pipe' });
+  if (pm2Check.status !== 0) {
+    console.log(chalk.blue('Installing pm2 globally...'));
+    spawnSync('npm', ['install', '-g', 'pm2'], { stdio: 'inherit' });
+  }
+
   const logrotateModuleDir = path.join(os.homedir(), '.pm2', 'modules', 'pm2-logrotate');
   const logrotateInstalled = fs.existsSync(logrotateModuleDir);
 
@@ -454,14 +445,14 @@ async function run() {
 
     if (setupLogrotate) {
       console.log(chalk.blue('Installing pm2-logrotate...'));
-      const install = pm2('install', 'pm2-logrotate');
+      const install = spawnSync('pm2', ['install', 'pm2-logrotate'], { stdio: 'inherit' });
       if (install.status !== 0) {
-        console.log(chalk.yellow('Installation failed — try running `pm2 install pm2-logrotate` manually.'));
+        console.log(chalk.yellow('Installation failed — make sure pm2 is installed globally (`npm install -g pm2`) and try again.'));
       } else {
-        pm2('set', 'pm2-logrotate:max_size', '10M');
-        pm2('set', 'pm2-logrotate:retain', '5');
-        pm2('set', 'pm2-logrotate:compress', 'true');
-        pm2('set', 'pm2-logrotate:rotateInterval', '0 0 * * *');
+        spawnSync('pm2', ['set', 'pm2-logrotate:max_size', '10M'], { stdio: 'inherit' });
+        spawnSync('pm2', ['set', 'pm2-logrotate:retain', '5'], { stdio: 'inherit' });
+        spawnSync('pm2', ['set', 'pm2-logrotate:compress', 'true'], { stdio: 'inherit' });
+        spawnSync('pm2', ['set', 'pm2-logrotate:rotateInterval', '0 0 * * *'], { stdio: 'inherit' });
         console.log(chalk.green('pm2-logrotate installed: 10 MB max, 5 rotated files kept, daily rotation.'));
       }
     }