kodu 1.1.13 → 1.1.15

package/src/commands/ops/subcommands/ops-sysinfo.command.ts

@@ -0,0 +1,53 @@
+import { CommandRunner, SubCommand } from 'nest-commander';
+import { ConfigService } from '../../../core/config/config.service';
+import { SshService } from '../../../shared/ssh/ssh.service';
+import {
+  printCliError,
+  printJson,
+  printSshError,
+  resolveServerOrThrow,
+} from '../ops.utils';
+
+@SubCommand({
+  name: 'sysinfo',
+  description: 'Collect remote server diagnostics',
+  arguments: '<alias>',
+})
+export class OpsSysinfoCommand extends CommandRunner {
+  constructor(
+    private readonly configService: ConfigService,
+    private readonly sshService: SshService,
+  ) {
+    super();
+  }
+
+  async run(passedParams: string[]): Promise<void> {
+    const [alias] = passedParams;
+
+    try {
+      const server = await resolveServerOrThrow(
+        this.configService.getConfig(),
+        alias,
+      );
+      const payload = `echo "{"uptime": "$(uptime -p)", "disk_usage": "$(df -h / | tail -1 | awk '{print $5}')", "mem_free": "$(free -m | grep Mem | awk '{print $4}')MB"}"`;
+
+      const result = await this.sshService.execute(server, payload);
+      if (!result.success) {
+        printSshError(result, payload);
+        return;
+      }
+
+      let data: Record<string, string> = {};
+      try {
+        data = JSON.parse(result.stdout) as Record<string, string>;
+      } catch {
+        data = { raw: result.stdout.trim() };
+      }
+
+      printJson({ status: 'ok', data });
+    } catch (error) {
+      printCliError(error);
+      process.exitCode = 1;
+    }
+  }
+}

package/src/commands/pack/pack.command.ts

@@ -124,8 +124,7 @@ export class PackCommand extends CommandRunner {
     const chunks = await Promise.all(
       files.map(async (file) => {
         const content = await this.fsService.readFileRelative(file);
-        const posixPath = file.split(path.sep).join(path.posix.sep);
-        return `// file: ${posixPath}\n${content}`;
+        return `// file: ${file}\n${content}`;
       }),
     );
 

package/src/core/config/config.schema.ts

@@ -73,6 +73,27 @@ const promptsSchema = z
   })
   .optional();
 
+const serverPathsSchema = z
+  .object({
+    apps: z.string().default('/var/agent-apps'),
+    caddy: z.string().optional(),
+  })
+  .optional();
+
+const serverConfigSchema = z.object({
+  host: z.string(),
+  port: z.number().default(22),
+  user: z.string(),
+  sshKeyPath: z.string(),
+  description: z.string().optional(),
+  paths: serverPathsSchema,
+  env: z.record(z.string(), z.string()).optional(),
+});
+
+const opsSchema = z.object({
+  servers: z.record(z.string(), serverConfigSchema),
+});
+
 export const configSchema = z.object({
   $schema: z.string().optional(),
   llm: llmSchema.optional(),
@@ -97,6 +118,8 @@ export const configSchema = z.object({
     contentBasedBinaryDetection: false,
   }),
   prompts: promptsSchema,
+  ops: opsSchema.optional(),
 });
 
 export type KoduConfig = z.infer<typeof configSchema>;
+export type ServerConfig = z.infer<typeof serverConfigSchema>;

package/src/core/file-system/fs.service.ts

@@ -1,5 +1,4 @@
-import type { Stats } from 'node:fs';
-import { promises as fs } from 'node:fs';
+import { promises as fs, type Stats } from 'node:fs';
 import path from 'node:path';
 import { Injectable } from '@nestjs/common';
 import ignore from 'ignore';
@@ -36,27 +35,29 @@ export class FsService {
     const { packer } = this.configService.getConfig();
     const shouldUseGitignore = options.useGitignore ?? packer.useGitignore;
     const gitignorePatterns = shouldUseGitignore
-      ? await this.readGitignorePatterns()
+      ? await this.readIgnoreFile('.gitignore')
       : [];
+    const koduignorePatterns = await this.readIgnoreFile('.koduignore');
+
+    const baseIgnore = options.ignore ?? packer.ignore ?? [];
+    const normalizedBase = this.normalizeIgnorePatterns(baseIgnore);
+    const combinedIgnore = [
+      ...normalizedBase,
+      ...gitignorePatterns,
+      ...koduignorePatterns,
+    ].map((pattern) => pattern.replace(/\\/g, '/'));
 
     const ig = ignore();
-    const rawIgnorePatterns = options.ignore ?? packer.ignore ?? [];
-    const ignorePatterns = rawIgnorePatterns
-      .map((pattern) => pattern.trim())
-      .filter((pattern) => pattern.length > 0)
-      .map((pattern) => pattern.replace(/\\/g, '/'));
-    if (ignorePatterns.length > 0) {
-      ig.add(ignorePatterns);
-    }
-    if (gitignorePatterns.length > 0) {
-      ig.add(gitignorePatterns);
+    if (combinedIgnore.length > 0) {
+      ig.add(combinedIgnore);
     }
 
+    const globIgnore = this.buildGlobIgnorePatterns(combinedIgnore);
     const entries = await glob(['**/*'], {
       onlyFiles: true,
       absolute: true,
       dot: true,
-      ignore: GLOB_IGNORE,
+      ignore: [...GLOB_IGNORE, ...globIgnore],
     });
 
     const relativePaths = entries
@@ -114,22 +115,70 @@ export class FsService {
     return fs.readFile(absolute, 'utf8');
   }
 
-  private async readGitignorePatterns(): Promise<string[]> {
-    const gitignorePath = path.join(process.cwd(), '.gitignore');
+  private toPosixPath(relativePath: string): string {
+    return relativePath.split(path.sep).join(path.posix.sep);
+  }
+
+  private normalizeIgnorePatterns(patterns: string[]): string[] {
+    return patterns
+      .map((pattern) => pattern.trim())
+      .filter((pattern) => pattern.length > 0 && !pattern.startsWith('#'));
+  }
+
+  private buildGlobIgnorePatterns(patterns: string[]): string[] {
+    const normalized = patterns
+      .map((pattern) => pattern.trim())
+      .filter(
+        (pattern) =>
+          pattern.length > 0 &&
+          !pattern.startsWith('#') &&
+          !pattern.startsWith('!'),
+      )
+      .map((pattern) => pattern.replace(/\\/g, '/'));
+
+    const result = new Set<string>();
+
+    for (const pattern of normalized) {
+      const trimmed = pattern.replace(/\/+$/, '');
+      result.add(pattern);
+
+      if (trimmed.length === 0) {
+        continue;
+      }
+
+      if (!pattern.includes('*')) {
+        result.add(`${trimmed}/**`);
+        result.add(`**/${trimmed}/**`);
+      }
+
+      if (!pattern.startsWith('**/')) {
+        result.add(`**/${trimmed}`);
+      }
+
+      if (pattern.endsWith('/')) {
+        result.add(`${trimmed}/**`);
+      }
+    }
+
+    return [...result];
+  }
+
+  private async readIgnoreFile(fileName: string): Promise<string[]> {
+    const target = path.join(process.cwd(), fileName);
 
     try {
-      const content = await fs.readFile(gitignorePath, 'utf8');
-      return content
-        .split(/\r?\n/)
-        .map((line) => line.trim())
-        .filter((line) => line.length > 0 && !line.startsWith('#'));
+      const content = await fs.readFile(target, 'utf8');
+      return this.parseIgnoreContent(content);
     } catch {
       return [];
     }
   }
 
-  private toPosixPath(relativePath: string): string {
-    return relativePath.split(path.sep).join(path.posix.sep);
+  private parseIgnoreContent(content: string): string[] {
+    return content
+      .split(/\r?\n/)
+      .map((line) => line.trim())
+      .filter((line) => line.length > 0 && !line.startsWith('#'));
   }
 
   private isBinaryExtension(relativePath: string): boolean {

package/src/shared/constants.ts

@@ -3,6 +3,7 @@ export const WARNING_TOKEN_THRESHOLD = 12_000;
 export const DEFAULT_COMMIT_TOKENS = 1_500;
 export const DEFAULT_REVIEW_TOKENS = 5_000;
 export const DEFAULT_LLM_MODEL = 'gpt-4o';
+export const DEFAULT_PRICE_PER_MILLION = 5;
 
 const BINARY_EXTENSION_LIST = [
   '.png',

package/src/shared/ssh/ssh.module.ts

@@ -0,0 +1,8 @@
+import { Module } from '@nestjs/common';
+import { SshService } from './ssh.service';
+
+@Module({
+  providers: [SshService],
+  exports: [SshService],
+})
+export class SshModule {}

package/src/shared/ssh/ssh.service.ts

@@ -0,0 +1,61 @@
+import { Injectable } from '@nestjs/common';
+import { execa } from 'execa';
+import type { ServerConfig } from '../../core/config/config.schema';
+
+export type SshResult = {
+  success: boolean;
+  stdout: string;
+  stderr: string;
+  exitCode: number;
+  error?: string;
+};
+
+@Injectable()
+export class SshService {
+  async execute(
+    serverConfig: ServerConfig,
+    command: string,
+  ): Promise<SshResult> {
+    const args = [
+      '-i',
+      serverConfig.sshKeyPath,
+      '-p',
+      String(serverConfig.port ?? 22),
+      '-o',
+      'StrictHostKeyChecking=no',
+      '-o',
+      'ConnectTimeout=10',
+      `${serverConfig.user}@${serverConfig.host}`,
+      command,
+    ];
+
+    try {
+      const { stdout, stderr, exitCode } = await execa('ssh', args, {
+        env: serverConfig.env,
+      });
+
+      return {
+        success: (exitCode ?? 0) === 0,
+        stdout,
+        stderr,
+        exitCode: exitCode ?? 0,
+      };
+    } catch (error) {
+      const failure = error as {
+        stdout?: string;
+        stderr?: string;
+        exitCode?: number;
+        shortMessage?: string;
+        message?: string;
+      };
+
+      return {
+        success: false,
+        stdout: failure.stdout ?? '',
+        stderr: failure.stderr ?? '',
+        exitCode: failure.exitCode ?? -1,
+        error: failure.shortMessage ?? failure.message ?? 'Unknown SSH error',
+      };
+    }
+  }
+}

package/src/shared/tokenizer/tokenizer.service.ts

@@ -1,7 +1,7 @@
 import { Injectable } from '@nestjs/common';
 import { encodingForModel, getEncoding, type TiktokenModel } from 'js-tiktoken';
 import { ConfigService } from '../../core/config/config.service';
-import { DEFAULT_LLM_MODEL } from '../constants';
+import { DEFAULT_LLM_MODEL, DEFAULT_PRICE_PER_MILLION } from '../constants';
 
 type TokenEstimate = {
   tokens: number;
@@ -31,7 +31,7 @@ export class TokenizerService {
     const config = this.configService.getConfig();
     const model = config.llm?.model ?? `openai/${DEFAULT_LLM_MODEL}`;
     const key = this.normalizeModelKey(model);
-    return PRICE_PER_MILLION[key] ?? 0;
+    return PRICE_PER_MILLION[key] ?? DEFAULT_PRICE_PER_MILLION;
   }
 
   private createEncoder() {

package/.cursor/commands/openspec-apply.md

@@ -1,23 +0,0 @@
----
-name: /openspec-apply
-id: openspec-apply
-category: OpenSpec
-description: Implement an approved OpenSpec change and keep tasks in sync.
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-Track these steps as TODOs and complete them one by one.
-1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
-4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
-5. Reference `openspec list` or `openspec show <item>` when additional context is required.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
-<!-- OPENSPEC:END -->

package/.cursor/commands/openspec-archive.md

@@ -1,27 +0,0 @@
----
-name: /openspec-archive
-id: openspec-archive
-category: OpenSpec
-description: Archive a deployed OpenSpec change and update specs.
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-1. Determine the change ID to archive:
-   - If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
-   - If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
-   - Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
-   - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
-2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
-3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
-4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
-5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show <id>` if anything looks off.
-
-**Reference**
-- Use `openspec list` to confirm change IDs before archiving.
-- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
-<!-- OPENSPEC:END -->

package/.cursor/commands/openspec-proposal.md

@@ -1,28 +0,0 @@
----
-name: /openspec-proposal
-id: openspec-proposal
-category: OpenSpec
-description: Scaffold a new OpenSpec change and validate strictly.
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
-- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
-
-**Steps**
-1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.
-3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
-4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
-5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.
-6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
-7. Validate with `openspec validate <id> --strict --no-interactive` and resolve every issue before sharing the proposal.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.
-- Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones.
-- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.
-<!-- OPENSPEC:END -->

package/.windsurf/workflows/openspec-apply.md

@@ -1,21 +0,0 @@
----
-description: Implement an approved OpenSpec change and keep tasks in sync.
-auto_execution_mode: 3
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-Track these steps as TODOs and complete them one by one.
-1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
-4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
-5. Reference `openspec list` or `openspec show <item>` when additional context is required.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
-<!-- OPENSPEC:END -->

package/.windsurf/workflows/openspec-archive.md

@@ -1,25 +0,0 @@
----
-description: Archive a deployed OpenSpec change and update specs.
-auto_execution_mode: 3
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-1. Determine the change ID to archive:
-   - If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
-   - If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
-   - Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
-   - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
-2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
-3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
-4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
-5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show <id>` if anything looks off.
-
-**Reference**
-- Use `openspec list` to confirm change IDs before archiving.
-- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
-<!-- OPENSPEC:END -->

package/.windsurf/workflows/openspec-proposal.md

@@ -1,26 +0,0 @@
----
-description: Scaffold a new OpenSpec change and validate strictly.
-auto_execution_mode: 3
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
-- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
-
-**Steps**
-1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.
-3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
-4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
-5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.
-6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
-7. Validate with `openspec validate <id> --strict --no-interactive` and resolve every issue before sharing the proposal.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.
-- Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones.
-- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.
-<!-- OPENSPEC:END -->