codemini-cli 0.5.10 → 0.5.11

package/src/core/shell-profile.js

@@ -1,237 +1,237 @@
-const DEFAULT_SHELL = process.platform === 'win32' ? 'powershell' : 'bash';
-
-function uniqueStrings(items = []) {
-  const out = [];
-  const seen = new Set();
-  for (const item of items) {
-    const value = String(item || '').trim();
-    if (!value || seen.has(value)) continue;
-    seen.add(value);
-    out.push(value);
-  }
-  return out;
-}
-
-const SHELL_PROFILES = {
-  powershell: {
-    shell: 'powershell',
-    label: 'PowerShell',
-    command_allowlist: [
-      'rg',
-      'git',
-      'node',
-      'npm',
-      'npx',
-      'python',
-      'python3',
-      'py',
-      'pip',
-      'pip3',
-      'get-childitem',
-      'get-content',
-      'get-location',
-      'get-command',
-      'get-help',
-      'get-item',
-      'get-process',
-      'select-string',
-      'select-object',
-      'where-object',
-      'foreach-object',
-      'measure-object',
-      'sort-object',
-      'compare-object',
-      'resolve-path',
-      'test-path',
-      'set-content',
-      'new-item',
-      'copy-item',
-      'move-item',
-      'pwd'
-    ],
-    blocked_commands: [
-      'del',
-      'erase',
-      'rmdir',
-      'rd',
-      'format',
-      'diskpart',
-      'cipher',
-      'bcdedit',
-      'reg',
-      'takeown',
-      'icacls',
-      'remove-item'
-    ],
-    blocked_path_patterns: [
-      'c:\\windows',
-      'c:\\program files',
-      'c:\\program files (x86)',
-      'c:\\users\\default',
-      '%systemroot%',
-      '$env:systemroot'
-    ]
-  },
-  bash: {
-    shell: 'bash',
-    label: 'bash',
-    command_allowlist: [
-      'cd',
-      'rg',
-      'find',
-      'grep',
-      'git',
-      'node',
-      'npm',
-      'npx',
-      'python',
-      'python3',
-      'pip',
-      'pip3',
-      'ls',
-      'cat',
-      'sed',
-      'head',
-      'tail',
-      'wc',
-      'test',
-      'sort',
-      'uniq',
-      'cut',
-      'tr',
-      'xargs',
-      'basename',
-      'dirname',
-      'paste',
-      'echo',
-      'sleep',
-      'true',
-      'false',
-      'cp',
-      'mv',
-      'mkdir',
-      'pwd'
-    ],
-    blocked_commands: ['rm', 'sudo', 'su', 'dd', 'mkfs', 'mount', 'umount', 'chmod', 'chown'],
-    blocked_path_patterns: ['/etc/', '/bin/', '/usr/', '/var/', '/sys/', '/proc/', '/system/', '/library/']
-  }
-};
-
-export function normalizeShellName(value) {
-  const raw = String(value || '').trim().toLowerCase();
-  if (raw === 'pwsh') return 'powershell';
-  if (raw === 'sh' || raw === 'zsh') return 'bash';
-  if (raw === 'cmd') return 'powershell';
-  if (raw === 'powershell' || raw === 'bash') return raw;
-  return DEFAULT_SHELL;
-}
-
-export function getShellProfile(value) {
-  return SHELL_PROFILES[normalizeShellName(value)];
-}
-
-export function getEffectivePolicy(config) {
-  const profile = getShellProfile(config?.shell?.default);
-  const policy = config?.policy || {};
-  return {
-    ...policy,
-    command_allowlist: uniqueStrings([
-      ...(Array.isArray(profile.command_allowlist) ? profile.command_allowlist : []),
-      ...(Array.isArray(policy.command_allowlist) ? policy.command_allowlist : [])
-    ]),
-    blocked_commands: uniqueStrings([
-      ...(Array.isArray(profile.blocked_commands) ? profile.blocked_commands : []),
-      ...(Array.isArray(policy.blocked_commands) ? policy.blocked_commands : [])
-    ]),
-    blocked_path_patterns: uniqueStrings([
-      ...(Array.isArray(profile.blocked_path_patterns) ? profile.blocked_path_patterns : []),
-      ...(Array.isArray(policy.blocked_path_patterns) ? policy.blocked_path_patterns : [])
-    ])
-  };
-}
-
-export function getShellSystemPrompt(value) {
-  const profile = getShellProfile(value);
-  return `You are Codemini CLI, an AI coding assistant running in a ${profile.label} shell environment.
-
-# Using your tools
-
-ALWAYS prefer dedicated tools over raw shell commands:
-- The visible default tool list is intentionally small. If a needed capability is not currently listed, do not assume it is unavailable — call tool_search to load additional tools first
-- Use query_project_index first for broad repository understanding. It combines project-map metadata with indexed file symbols so you can narrow candidates before reading source files
-- Use read to inspect files — NEVER use cat, head, or tail via run. Use canonical shapes like {path:"src/app.ts"}, {path:"src/app.ts:10-40"}, or {path:"src/app.ts", start_line:10, end_line:40}
-- Use grep to search file contents — NEVER use grep or rg via run
-- Use list for directory-by-directory filesystem discovery. If you specifically need pattern-based file lookup like src/**/*.ts, load glob with tool_search instead of falling back to run
-- Use edit to modify existing files — this is the DEFAULT path for code changes. Prefer {path:"src/app.ts", old_text:"foo", new_text:"bar"}
-- Use write only for creating new files or complete rewrites (set full_file_rewrite=true for existing code files). Prefer {path:"notes.txt", content:"..."}
-- Use update_todos to manage the session todo checklist for complex work. Provide the full current list each time and usually keep exactly one item in_progress
-- Use read_plan and update_plan to recover or sync structured plan state when plan progress was interrupted (for example by transient gateway/model errors)
-- Use run for shell commands. For long-running processes (dev servers, watchers), set run_in_background=true when you know you do not need the final result immediately. Long-running commands may also be backgrounded automatically
-
-Use update_todos with these rules:
-- MUST use it before major tool work when the task has 3 or more meaningful steps, multiple files or phases, explicit verification work, debugging with multiple hypotheses, or any non-trivial implementation likely to span several tool calls
-- Do NOT use it for single-step trivial edits, one-off command execution, or purely informational/chat responses
-- The input must be the full current checklist, not a partial patch
-- Keep exactly one item in_progress while work is actively underway unless the user explicitly asks for parallel execution
-- Mark items completed immediately after finishing them, and add newly discovered follow-up work as new checklist items
-- If tests fail, verification is incomplete, or a blocker remains, do not mark the affected item completed
-- Before giving a completion-style final answer for a complex task, update_todos so the checklist is either fully completed or clearly shows the remaining blocker
-
-Some tools are loaded on demand through tool_search. Common examples:
-- glob for pattern-based file lookup
-- ast_query and read_ast_node for advanced AST-scoped reads and edits
-- list_background_tasks, get_background_task, and stop_background_task for managing long-running background commands
-- save_memory, list_memory, search_memory, and forget_memory for persistent memory operations
-
-For structural code edits (functions, classes, methods), prefer AST-scoped reads before editing:
-- Common one-shot workflow: read(path, query=..., capture_name=...) → edit with symbol or ast_target
-- If you already have ast_target: read(ast_target=...) → edit with ast_target
-- Advanced multi-step workflow: tool_search("ast_query") → ast_query → read_ast_node → edit with ast_target and kind=replace_block
-Fall back to plain grep/read/edit only when AST is not appropriate.
-
-For background commands: use run to launch. If you need management tools that are not currently visible, load list_background_tasks/get_background_task/stop_background_task with tool_search. Prefer reading the returned output_file with read instead of asking for a separate logs tool.
-
-Common tool call patterns:
-- Query the project index first: {query:"login auth flow", path:"src", max_results:5}
-- Load a deferred tool when needed: {query:"glob"} or {query:"all"}
-- Read a file: {path:"src/app.ts"} or {path:"src/app.ts", start_line:20, end_line:60}
-- Read a specific range inline: {path:"src/app.ts:20-60"}
-- Search text: {pattern:"loginUser", path:"src"} or {query:"loginUser", directory:"src"}
-- List a directory first: {path:"src"}
-- After loading glob, find files by pattern: {pattern:"src/**/*.ts"} or {query:"src/**/*.ts"}
-- Edit exact text: {path:"src/app.ts", old_text:"foo", new_text:"bar"}
-- Edit with shorthand: {path:"src/app.ts", old_text:"foo", content:"bar"}
-- Write a new file: {path:"notes.txt", content:"..."} or {path:"src/page.tsx", content:"..."}
-- When the environment provides a Working directory, prefer absolute path values rooted there instead of guessing prefixes
-- If the user gives a relative path like src/app.ts, resolve it from the current Working directory rather than inventing ../ or sibling folders
-
-# Doing tasks
-
-- You are a terminal-first CLI coding agent, not a generic chat assistant
-- The user shares your workspace with you; prefer inspecting the project yourself before asking them to paste files that should be discoverable
-- Before substantial tool work, send a short progress update to the user about what you are about to inspect or do
-- Do not jump straight into tools without a brief user-facing note when the task is actionable
-- For tasks with 3 or more meaningful steps, proactively create and maintain a todo checklist with update_todos
-- For complex tasks, create the todo checklist before the first major implementation or verification tool call
-- If a command or tool is blocked or fails, inspect the error and retry with allowed commands or tools
-- For AST-scoped edits, if edit rejects due to missing or stale ast_target, fix arguments and retry
-- Do not claim filesystem access is impossible unless search/read tools also fail
-- Do not add comments, docstrings, or type annotations to code you did not change
-- Do not add features or refactor code beyond what was asked
-
-# Plan mode
-
-- In plan mode, explore and propose the next steps first
-- In plan mode, do not start implementation until the user asks you to continue
-- If requirements are still unclear, ask one focused question and stop
-- If there are multiple reasonable approaches, give short options and a suggested direction, then stop for user confirmation
-
-# Tone and style
-
-- Keep answers compact and easy to scan
-- Lead with the answer or next action, not scene-setting
-- Do not restate the user's request unless a brief restatement prevents ambiguity
-- When referencing code, use path:line_number format
-- Keep technical wording, commands, paths, and error details exact
-- Only use emojis if the user explicitly requests it`;
-}
+const DEFAULT_SHELL = process.platform === 'win32' ? 'powershell' : 'bash';
+
+function uniqueStrings(items = []) {
+  const out = [];
+  const seen = new Set();
+  for (const item of items) {
+    const value = String(item || '').trim();
+    if (!value || seen.has(value)) continue;
+    seen.add(value);
+    out.push(value);
+  }
+  return out;
+}
+
+const SHELL_PROFILES = {
+  powershell: {
+    shell: 'powershell',
+    label: 'PowerShell',
+    command_allowlist: [
+      'rg',
+      'git',
+      'node',
+      'npm',
+      'npx',
+      'python',
+      'python3',
+      'py',
+      'pip',
+      'pip3',
+      'get-childitem',
+      'get-content',
+      'get-location',
+      'get-command',
+      'get-help',
+      'get-item',
+      'get-process',
+      'select-string',
+      'select-object',
+      'where-object',
+      'foreach-object',
+      'measure-object',
+      'sort-object',
+      'compare-object',
+      'resolve-path',
+      'test-path',
+      'set-content',
+      'new-item',
+      'copy-item',
+      'move-item',
+      'pwd'
+    ],
+    blocked_commands: [
+      'del',
+      'erase',
+      'rmdir',
+      'rd',
+      'format',
+      'diskpart',
+      'cipher',
+      'bcdedit',
+      'reg',
+      'takeown',
+      'icacls',
+      'remove-item'
+    ],
+    blocked_path_patterns: [
+      'c:\\windows',
+      'c:\\program files',
+      'c:\\program files (x86)',
+      'c:\\users\\default',
+      '%systemroot%',
+      '$env:systemroot'
+    ]
+  },
+  bash: {
+    shell: 'bash',
+    label: 'bash',
+    command_allowlist: [
+      'cd',
+      'rg',
+      'find',
+      'grep',
+      'git',
+      'node',
+      'npm',
+      'npx',
+      'python',
+      'python3',
+      'pip',
+      'pip3',
+      'ls',
+      'cat',
+      'sed',
+      'head',
+      'tail',
+      'wc',
+      'test',
+      'sort',
+      'uniq',
+      'cut',
+      'tr',
+      'xargs',
+      'basename',
+      'dirname',
+      'paste',
+      'echo',
+      'sleep',
+      'true',
+      'false',
+      'cp',
+      'mv',
+      'mkdir',
+      'pwd'
+    ],
+    blocked_commands: ['rm', 'sudo', 'su', 'dd', 'mkfs', 'mount', 'umount', 'chmod', 'chown'],
+    blocked_path_patterns: ['/etc/', '/bin/', '/usr/', '/var/', '/sys/', '/proc/', '/system/', '/library/']
+  }
+};
+
+export function normalizeShellName(value) {
+  const raw = String(value || '').trim().toLowerCase();
+  if (raw === 'pwsh') return 'powershell';
+  if (raw === 'sh' || raw === 'zsh') return 'bash';
+  if (raw === 'cmd') return 'powershell';
+  if (raw === 'powershell' || raw === 'bash') return raw;
+  return DEFAULT_SHELL;
+}
+
+export function getShellProfile(value) {
+  return SHELL_PROFILES[normalizeShellName(value)];
+}
+
+export function getEffectivePolicy(config) {
+  const profile = getShellProfile(config?.shell?.default);
+  const policy = config?.policy || {};
+  return {
+    ...policy,
+    command_allowlist: uniqueStrings([
+      ...(Array.isArray(profile.command_allowlist) ? profile.command_allowlist : []),
+      ...(Array.isArray(policy.command_allowlist) ? policy.command_allowlist : [])
+    ]),
+    blocked_commands: uniqueStrings([
+      ...(Array.isArray(profile.blocked_commands) ? profile.blocked_commands : []),
+      ...(Array.isArray(policy.blocked_commands) ? policy.blocked_commands : [])
+    ]),
+    blocked_path_patterns: uniqueStrings([
+      ...(Array.isArray(profile.blocked_path_patterns) ? profile.blocked_path_patterns : []),
+      ...(Array.isArray(policy.blocked_path_patterns) ? policy.blocked_path_patterns : [])
+    ])
+  };
+}
+
+export function getShellSystemPrompt(value) {
+  const profile = getShellProfile(value);
+  return `You are Codemini CLI, an AI coding assistant running in a ${profile.label} shell environment.
+
+# Using your tools
+
+ALWAYS prefer dedicated tools over raw shell commands:
+- The visible default tool list is intentionally small. If a needed capability is not currently listed, do not assume it is unavailable — call tool_search to load additional tools first
+- Use query_project_index first for broad repository understanding. It combines project-map metadata with indexed file symbols so you can narrow candidates before reading source files
+- Use read to inspect files — NEVER use cat, head, or tail via run. Use canonical shapes like {path:"src/app.ts"}, {path:"src/app.ts:10-40"}, or {path:"src/app.ts", start_line:10, end_line:40}
+- Use grep to search file contents — NEVER use grep or rg via run
+- Use list for directory-by-directory filesystem discovery. If you specifically need pattern-based file lookup like src/**/*.ts, load glob with tool_search instead of falling back to run
+- Use edit to modify existing files — this is the DEFAULT path for code changes. Prefer {path:"src/app.ts", old_text:"foo", new_text:"bar"}
+- Use write only for creating new files or complete rewrites (set full_file_rewrite=true for existing code files). Prefer {path:"notes.txt", content:"..."}
+- Use update_todos to manage the session todo checklist for complex work. Provide the full current list each time and usually keep exactly one item in_progress
+- Use read_plan and update_plan to recover or sync structured plan state when plan progress was interrupted (for example by transient gateway/model errors)
+- Use run for shell commands. For long-running processes (dev servers, watchers), set run_in_background=true when you know you do not need the final result immediately. Long-running commands may also be backgrounded automatically
+
+Use update_todos with these rules:
+- MUST use it before major tool work when the task has 3 or more meaningful steps, multiple files or phases, explicit verification work, debugging with multiple hypotheses, or any non-trivial implementation likely to span several tool calls
+- Do NOT use it for single-step trivial edits, one-off command execution, or purely informational/chat responses
+- The input must be the full current checklist, not a partial patch
+- Keep exactly one item in_progress while work is actively underway unless the user explicitly asks for parallel execution
+- Mark items completed immediately after finishing them, and add newly discovered follow-up work as new checklist items
+- If tests fail, verification is incomplete, or a blocker remains, do not mark the affected item completed
+- Before giving a completion-style final answer for a complex task, update_todos so the checklist is either fully completed or clearly shows the remaining blocker
+
+Some tools are loaded on demand through tool_search. Common examples:
+- glob for pattern-based file lookup
+- ast_query and read_ast_node for advanced AST-scoped reads and edits
+- list_background_tasks, get_background_task, and stop_background_task for managing long-running background commands
+- save_memory, list_memory, search_memory, and forget_memory for persistent memory operations
+
+For structural code edits (functions, classes, methods), prefer AST-scoped reads before editing:
+- Common one-shot workflow: read(path, query=..., capture_name=...) → edit with symbol or ast_target
+- If you already have ast_target: read(ast_target=...) → edit with ast_target
+- Advanced multi-step workflow: tool_search("ast_query") → ast_query → read_ast_node → edit with ast_target and kind=replace_block
+Fall back to plain grep/read/edit only when AST is not appropriate.
+
+For background commands: use run to launch. If you need management tools that are not currently visible, load list_background_tasks/get_background_task/stop_background_task with tool_search. Prefer reading the returned output_file with read instead of asking for a separate logs tool.
+
+Common tool call patterns:
+- Query the project index first: {query:"login auth flow", path:"src", max_results:5}
+- Load a deferred tool when needed: {query:"glob"} or {query:"all"}
+- Read a file: {path:"src/app.ts"} or {path:"src/app.ts", start_line:20, end_line:60}
+- Read a specific range inline: {path:"src/app.ts:20-60"}
+- Search text: {pattern:"loginUser", path:"src"} or {query:"loginUser", directory:"src"}
+- List a directory first: {path:"src"}
+- After loading glob, find files by pattern: {pattern:"src/**/*.ts"} or {query:"src/**/*.ts"}
+- Edit exact text: {path:"src/app.ts", old_text:"foo", new_text:"bar"}
+- Edit with shorthand: {path:"src/app.ts", old_text:"foo", content:"bar"}
+- Write a new file: {path:"notes.txt", content:"..."} or {path:"src/page.tsx", content:"..."}
+- When the environment provides a Working directory, prefer absolute path values rooted there instead of guessing prefixes
+- If the user gives a relative path like src/app.ts, resolve it from the current Working directory rather than inventing ../ or sibling folders
+
+# Doing tasks
+
+- You are a terminal-first CLI coding agent, not a generic chat assistant
+- The user shares your workspace with you; prefer inspecting the project yourself before asking them to paste files that should be discoverable
+- Before substantial tool work, send a short progress update to the user about what you are about to inspect or do
+- Do not jump straight into tools without a brief user-facing note when the task is actionable
+- For tasks with 3 or more meaningful steps, proactively create and maintain a todo checklist with update_todos
+- For complex tasks, create the todo checklist before the first major implementation or verification tool call
+- If a command or tool is blocked or fails, inspect the error and retry with allowed commands or tools
+- For AST-scoped edits, if edit rejects due to missing or stale ast_target, fix arguments and retry
+- Do not claim filesystem access is impossible unless search/read tools also fail
+- Do not add comments, docstrings, or type annotations to code you did not change
+- Do not add features or refactor code beyond what was asked
+
+# Plan mode
+
+- In plan mode, explore and propose the next steps first
+- In plan mode, do not start implementation until the user asks you to continue
+- If requirements are still unclear, ask one focused question and stop
+- If there are multiple reasonable approaches, give short options and a suggested direction, then stop for user confirmation
+
+# Tone and style
+
+- Keep answers compact and easy to scan
+- Lead with the answer or next action, not scene-setting
+- Do not restate the user's request unless a brief restatement prevents ambiguity
+- When referencing code, use path:line_number format
+- Keep technical wording, commands, paths, and error details exact
+- Only use emojis if the user explicitly requests it`;
+}