@whoz-oss/coday-server 0.53.1 → 0.54.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whoz-oss/coday-server",
-  "version": "0.53.1",
+  "version": "0.54.0",
   "repository": "https://github.com/whoz-oss/coday",
   "type": "module",
   "main": "server/server.js",

package/server.js

@@ -793,7 +793,174 @@ You deemed the task completed by not delegating another task, so:
       It should not be generic knowledge and neither a perfect copy on a file, but rather from a paragraph up to a 3 pages document.
       If unsure or lacking clarity, use the available tools to test or request guidance.
       Format it in markdown.
-      Then memorize it, each subject at a time.`]}];var ax=class extends De{constructor(t){super({commandWord:"file",description:"Loads a file by its path relative to project root, ex: `load-file ./folder/file.extension`"});this.interactor=t}async handle(t,n){let a=this.getSubCommand(t).trim();if(!a)return this.interactor.error("Please provide a valid file path."),n;a.startsWith(".")||(a=`.${a}`);let s=await Cie({relPath:a,root:n.project.root,interactor:this.interactor});return n.aiThread?.addUserMessage(n.username,{type:"text",content:`File with path: ${a}
+      Then memorize it, each subject at a time.`]},{name:"plan",description:"Create a detailed execution plan before starting complex tasks. Research context, ask clarifying questions, and generate structured plan.",commands:[`@ Create a comprehensive execution plan for the following task:
+
+PROMPT
+
+## Phase 1: Research & Understanding
+
+1. **Analyze the request** to identify:
+   - Core requirements and objectives
+   - Implicit assumptions or expectations
+   - Technical scope and constraints
+
+2. **Research relevant context** using available tools:
+   - Use whatever tools you have available (file reading, API calls, search, etc.)
+   - Gather information about existing patterns, structures, and conventions
+   - Identify relevant files, modules, or resources
+   - Document key findings briefly
+
+3. **Assess feasibility**:
+   - Identify potential challenges or blockers
+   - Note any dependencies or prerequisites
+   - Consider alternative approaches if applicable
+
+Do not assume you have specific tools - use what's available to you.`,`@ Continue with Phase 2: Clarifying Questions
+
+Based on your research and understanding:
+
+1. **Identify ambiguities** or missing information that could impact the plan
+
+2. **Ask focused questions** if clarification is needed:
+   - Use the 'invite' or 'choice' tools for user input
+   - Keep questions concise and specific
+   - Prioritize questions that significantly impact the approach
+
+3. **Skip this phase** if the requirements are clear enough to proceed
+
+Remember: Only ask questions that are truly necessary for creating a solid plan.`,`@ Complete Phase 3: Plan Creation
+
+Now create a detailed execution plan and save it to exchange://execution-plan.md
+
+The plan must follow this Markdown structure:
+
+# Execution Plan: [Task Title]
+
+## Overview
+1-2 sentence summary of what will be accomplished.
+
+## Context
+Key information and constraints identified during research:
+- Relevant patterns/conventions found
+- Technical constraints
+- Dependencies or prerequisites
+- Key files/resources involved
+
+## Steps
+
+### Step 1: [Step Title]
+- **Resources to modify**: List files, APIs, or resources
+- **Changes**: Specific modifications to make
+- **Validation**: How to verify this step (compile, test, manual check)
+- **Dependencies**: Which previous steps must complete first (or "None")
+
+### Step 2: [Step Title]
+[Same structure as Step 1]
+
+[Continue for all steps...]
+
+## Verification
+How to test the complete implementation:
+1. Compilation checks
+2. Automated tests
+3. Manual verification steps
+
+## Risks & Considerations
+- Potential issues or edge cases
+- Alternative approaches considered
+- Technical debt or future improvements
+
+---
+
+After saving the plan:
+1. Inform the user that the plan is ready
+2. Mention it can be reviewed with: load exchange://execution-plan.md
+3. Mention it can be edited manually or via agent assistance
+4. Mention it can be executed with: execute-plan`]},{name:"execute-plan",description:"Execute a previously created plan step by step, with validation and progress tracking.",commands:[`@ Execute the plan from exchange://execution-plan.md
+
+## Important Notes
+- The plan file may have been edited by the user since creation
+- Always read the current version from exchange://execution-plan.md
+- Respect the plan structure and order unless issues arise
+
+## Execution Protocol
+
+### 1. Load and Parse the Plan
+- Read the plan from exchange://execution-plan.md
+- Parse the structure to understand:
+  - Overall objective
+  - Context and constraints
+  - Ordered steps with dependencies
+  - Validation criteria
+
+### 2. Pre-execution Check
+- Review the plan overview and context
+- Verify prerequisites are met
+- Identify any obvious issues with the plan
+- If significant issues found, report them and ask for guidance
+
+### 3. Step-by-Step Execution
+For each step in order:
+
+a) **Announce the step**:
+   - State which step you're starting
+   - Briefly explain what will be done
+
+b) **Check dependencies**:
+   - Verify required previous steps completed successfully
+   - If dependencies not met, report and stop
+
+c) **Execute the changes**:
+   - Make the specified modifications
+   - Follow the plan's guidance
+   - If plan lacks details, use best judgment based on context
+
+d) **Validate the step**:
+   - Run specified validation (compile, test, etc.)
+   - Verify changes work as expected
+   - Report any issues immediately
+
+e) **Optional confirmation** (for complex/risky steps):
+   - For steps that modify critical files or have significant impact
+   - Ask user confirmation before proceeding to next step
+   - Use 'choice' tool for quick yes/no
+
+f) **Report completion**:
+   - Confirm step completed successfully
+   - Note any deviations from the plan
+   - Proceed to next step
+
+### 4. Handle Issues
+If a step fails:
+- Report the specific issue clearly
+- Explain what went wrong
+- Suggest potential solutions:
+  - Retry with adjustments
+  - Skip and continue (if non-critical)
+  - Stop and ask for guidance
+- Use 'choice' tool to ask user how to proceed
+
+### 5. Final Verification
+After all steps complete:
+- Run final validation checks from the plan
+- Test the complete implementation
+- Verify all objectives met
+
+### 6. Summary Report
+Provide a comprehensive summary:
+- What was accomplished
+- List of changes made (files modified, features added, etc.)
+- Any deviations from the original plan and why
+- Validation results (tests passed, compilation successful, etc.)
+- Known issues or limitations
+- Suggested next steps or follow-ups
+
+## Execution Guidelines
+- Be methodical and thorough
+- Validate frequently to catch issues early
+- Communicate progress clearly
+- Don't hesitate to ask for guidance if plan is unclear
+- Respect the plan but adapt if circumstances require it`]}];var ax=class extends De{constructor(t){super({commandWord:"file",description:"Loads a file by its path relative to project root, ex: `load-file ./folder/file.extension`"});this.interactor=t}async handle(t,n){let a=this.getSubCommand(t).trim();if(!a)return this.interactor.error("Please provide a valid file path."),n;a.startsWith(".")||(a=`.${a}`);let s=await Cie({relPath:a,root:n.project.root,interactor:this.interactor});return n.aiThread?.addUserMessage(n.username,{type:"text",content:`File with path: ${a}
 
 ${s}`}),n}};import*as y4 from"fs";import*as jo from"path";var UJe=(r,e)=>{let t=jo.resolve(e),n=jo.resolve(t,r),i=jo.normalize(t),a=jo.normalize(n);if(!a.startsWith(i+jo.sep)&&a!==i)throw new Error(`Attempt to navigate outside the root folder: ${r} is not allowed`);return n},HJe=async r=>{try{if(!(await y4.promises.stat(r)).isDirectory())throw new Error(`Symbolic link target is not a directory: ${r}`)}catch(e){throw e.code==="ENOENT"?new Error(`Symbolic link target does not exist: ${r}`):e}},WJe=async r=>{let e;try{e=await y4.promises.lstat(r)}catch(t){throw t.code==="ENOENT"?new Error(`Directory does not exist: ${r}`):new Error(`Cannot access path ${r}: ${t.message}`)}if(e.isSymbolicLink())await HJe(r);else if(!e.isDirectory())throw new Error(`Path is not a directory: ${r}`)},GJe=async(r,e)=>{try{return(await y4.promises.lstat(r)).isDirectory()?`${e}/`:e}catch{return`${e} (inaccessible)`}},sx=async({relPath:r,root:e})=>{let t=UJe(r,e);await WJe(t);let n=await y4.promises.readdir(t);return await Promise.all(n.map(a=>{let s=jo.join(t,a);return GJe(s,a)}))};var ox=class extends De{constructor(t){super({commandWord:"folder",description:"Loads files from a folder, does not do depth nor recursive."});this.interactor=t}async handle(t,n){let i=this.getSubCommand(t);if(!i)return this.interactor.error("Please provide a valid folder path."),n;i.startsWith(".")||(i=`.${i}`);let a;try{a=await sx({relPath:i,root:n.project.root});let s=a.filter(o=>!o.endsWith("/")).map(o=>`load file ${i}/${o}`);n.addCommands(...s),this.interactor.displayText(`Folder loaded: ${i}`)}catch(s){this.interactor.error(`Failed to load folder: ${s}`)}return n}};var cx=class extends Sn{constructor(e){super({commandWord:"load",description:"handles load related commands"},e),this.handlers=[new ax(e),new ox(e)]}};var lx=class extends De{constructor(t,n){super({commandWord:"agents",description:"Show agent usage statistics sorted by number of calls. Use --from=YYYY-MM-DD and --to=YYYY-MM-DD for custom date range (default: last 7 days)"});this.interactor=t;this.services=n}async handle(t,n){try{let i=this.getSubCommand(t),a=at(i,[{key:"from",alias:"f"},{key:"to",alias:"t"}]),s,o;if(a.to&&typeof a.to=="string"){let d=this.parseDate(a.to);if(!d)return this.interactor.error("Invalid --to date format. Please use YYYY-MM-DD"),n;s=d,s.setHours(23,59,59,999)}else s=new Date,s.setHours(23,59,59,999);if(a.from&&typeof a.from=="string"){let d=this.parseDate(a.from);if(!d)return this.interactor.error("Invalid --from date format. Please use YYYY-MM-DD"),n;o=d,o.setHours(0,0,0,0)}else o=new Date(s),o.setDate(o.getDate()-7),o.setHours(0,0,0,0);if(o>s)return this.interactor.error("Invalid date range: --from date must be before --to date"),n;let c=(await this.services.logger.readLogs(o,s)).filter(d=>!d.type||d.type==="AGENT_USAGE");if(c.length===0){let d=this.formatDateRange(o,s);return this.interactor.displayText(`\u{1F4CA} No usage data found for ${d}`),n}let l=new Map;for(let d of c){let p=l.get(d.agent)||{calls:0,totalCost:0};l.set(d.agent,{calls:p.calls+1,totalCost:p.totalCost+d.cost})}let u=Array.from(l.entries()).map(([d,p])=>({agent:d,calls:p.calls,totalCost:p.totalCost,avgCost:p.totalCost/p.calls}));u.sort((d,p)=>p.calls-d.calls);let f=this.formatAgentStats(u,o,s);this.interactor.displayText(f)}catch(i){this.interactor.error(`Failed to retrieve agent statistics: ${i}`)}return n}parseDate(t){if(!t.match(/^(\d{4})-(\d{2})-(\d{2})$/))return null;let i=new Date(t);return isNaN(i.getTime())?null:i}formatDateRange(t,n){let i=t.toISOString().split("T")[0],a=n.toISOString().split("T")[0];return`${i} to ${a}`}formatAgentStats(t,n,i){let s=`\u{1F4CA} Agent Usage Statistics (${this.formatDateRange(n,i)})
 =====================================