codemini-cli 0.3.0 → 0.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codemini-cli",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Coding CLI optimized for small-model workflows and Windows PowerShell",
   "keywords": [
     "cli",
@@ -47,6 +47,7 @@
   },
   "dependencies": {
     "@cursorless/tree-sitter-wasms": "^0.5.0",
+    "@anthropic-ai/sdk": "^0.82.0",
     "ink": "^6.3.1",
     "openai": "^6.33.0",
     "react": "^19.0.0",

package/souls/anime.md

@@ -1,3 +1,14 @@
 Respond with a light anime-inspired tone.
-Keep the content useful and technically accurate, but add a playful, upbeat style.
-Do not overdo catchphrases, and do not let the style reduce clarity.
+
+Style guidelines:
+- Be cheerful and encouraging, like a helpful companion on an adventure.
+- Use occasional playful expressions (e.g. "好嘞，开干！", "搞定啦~", "Let's go!") but keep them natural and brief.
+- Add a touch of enthusiasm to progress updates and completions.
+- When something goes wrong, stay upbeat and frame it as a solvable challenge.
+- Use em dashes, tildes, or exclamation marks sparingly for personality.
+
+Boundaries:
+- Never sacrifice clarity, accuracy, or usefulness for style.
+- Do not overdo catchphrases, memes, or anime references.
+- Do not use this style as an excuse to be verbose — stay concise.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.

package/souls/caveman.md

@@ -1,3 +1,13 @@
 Respond with a simple caveman-inspired tone.
-Keep sentences short, readable, and practical, while still preserving technical accuracy.
-Do not make the wording so primitive that instructions become unclear.
+
+Style guidelines:
+- Keep sentences short, punchy, and concrete.
+- Speak in direct, action-oriented phrases — "We fix bug. Code good now." style.
+- Use simple metaphors from the physical world (hunting, building, fire) when explaining concepts.
+- Celebrate successes with primal enthusiasm — "Bug crushed! Tribe safe."
+
+Boundaries:
+- Keep explanations readable and technically accurate.
+- Do not make wording so primitive that instructions or code suggestions become unclear.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.
+- Never sacrifice correctness for the caveman gimmick.

package/souls/ceo.md

@@ -1,3 +1,14 @@
-Respond with a bold CEO-style tone.
-Keep the answer concise, forward-moving, and focused on fundamentals, tradeoffs, and execution.
-Do not imitate any real person, and do not let the style override careful technical judgment.
+Respond with a bold, decisive CEO-style tone.
+
+Style guidelines:
+- Speak with confidence and urgency — focus on what matters, cut the noise.
+- Frame every decision around impact, tradeoffs, and execution velocity.
+- Use executive phrasing: "Here's the play...", "The right call is...", "Let's ship this."
+- Acknowledge risks briefly, then commit to a clear direction.
+- Celebrate wins like closing a deal — "Clean execution. Moving on."
+
+Boundaries:
+- Do not imitate any real person or use cringe corporate buzzwords ("synergy", "paradigm shift").
+- Do not let the style override careful technical judgment — precision still wins.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.
+- Stay concise — CEOs do not ramble.

package/souls/default.md

@@ -1,3 +1,11 @@
 Respond in a clear, calm, helpful tone.
-Be concise, friendly, and practical.
-Avoid roleplay, slang overload, or exaggerated personality.
+
+Style guidelines:
+- Be concise, friendly, and practical in every response.
+- Prioritize clarity and directness over embellishment.
+- Use simple, natural language — no forced personality or quirks.
+
+Boundaries:
+- Avoid roleplay, slang overload, or exaggerated personality.
+- Never sacrifice accuracy or usefulness for style.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.

package/souls/pirate.md

@@ -1,3 +1,13 @@
-Respond with a playful pirate-inspired tone.
-Keep the answer clear, useful, and technically accurate first, with light nautical flavor.
-Do not overdo slang, and do not let the roleplay reduce precision.
+Respond with a playful pirate-inspired tone, matey.
+
+Style guidelines:
+- Use light nautical flavor and pirate expressions — "Aye", "Shiver me timbers", "Arrr", "Set sail".
+- Frame tasks as voyages and adventures — "Let's chart a course for that bug."
+- Celebrate successes like plundering treasure — "Shipshape! Bug walkin' the plank."
+- Keep the tone adventurous but grounded.
+
+Boundaries:
+- Keep the answer clear, useful, and technically accurate first, pirate flavor second.
+- Do not overdo slang — every sentence should still be understandable on first read.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.
+- Never let roleplay reduce precision or hide important warnings.

package/souls/playful.md

@@ -1,3 +1,13 @@
-Respond with a witty and lively tone.
-Keep the answer readable and practical first, but allow a bit more personality and humor.
-Do not let humor obscure instructions or technical accuracy.
+Respond with a witty, lively, and slightly cheeky tone.
+
+Style guidelines:
+- Add personality and humor naturally — a well-placed quip or clever analogy goes a long way.
+- Use casual, conversational phrasing — "So here's the fun part...", "Plot twist:", "Easy fix incoming."
+- React to bugs and errors with good-natured humor — "Well, that's a creative way to break things."
+- Celebrate wins with flair — "Nailed it. Next?"
+
+Boundaries:
+- Keep the answer readable and practical first — humor is the seasoning, not the main dish.
+- Do not let jokes obscure instructions, warnings, or technical accuracy.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.
+- Avoid sarcasm that could feel dismissive of the user's question.

package/souls/professional.md

@@ -1,3 +1,13 @@
-Respond in a polished, professional tone.
-Keep phrasing precise, confident, and concise.
-Prefer structured explanations over playful expression.
+Respond in a polished, professional, and authoritative tone.
+
+Style guidelines:
+- Keep phrasing precise, confident, and concise — like a senior engineer briefing a team.
+- Prefer structured explanations: numbered steps, clear headings, and logical flow.
+- State conclusions first, then back them up — lead with the answer, follow with reasoning.
+- Use measured, deliberate language — "The recommended approach is...", "This ensures..."
+
+Boundaries:
+- Prefer structured explanations over playful expression.
+- Avoid colloquialisms, emojis, or overly casual phrasing.
+- Technical terms, code, file paths, and command output must remain precise and unchanged.
+- Never pad responses with filler — every sentence should earn its place.

package/src/cli.js

@@ -3,8 +3,9 @@ import { handleRun } from './commands/run.js';
 import { handleConfig } from './commands/config.js';
 import { handleDoctor } from './commands/doctor.js';
 import { handleSkill } from './commands/skill.js';
+import pkg from '../package.json' with { type: 'json' };
 
-const VERSION = '0.3.0';
+const VERSION = pkg.version;
 
 function printHelp() {
   console.log(`codemini ${VERSION}

package/src/commands/chat.js

@@ -92,16 +92,19 @@ export async function handleChat(args) {
   const React = (await import('react')).default;
   const { render } = await import('ink');
   const { ChatApp } = await import('../tui/chat-app.js');
+
   const instance = render(
     React.createElement(ChatApp, {
       runtime,
       sessionId: session.id,
       model: parsed.model || config.model.name,
+      sdkProvider: config.sdk?.provider || 'openai-compatible',
       language: config.ui?.language || 'zh',
       shellName: config.shell?.default || 'powershell',
       safeMode: config.policy?.safe_mode !== false,
       version: pkg.version
     })
   );
+
   await instance.waitUntilExit();
 }

package/src/commands/run.js

@@ -1,9 +1,10 @@
 import { loadConfig } from '../core/config-store.js';
 import { buildDefaultSystemPrompt } from '../core/default-system-prompt.js';
 import { runAgentLoop } from '../core/agent-loop.js';
-import { createChatCompletion } from '../core/provider/openai-compatible.js';
+import { createChatCompletion } from '../core/provider/index.js';
 import { buildSystemPromptWithSoul } from '../core/soul.js';
 import { getBuiltinTools } from '../core/tools.js';
+import { buildMemorySnapshot } from '../core/memory-prompt.js';
 
 function parseRunArgs(args) {
   const parsed = {
@@ -39,7 +40,9 @@ export async function handleRun(args) {
     workspaceRoot: process.cwd(),
     config
   });
-  const systemPrompt = await buildSystemPromptWithSoul(buildDefaultSystemPrompt(config), config);
+  const soulPrompt = await buildSystemPromptWithSoul(buildDefaultSystemPrompt(config), config);
+  const memorySnapshot = await buildMemorySnapshot({ config, workspaceRoot: process.cwd() }).catch(() => '');
+  const systemPrompt = [soulPrompt, memorySnapshot].filter(Boolean).join('\n\n');
 
   const result = await runAgentLoop({
     systemPrompt,
@@ -52,6 +55,7 @@ export async function handleRun(args) {
     maxSteps: parsed.maxSteps,
     requestCompletion: async ({ messages, tools, model }) =>
       createChatCompletion({
+        sdkProvider: config.sdk?.provider,
         baseUrl: config.gateway.base_url,
         apiKey: config.gateway.api_key,
         model,

package/src/core/agent-loop.js

@@ -1,6 +1,7 @@
 import os from 'node:os';
 import path from 'node:path';
 import fs from 'node:fs/promises';
+import { BoundedCache } from './bounded-cache.js';
 
 function safeJsonParse(raw) {
   if (!raw || typeof raw !== 'string') return {};
@@ -206,8 +207,16 @@ const TOOL_RESULTS_SUBDIR = 'tool-results';
 
 let currentResultDir = null;
 let resultDirReady = false;
-const storedResults = new Map(); // callId -> { filePath, summary }
-const readCache = new Map();     // "path:startLine:endLine:mtimeMs" -> true
+const storedResults = new BoundedCache({
+  maxSize: 64,
+  ttlMs: 30 * 60 * 1000,
+  onEvict(key, value) {
+    if (value?.filePath) {
+      fs.unlink(value.filePath).catch(() => {});
+    }
+  }
+}); // callId -> { filePath, summary }
+const readCache = new BoundedCache({ maxSize: 128, ttlMs: 10 * 60 * 1000 });   // "path:startLine:endLine:mtimeMs" -> true
 
 function generatePreview(content) {
   if (content.length <= PREVIEW_SIZE_BYTES) {
@@ -272,7 +281,7 @@ Summary: ${summary}
 
 export function clearResultStore() {
   const files = [];
-  for (const [, val] of storedResults) {
+  for (const [, val] of storedResults.entries()) {
     files.push(val.filePath);
   }
   storedResults.clear();
@@ -288,11 +297,6 @@ export function checkReadDedup(filePath, startLine, endLine, mtimeMs) {
     return true;
   }
   readCache.set(key, true);
-  // Keep cache bounded
-  if (readCache.size > 100) {
-    const firstKey = readCache.keys().next().value;
-    readCache.delete(firstKey);
-  }
   return false;
 }
 
@@ -687,7 +691,7 @@ export async function runAgentLoop({
     const assistantText = completion.text || '';
     lastAssistantText = assistantText || lastAssistantText;
 
-    const assistantMessage = { role: 'assistant', content: assistantText };
+    const assistantMessage = { role: 'assistant', content: completion?.content ?? assistantText };
     if (toolCalls.length > 0) {
       assistantMessage.tool_calls = toolCalls.map((tc) => ({
         id: tc.id,

package/src/core/ast.js

@@ -1,8 +1,9 @@
 import fs from 'node:fs/promises';
 import path from 'node:path';
-import crypto from 'node:crypto';
 import { createRequire } from 'node:module';
 import { Parser, Language, Query } from 'web-tree-sitter';
+import { LANGUAGE_ALIASES, EXTENSION_LANGUAGE_MAP } from './constants.js';
+import { sha256Prefixed as sha256 } from './crypto-utils.js';
 
 const require = createRequire(import.meta.url);
 
@@ -20,56 +21,6 @@ const WRAPPER_NODE_TYPES = new Set([
   'template_function',
   'template_type'
 ]);
-const LANGUAGE_ALIASES = {
-  javascript: 'js',
-  js: 'js',
-  jsx: 'js',
-  typescript: 'ts',
-  ts: 'ts',
-  tsx: 'tsx',
-  python: 'python',
-  py: 'python',
-  go: 'go',
-  c: 'c',
-  cpp: 'cpp',
-  'c++': 'cpp',
-  bash: 'bash',
-  sh: 'bash',
-  shell: 'bash',
-  java: 'java',
-  rust: 'rust',
-  rs: 'rust',
-  csharp: 'csharp',
-  'c#': 'csharp',
-  cs: 'csharp',
-  php: 'php',
-  ruby: 'ruby',
-  rb: 'ruby'
-};
-const EXTENSION_LANGUAGE_MAP = {
-  '.js': 'js',
-  '.jsx': 'js',
-  '.mjs': 'js',
-  '.cjs': 'js',
-  '.ts': 'ts',
-  '.tsx': 'tsx',
-  '.py': 'python',
-  '.go': 'go',
-  '.c': 'c',
-  '.h': 'c',
-  '.cpp': 'cpp',
-  '.cc': 'cpp',
-  '.cxx': 'cpp',
-  '.hpp': 'cpp',
-  '.hh': 'cpp',
-  '.java': 'java',
-  '.rs': 'rust',
-  '.cs': 'csharp',
-  '.php': 'php',
-  '.rb': 'ruby',
-  '.sh': 'bash',
-  '.bash': 'bash'
-};
 const LANGUAGE_WASM_PATHS = {
   js: require.resolve('@cursorless/tree-sitter-wasms/out/tree-sitter-javascript.wasm'),
   ts: require.resolve('@cursorless/tree-sitter-wasms/out/tree-sitter-typescript.wasm'),
@@ -94,10 +45,6 @@ const parserInitPromise = Parser.init({
 });
 const languageCache = new Map();
 
-function sha256(input) {
-  return `sha256:${crypto.createHash('sha256').update(String(input || '')).digest('hex')}`;
-}
-
 function clipText(text, maxLen = 220) {
   const normalized = String(text || '').replace(/\s+/g, ' ').trim();
   if (normalized.length <= maxLen) return normalized;

package/src/core/bounded-cache.js

@@ -0,0 +1,121 @@
+/**
+ * 有限大小 + TTL 的 Map 缓存，带主动清理和可选的 onEvict 钩子。
+ * 用于替代无界 Map 以防止长时间运行时的内存泄漏。
+ */
+
+const DEFAULT_MAX_SIZE = 128;
+const DEFAULT_TTL_MS = 10 * 60 * 1000; // 10 分钟
+
+export class BoundedCache {
+  constructor(options = {}) {
+    this._maxSize = options.maxSize ?? DEFAULT_MAX_SIZE;
+    this._ttlMs = options.ttlMs ?? DEFAULT_TTL_MS;
+    this._onEvict = options.onEvict ?? null;
+    this._map = new Map();
+  }
+
+  get(key) {
+    const entry = this._map.get(key);
+    if (!entry) return undefined;
+    if (this._expired(entry)) {
+      this._removeEntry(key, entry);
+      return undefined;
+    }
+    return entry.value;
+  }
+
+  has(key) {
+    return this.get(key) !== undefined;
+  }
+
+  set(key, value) {
+    if (this._map.has(key)) {
+      const old = this._map.get(key);
+      if (this._onEvict && old !== undefined) {
+        try { this._onEvict(key, old.value); } catch {}
+      }
+      this._map.delete(key);
+    }
+    this._map.set(key, { value, ts: Date.now() });
+    this._evict();
+  }
+
+  delete(key) {
+    const entry = this._map.get(key);
+    if (!entry) return false;
+    this._removeEntry(key, entry);
+    return true;
+  }
+
+  clear() {
+    if (this._onEvict) {
+      for (const [key, entry] of this._map) {
+        try { this._onEvict(key, entry.value); } catch {}
+      }
+    }
+    this._map.clear();
+  }
+
+  get size() {
+    this._prune();
+    return this._map.size;
+  }
+
+  keys() {
+    this._prune();
+    return this._map.keys();
+  }
+
+  values() {
+    this._prune();
+    const out = [];
+    for (const entry of this._map.values()) {
+      out.push(entry.value);
+    }
+    return out;
+  }
+
+  entries() {
+    this._prune();
+    const out = [];
+    for (const [key, entry] of this._map.entries()) {
+      out.push([key, entry.value]);
+    }
+    return out;
+  }
+
+  // ─── 内部方法 ──────────────────────────────────────────────────────
+
+  _expired(entry) {
+    return Date.now() - entry.ts > this._ttlMs;
+  }
+
+  _removeEntry(key, entry) {
+    this._map.delete(key);
+    if (this._onEvict) {
+      try { this._onEvict(key, entry.value); } catch {}
+    }
+  }
+
+  /** 清理所有过期条目 */
+  _prune() {
+    for (const [key, entry] of this._map) {
+      if (this._expired(entry)) {
+        this._removeEntry(key, entry);
+      }
+    }
+  }
+
+  /** 按数量裁剪最旧的条目 */
+  _evict() {
+    this._prune();
+    if (this._map.size <= this._maxSize) return;
+    const iter = this._map.keys();
+    while (this._map.size > this._maxSize) {
+      const oldest = iter.next().value;
+      if (oldest === undefined) break;
+      const entry = this._map.get(oldest);
+      this._removeEntry(oldest, entry);
+    }
+  }
+}