mocode-ai 1.0.14 → 1.1.1

package/dist/config/index.js

@@ -2,8 +2,6 @@ import fs from 'node:fs';
 import os from 'node:os';
 import path from 'node:path';
 import dotenv from 'dotenv';
-import { loadSnapshot } from '../project-snapshot/index.js';
-import { buildProjectSkillSection } from '../project-skill/index.js';
 import { getSandboxRoot } from '../sandbox/root.js';
 import { getCurrentSessionId } from '../session/state.js';
 import { buildWorkDisciplineSection, inferModelFamily } from '../agent/work-discipline.js';
@@ -64,57 +62,32 @@ export function isModelConfigured() {
 const PLATFORM_NOTE = (() => {
     if (process.platform === 'win32') {
         return `## Environment (Windows)
-- You are on Windows; run_command runs commands via cmd.exe (/c). Unix shell builtins are NOT available here.
-- Windows equivalents: which→where, cat→type, ls→dir, rm→del/rd, cp→copy, mv→move. cmd.exe uses %VAR% (not $VAR); pipes (|) and redirects (>, >>) work, but no $(...) command substitution or backticks.
-- head/tail/find/grep/sed have no cmd.exe equivalent — use the dedicated tools (read_file for head/tail, glob for find, grep for grep), or invoke PowerShell via run_command if you need more.
-- **Avoid \`run_command\` for file ops on Windows**: cmd /c re-parses paths with backslashes / spaces / quotes — fragile, and ~half of "agent can't find file" failures trace back to this. Use the dedicated tools (read_file/glob/grep) which take absolute Windows paths natively, no shell involved. In particular, NEVER \`dir\` / \`ls\` / \`Test-Path\` / \`if exist\` / \`python -c "os.path.exists(...)"\` — those waste turns on escaping. Use \`glob\` to list, and just call \`read_file\` to test existence (returns ENOENT as a clean error string). If you must shell out, use forward slashes (\`C:/foo/bar\`).
-- Prefer the dedicated tools (read_file/glob/grep) over shell equivalents — they're cross-platform and already wired in.`;
+- \`run_command\` uses \`cmd.exe /c\`: use cmd syntax and \`%VAR%\`; Unix builtins and command substitution are unavailable.
+- Prefer read_file/glob/grep for file discovery and reading. When shell is necessary, use forward-slash paths or invoke PowerShell explicitly.`;
     }
     if (process.platform === 'darwin') {
         return `## Environment (macOS)
-- You are on macOS; run_command runs via bash -c (user default shell may be zsh). BSD coreutils, not GNU.
-- Pitfalls: sed -i needs an empty backup-ext arg (sed -i '' 's/x/y/' file); grep -P unavailable (use grep -E or the grep tool); find/readlink/date are BSD variants; readlink -f unsupported (use realpath, or greadlink -f if GNU coreutils installed via brew).
-- Prefer the dedicated tools (read_file/glob/grep) over shell equivalents — they sidestep BSD/GNU differences.`;
+- \`run_command\` uses bash with BSD utilities. Prefer read_file/glob/grep; account for BSD/GNU differences when shell commands are necessary.`;
     }
     return `## Environment (Linux/Unix)
-- You are on ${process.platform}; run_command runs via bash -c. GNU coreutils — standard POSIX/GNU shell syntax is safe.
-- Still prefer the dedicated tools (read_file/glob/grep) over hand-rolled shell where they fit — they avoid quoting pitfalls and are already wired in.`;
+- \`run_command\` uses bash. Prefer read_file/glob/grep when they fit; otherwise use standard POSIX/GNU syntax.`;
 })();
 /**
  * 基础系统提示的"记忆段落":开 isMemoryEnabled() 时才拼。
  * 默认关(新用户零侵入):这段 + 工具表里的 5 个 memory_* + 系统提示尾部的 Memory Index
  * 都不出现;打开 /memory_switch 后下一次新建 system message 才注入。
  */
-/**
- * 项目快照段落：开 isProjectSnapshotEnabled() 且有快照时才拼。
- * 告诉 LLM 项目已有哪些静态文件可 cache hit，减少无谓 read_file。
- */
-function buildSnapshotSection() {
-    if (!config.projectSnapshotEnabled)
-        return '';
-    try {
-        const snap = loadSnapshot();
-        if (!snap)
-            return '';
-        // 快照内容已经是完整的 markdown，直接返回
-        return `\n${snap.content}\n`;
-    }
-    catch {
-        return '';
-    }
-}
-/**
- * 项目快照总开关查询器（read-file 工具用）。
- */
-export function isProjectSnapshotEnabled() {
-    return config.projectSnapshotEnabled;
-}
 /**
  * Session notepad 段落：读取 .mocode/sessions/<sessionId>/notes.md，只注入 ## 标题行作为目录摘要。
  * Agent 用 write_file/edit_file/read_file 维护此文件，抗 compact（在 context window 之外）。
  * 文件不存在或为空时返空串（零开销）。
+ *
+ * 输出按"活跃 / 已完成"两栏分桶，让 agent 一眼看到还有未结的工作：
+ *   - Active: ## Plan: ...   ## Open Questions   ## <其它正在用的 topic>
+ *   - Done:   ## Done: ...   (agent 在完成时把 topic 重命名为 "## Done: ...")
+ * 这样比纯目录列表更显眼，降低 agent 在长上下文里扫过去就忘了的概率。
  */
-function buildNotepadSection(sessionId = getCurrentSessionId()) {
+export function buildNotepadSection(sessionId = getCurrentSessionId()) {
     if (!sessionId)
         return '';
     const root = getSandboxRoot() ?? process.cwd();
@@ -125,39 +98,54 @@ function buildNotepadSection(sessionId = getCurrentSessionId()) {
         const content = fs.readFileSync(p, 'utf8').trim();
         if (!content)
             return '';
-        // 1) 提取 ## 标题行（最多 15 个），用作目录摘要
+        // 1) 提取 ## 标题行（最多 15 个，按文件出现顺序保留）
         const headers = content.split('\n')
             .filter(l => /^##\s/.test(l))
             .slice(0, 15);
-        // 2) 提取 Plan 段进度（仅当存在 "## Plan: ..." 时）
-        const planMatch = content.match(/^## Plan:\s*(.+)$/m);
-        const stepsTotal = (content.match(/^\s*-\s*\[[ xX]\]\s*\d+\./gm) || []).length;
-        const stepsDone = (content.match(/^\s*-\s*\[[xX]\]\s*\d+\./gm) || []).length;
-        const planChip = planMatch
-            ? `\nPlan: ${planMatch[1].trim()} (${stepsDone}/${stepsTotal})`
-            : '';
-        if (headers.length === 0 && !planChip)
+        // 2) 分桶：Done: 开头 → archived；其余 → active
+        //    "## Plan:" 和 "## Open Questions" 视为永久 active（不需要改名为 Done）。
+        const archived = [];
+        const active = [];
+        for (const h of headers) {
+            if (/^##\s+Done:\s/.test(h))
+                archived.push(h);
+            else
+                active.push(h);
+        }
+        if (active.length === 0 && archived.length === 0)
             return '';
-        return [
-            '',
-            `## Session Notepad (your working notes — use read_file(".mocode/sessions/${sessionId}/notes.md") for details)`,
-            'Sections:',
-            ...headers,
-            planChip,
+        const totalCount = active.length + archived.length;
+        const lines = [
             '',
-        ].join('\n');
+            `## Session Notepad (${totalCount} section${totalCount === 1 ? '' : 's'} — read \`.mocode/sessions/${sessionId}/notes.md\` to recover full context; surviving compact is the whole point of this file)`,
+            `Active (${active.length}):`,
+            ...(active.length ? active.map(h => `  - ${h.replace(/^##\s+/, '')}`) : ['  - (none)']),
+        ];
+        if (archived.length) {
+            lines.push(`Done (${archived.length}):`);
+            lines.push(...archived.map(h => `  - ${h.replace(/^##\s+/, '')}`));
+        }
+        lines.push('');
+        return lines.join('\n');
     }
     catch {
         return '';
     }
 }
 const SYSTEM_PROMPT_MEMORY_SECTION = `
-## Memory (cross-session long-term facts)
-- A "memory index" (id/title/summary only) is injected into the system prompt. Retrieve full body via memory_search (pass id or keyword); use memory_list to see the entire index.
-- Store non-obvious, cross-session-useful facts/decisions/pitfalls (architecture conventions, gotchas, user preferences, decisions made) with memory_save — only long-term stable items, not current bugs / temp files / undecided TODOs.
-- If an existing memory is outdated or contradicts new facts, correct it in-place with memory_update(id, …) (don't create a duplicate); archive clearly-stale ones with memory_forget(id).
-- Before saving, memory_search to check for an existing similar entry to avoid duplicates. Better to store less than to store trivially correct information.
-- A background reflection pass periodically mines and organizes memories from the session (no manual action needed), but key facts you proactively save are more reliable.`;
+## Memory (cross-session facts)
+- The prompt may contain a title/summary index; retrieve details with memory_search or inspect all with memory_list.
+- Save only stable, non-obvious cross-session facts. Search before saving; update an existing entry instead of duplicating it, and archive stale entries.`;
+/** Inject only retrieval guidance; MOCODE.md contents stay outside the prompt until read on demand. */
+function buildMemoryPromptSection() {
+    if (!isMemoryEnabled())
+        return '';
+    const projectMocode = path.join(process.cwd(), 'MOCODE.md');
+    const mocodeHint = fs.existsSync(projectMocode)
+        ? '\n- `MOCODE.md` exists at the workspace root but is not preloaded. Read it with `read_file` only when the task may depend on project architecture, conventions, commands, prior decisions, or user preferences; skip it for greetings and unrelated simple requests. Current code and the user request override stale memory.'
+        : '';
+    return SYSTEM_PROMPT_MEMORY_SECTION + mocodeHint;
+}
 /**
  * plan 模式追加到系统提示末尾的指令(切到 plan 模式时由 repl 拼进 history[0])。
  * 与 SYSTEM_PROMPT 同语种(英文),指示:只读探查、产出步骤化计划、不执行、审批后回 auto。
@@ -165,167 +153,74 @@ const SYSTEM_PROMPT_MEMORY_SECTION = `
  * memoryEnabled=false 时:memory_save/update/forget 三个写工具名字 + "memory-write tools" 这
  * 句都不出现,且 read-only 列表里的 memory_search/memory_list 也移除——避免提示词里出现
  * 根本不存在的工具名引起 LLM 调不到。
+ *
+ * .codegraph/ 存在性也动态决定:有索引时引导 LLM 优先用 codegraph skill(免去逐文件扫);
+ * 没索引时干脆不提,避免 LLM 调出失败。函数化(非 const)以便在 buildPlanModeSuffix 里现拼。
  */
-const PLAN_RESEARCH_RULES = `
-- Research enough to locate relevant code, trace call paths, and understand existing conventions. Use the codegraph-first Workflow, but do not repeat information already retrieved in this session.
-- Produce an actionable plan: files and reasons, ordered steps, edge cases, and verification (typecheck / tests / build).
-- When ready, MUST call the \`ask_human\` tool with a concise summary and exactly these options:
-  1. "按计划执行 (switch to auto and implement)" — call \`switch_mode("auto")\` in the same turn, then implement.
-  2. "继续细化方案 (stay in plan, refine)" — remain in plan and refine.
-  3. "取消 / 暂不执行 (abort)" — stop without switching mode.
-- Never silently switch or stop. Do not ask approval in plain text; \`ask_human\` is the approval channel.
-- The REPL approval prompt is only a fallback; do not rely on it.`;
-function buildPlanModeSuffix() {
-    const memoryTools = isMemoryEnabled()
-        ? 'memory_save, memory_update, memory_forget'
+function buildPlanResearchRules() {
+    const cg = hasCodegraphIndex()
+        ? ' Prefer the available codegraph skill for call paths and blast radius.'
         : '';
-    const readOnlyTools = isMemoryEnabled()
-        ? 'read_file, glob, grep, codegraph, web_search, web_fetch, use_skill, ask_human, memory_search, memory_list'
-        : 'read_file, glob, grep, codegraph, web_search, web_fetch, use_skill, ask_human';
-    const removed = ['write_file', 'edit_file', 'run_command', memoryTools]
-        .filter(Boolean)
-        .join(', ');
+    return `
+- Locate relevant code and conventions without repeating retrieved work.${cg}
+- Return an actionable plan with affected files, ordered steps, edge cases, and verification.
+- When ready, call \`ask_human\` with exactly: "按计划执行", "继续细化方案", and "取消 / 暂不执行". Approval requires the user to switch to /auto; never execute or switch modes silently.`;
+}
+function buildPlanModeSuffix() {
     return `
 
 ## ⛯ PLAN MODE (active now)
-You are in PLAN mode: investigate and design only — do NOT execute or change anything.
-- Removed from your tool list: ${removed}. Use only these read-only tools: ${readOnlyTools}.
-${PLAN_RESEARCH_RULES}`;
+Investigate and design only. Use only the read-only tools currently exposed; do not execute commands or change files.
+${buildPlanResearchRules()}`;
 }
 /** 兼容旧名字:repl 的 buildSystemMessage 仍引 PLAN_MODE_SUFFIX(变量)。运行时按需现拼。 */
 export function buildBasePrompt(sessionId = getCurrentSessionId()) {
-    const autoAllToolsLine = isMemoryEnabled()
-        ? '- Default is AUTO mode: you research and execute with all tools (read/edit/run_command/memory/web/skills).'
-        : '- Default is AUTO mode: you research and execute with all tools (read/edit/run_command/web/skills).';
-    const memorySection = isMemoryEnabled() ? SYSTEM_PROMPT_MEMORY_SECTION : '';
-    const planLine = isMemoryEnabled()
-        ? '- For complex or multi-step tasks, the user may switch to PLAN mode (Shift+Tab): your editing/command/memory-write tools are then removed from your tool list, and you must research with read-only tools only and produce a step-by-step plan (no execution). On approval the session returns to auto mode to execute the plan.'
-        : '- For complex or multi-step tasks, the user may switch to PLAN mode (Shift+Tab): your editing/command tools are then removed from your tool list, and you must research with read-only tools only and produce a step-by-step plan (no execution). On approval the session returns to auto mode to execute the plan.';
+    const memorySection = buildMemoryPromptSection();
     return `## Core behavior
 You are mocode, a terminal coding agent. Complete programming tasks through a "think → call tool → observe result → think again" loop until solved. ${t('assistant.languageInstruction')}
 
-## 模式 (Modes)
-${autoAllToolsLine}
-${planLine}
+## Modes
+- AUTO is the default: investigate and complete the task with the tools currently exposed.
+- PLAN is read-only research and design; do not make changes until the user approves and switches back to AUTO.
 
 ${PLATFORM_NOTE}
 
 ${buildWorkDisciplineSection(inferModelFamily(config.model))}
 
-## Tool details
-### Token-efficient execution
-- First check whether the answer is already in this conversation or a previous tool result. If yes, answer directly; do not re-run tools "to be safe".
-- Plan the complete sub-task before calling tools. Batch independent reads in one turn. Because tool calls in one response execute without intermediate model reasoning, never batch a read with an edit that depends on its result.
-- Do not read "just to see". Read only what supports the next decision. Re-read after a change, compaction, stale state, or uncertain line context.
-- Prefer one precise call over overlapping searches. If a call fails, inspect the error and change the approach instead of repeating it unchanged.
-- Batch only independent read-only calls. After their results arrive, make the dependent edit in the next turn; then batch independent edits and one final verification when their exact inputs are already known.
-- Read only what supports the next decision; verify once after a related edit set, not after every edit.
-- Do not repeat an unchanged failing call; after three unproductive attempts, change tools or ask for the missing decision.
-- For \`edit_file\`, derive \`old_string\` by copying the exact relevant lines from the latest successful \`read_file\` of that same path and pass that read's \`expected_hash\`; never reconstruct either from memory, a summary, grep output, or a previous diff. That read becomes stale after any edit/write to the path, compaction/resume, or a possible external change. On a conflict, re-read the exact region and retry once with the new text and hash; never retry identical arguments.
-
 ## Workflow
-- Understand requirements and current code before acting; do not guess.
-- If \`.codegraph/\` exists, use \`codegraph\` first for unfamiliar code questions. Use direct reads for known or recently changed files.
-- After modifications, run the smallest relevant verification, then typecheck/build when appropriate. Never claim success without evidence.
-- Use web search only when freshness materially affects the answer (new APIs, versions, security, current UI conventions).
-
-## Tool rules
-- Precise path/symbol → go directly to \`read_file\` or \`codegraph node\`; use \`glob\`/\`grep\` only for discovery.
-- Before editing, read the exact target region and copy both its artifact \`hash\` and verbatim text. Use \`edit_file\` with \`expected_hash\` for unique local replacements, and \`write_file\` with the latest hash for replacement (or null only for creation).
-- Local edits require an exact unique match; use \`write_file\` for new/full files.
-- Use \`glob\`/\`grep\` for discovery and \`run_command\` for execution or verification, not file existence checks. State intent before side effects.
-- Call \`ask_human\` only when a real user decision is required; otherwise decide and proceed.
-- Drop stale tool output when it no longer supports the current sub-task. Keep only evidence needed for the next decision.
-- Batch independent writes only when each input is already known and their order does not matter. Keep dependent mutations sequential. Combine a clear shell workflow in one command; follow up when its result creates a decision.
-
-## Large file writes (avoid token-cap truncation)
-- \`write_file\` / \`edit_file\` arguments are part of the model's JSON output — a single tool call's content > ~5K tokens risks mid-stream truncation when the model's max output (default 8K–16K tokens) is exceeded, producing a "arguments 不是合法 JSON" error. Even with \`MAX_TOKENS=32000\` set, huge files still risk truncation.
-- **For large files (rough threshold: >200 lines OR >5K tokens of content)**, default to one of these strategies instead of one giant \`write_file\`:
-  - **Skeleton + edit**: \`write_file\` a small skeleton (head + placeholders), then call \`edit_file\` repeatedly to append/replace sections — each edit stays well under the cap, and partial progress survives a stream error.
-  - **Shell heredoc**: \`run_command\` with \`cat > path <<'EOF' ... EOF\` (bash) or \`Set-Content -Path ... -Value @"..."@\` (PowerShell) — the file content bypasses the model's JSON output entirely, so no token cap applies. Prefer this for generated/structured content (JSON config, full HTML pages, large code dumps).
-- For small files (≤200 lines, ≤5K tokens) just use \`write_file\` directly — no need to over-engineer.
+- Use existing conversation and tool evidence before gathering more. Inspect only what supports the next decision; do not guess.
+- Keep changes focused. After modifications, run the smallest relevant executable verification and report its result.
+- Use web search only when freshness materially affects the answer.
+${buildCodegraphSection()}
 
-## Failure Handling
-- Tools return errors as strings (edit_file no match or non-unique, run_command non-zero exit, etc.). Analyze the root cause, adjust, then retry — don't resend the same call verbatim.
-- When a command errors, read the actual output before judging; don't skip it.
+## Tool use
+- Go directly to a known path or symbol; use discovery tools only when the location is unknown.
+- Before an edit, use fresh exact file content and its hash. A mutation, compaction, resume, conflict, or external change makes prior edit context stale.
+- Batch only independent calls. Never batch a read with an edit that depends on it; do not repeat overlapping reads or unchanged failed calls.
+- On failure, inspect the full error, change the approach, and retry only with a reason. Drop stale tool output when it no longer supports the task.
+- For generated content over roughly 200 lines or 5K tokens, use small staged writes rather than one oversized tool argument.
+- Use \`ask_human\` only for a genuinely user-owned decision; otherwise choose the safest reversible option and proceed.
 
 ## Safety & Boundaries
-- Confirm with the user before irreversible or outward-facing operations (delete, overwrite existing files, push, request external services), unless explicitly authorized.
-- Operate only within authorized scope; when unsure, ask — don't guess.
+- Get confirmation before irreversible or outward-facing actions such as deletion, push, production changes, or external requests, unless explicitly authorized.
+- Stay within the authorized workspace and disclose anything skipped or unverifiable.
 
 ## Project context (dynamic reference)
-${buildSnapshotSection()}${config.projectSkillEnabled ? buildProjectSkillSection() : ''}${memorySection}${buildNotepadSection(sessionId)}
-
-## Session Notepad — working notes file
-${sessionId
-        ? `You maintain a working notepad at \`.mocode/sessions/${sessionId}/notes.md\` using write_file / edit_file / read_file.`
-        : 'You maintain a working notepad (path will be shown after the session starts).'}
-This is your private working surface — write intermediate findings, decisions, open questions,
-and anything you might need to recall later. The file survives context compaction.
-
-### WHEN TO WRITE
-The notepad is opt-in for complex work, not a routine task log. Use it only when the task has at least 3 meaningful steps, spans multiple investigation/implementation phases, or contains details that are genuinely at risk of being lost to context compaction.
-
-Do NOT create, read, or update the notepad for simple tasks, including:
-- Questions that can be answered directly
-- One-step commands or lookups
-- Small, localized edits that can be completed without intermediate notes
-- Work that only needs a few tool calls and fits comfortably in the current context
+${memorySection}${buildNotepadSection(sessionId)}
 
-For qualifying complex work:
-- After exploring code and discovering key constraints → add a section
-- Before making a consequential design decision → record reasoning and alternatives considered
-- When accumulating data across many tool calls → store concise intermediates
-- When you realize important information may be lost after compaction → write it down
-- After completing a substantial phase → summarize what you learned
+## Session Notepad (\`.mocode/sessions/${sessionId ?? '<id>'}/notes.md\`)
+Use this compact, persistent working surface for tasks with at least three steps or context-loss risk; skip it for simple work.
 
-### FORMAT (markdown, section-based)
-Use \`## <topic>\` headers to organize. Each section is self-contained.
-Example:
-
-    ## Auth Module
-    - JWT TTL: 86400s, hardcoded at src/auth/jwt.ts:42
-    - Config path: config.auth.jwt.ttl (does not exist yet)
-    - Migration: read from config with fallback to 86400
-
-    ## Decision: Schema Validation
-    - Chose: zod over joi
-    - Why: project already uses zod (config/index.ts:8), joi would add a dep
-    - Risk: none — zod already in dependency tree
-
-    ## Open Questions
-    - [ ] Does the refresh token flow need TTL config too?
-    - [ ] Check if rate limiter interacts with auth middleware
-
-### RULES
-${sessionId
-        ? `- Your notepad file path is: \`.mocode/sessions/${sessionId}/notes.md\`. Use this exact path for all read_file/write_file/edit_file operations on your notes.`
-        : '- Your notepad file path will be available after the session starts.'}
-- Use write_file to create/overwrite; use edit_file to append or modify sections
-- Keep the file concise — summarize, don't dump raw tool output
-- At task completion, the file can be deleted or left for the user's reference
-- Do NOT use this for cross-session knowledge (use memory_save for that)
-
-### PLAN FORMAT (use for any task with ≥3 steps)
-Write the plan as a top-level \`## Plan:\` section. The system extracts this for the status bar chip, so follow the format exactly.
-
-    ## Plan: <task title>
-
-    Goal: <one-line goal>
-
-    ### Steps
-    - [ ] 1. <step 1>
-    - [x] 2. <step 2>
-    - [ ] 3. <step 3>
-
-    ### Progress
-    - <what you learned / did in this phase>
-
-Rules:
-- Only ONE active \`## Plan:\` section at a time.
-- Mark steps \`[x]\` as you complete them; append a line to \`### Progress\` after each phase.
-- Before your final response, reconcile every step with the work actually completed, then delete the plan section or rename it to \`## Done: <title>\`.
-- The host hides an unchanged active plan when an agent turn ends as a safety fallback; this does not edit the notepad. Keep updating the plan during execution so live progress remains accurate.
+Keep at most one active plan:
+\`\`\`
+## Plan: <title>
+Goal: <outcome>
+### Steps
+- [ ] 1. <verifiable step>
+### Progress
+- <completed phase and evidence>
+\`\`\`
+Update checkboxes and Progress after each completed phase. Before the final reply, reconcile the plan with actual work, then rename it to \`## Done:\` or remove it. Keep other notes concise and session-specific; use memory for stable cross-session facts.
 
 ## Termination & Reporting
 - Stop immediately when no more tools are needed; give conclusions directly.
@@ -394,10 +289,8 @@ export const config = {
     theme: process.env.MOCODE_THEME || 'default',
     themeFromShell,
     llmKeysFromShell,
-    projectSnapshotEnabled: process.env.MOCODE_PROJECT_SNAPSHOT !== 'false',
     permissionEnabled: process.env.MOCODE_PERMISSION !== 'false',
     permissionNonInteractiveAllow: process.env.MOCODE_PERMISSION_NON_INTERACTIVE_ALLOW === 'true',
-    projectSkillEnabled: process.env.MOCODE_PROJECT_SKILL === 'true',
 };
 /**
  * 运行时更新模型相关配置(/model 命令调)。
@@ -442,6 +335,32 @@ export function updateSubAgentConfig(enabled) {
 export function isMemoryEnabled() {
     return config.memoryEnabled;
 }
+/**
+ * .codegraph/ 索引存在性:仅查 cwd 顶层 .codegraph(目录或文件均可,codegraph CLI
+ * 自己会处理内部布局)。用于动态决定是否在系统提示里注入 codegraph skill 用法段——
+ * 没有索引的项目不应被提示「用 codegraph」以免 LLM 调出失败。失败静默返 false。
+ */
+export function hasCodegraphIndex() {
+    try {
+        return fs.existsSync(path.join(process.cwd(), '.codegraph'));
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * 当 .codegraph/ 存在时拼进 auto 模式系统提示的 codegraph 段;否则返空串(零成本)。
+ * 单一来源:被 buildBasePrompt 注入,确保 basePrompt 不含死字符串。
+ */
+export function buildCodegraphSection() {
+    if (!hasCodegraphIndex())
+        return '';
+    return [
+        '',
+        '## Codegraph (project has .codegraph/ index)',
+        '- For unfamiliar code questions, prefer loading the `codegraph` skill (via use_skill) and querying it with run_command (`codegraph explore <entry>`, `codegraph node <symbol>`). Falls back to read_file / glob / grep when not applicable.',
+    ].join('\n');
+}
 /**
  * 切换记忆子系统开关(/memory_switch on|off 调)。
  * - 更新 config 单例字段(其它模块下次调 isMemoryEnabled() 即拿新值)。
@@ -457,34 +376,6 @@ export function updateMemoryConfig(enabled) {
     config.memoryEnabled = enabled;
     process.env.MEMORY_ENABLED = enabled ? 'true' : 'false';
 }
-/**
- * 项目专属 Skill 总开关:单一来源。/project_skill、buildBasePrompt、
- * tools/builtins/index.ts 都从这里查。默认 false(零侵入)。
- */
-export function isProjectSkillEnabled() {
-    return config.projectSkillEnabled;
-}
-/**
- * 切换项目专属 Skill 开关(/project_skill on|off 调)。
- * - 更新 config 单例字段(其它模块下次调 isProjectSkillEnabled() 即拿新值)。
- * - 同步 process.env.MOCODE_PROJECT_SKILL(下次启动 loadEnvFiles 不被文件回填)。
- * 持久化(写 ~/.mocode/config 的 MOCODE_PROJECT_SKILL 键)由调用方走 writeConfigKeys。
- */
-export function updateProjectSkillConfig(enabled) {
-    config.projectSkillEnabled = enabled;
-    process.env.MOCODE_PROJECT_SKILL = enabled ? 'true' : 'false';
-}
-/**
- * 切换项目快照开关(/snapshot on|off 调)。
- * - 更新 config 单例字段(其它模块下次读 config.projectSnapshotEnabled 即拿新值:
- *   buildSnapshotSection 现拼现读、read-file 每次 execute 现读)。
- * - 同步 process.env.MOCODE_PROJECT_SNAPSHOT(下次启动 loadEnvFiles 不会被文件回填)。
- * 持久化(写 ~/.mocode/config 的 MOCODE_PROJECT_SNAPSHOT 键)由调用方走 updateConfigKey。
- */
-export function updateSnapshotConfig(enabled) {
-    config.projectSnapshotEnabled = enabled;
-    process.env.MOCODE_PROJECT_SNAPSHOT = enabled ? 'true' : 'false';
-}
 /** 切换界面与模型回复语言；持久化由 REPL 调用 config/file.ts 完成。 */
 export function updateLanguageConfig(language) {
     setLanguage(language);

package/dist/context/artifacts.js

@@ -40,7 +40,7 @@ function callArgs(history, idx) {
 function sourceType(tool) {
     if (tool === 'read_file')
         return 'read';
-    if (tool === 'grep' || tool === 'glob' || tool === 'codegraph')
+    if (tool === 'grep' || tool === 'glob')
         return 'search';
     if (tool === 'run_command')
         return 'diagnostic';
@@ -53,7 +53,7 @@ function pathsFromOutput(tool, output) {
         if (normalized)
             paths.add(normalized);
     };
-    if (tool === 'grep' || tool === 'codegraph' || tool === 'run_command') {
+    if (tool === 'grep' || tool === 'run_command') {
         const expression = /^(.+?\.[A-Za-z0-9]+):(?:\d+|\s*\d+\s*(?:处匹配|matches?))/gmi;
         let match;
         while ((match = expression.exec(output)))

package/dist/context/classifier.js

@@ -1,21 +1,19 @@
 // Context Classifier:据工具名(强先验)+ 输出形状(启发)+ 兜底,选 ContextKind。
 //
 // 三级信号:
-//  1) 名字强先验(BY_NAME 表,覆盖全部 17 内置工具,确定性强)。
+//  1) 名字强先验(BY_NAME 表,覆盖全部内置工具,确定性强)。
 //  2) 形状启发(为 MCP 工具 / 未来工具 / 未登记工具兜底识别)。
 //  3) 兜底 'passthrough'(不认识 = 不动,零行为变化)。
 //
 // 单一事实源风格(仿 tools/constants.ts 的 READ_TOOL_NAMES / PLAN_DISABLED_TOOLS)。
 // 加新工具:在 BY_NAME 加一行;或靠形状启发自动识别。
-/** 工具名 → ContextKind 的强先验表(覆盖全部 18 内置工具)。 */
+/** 工具名 → ContextKind 的强先验表(覆盖全部内置工具)。 */
 const BY_NAME = {
     // tree:路径列表 → 缩进树
     glob: 'tree',
     // search:file:line 分组
     grep: 'search',
     web_search: 'search',
-    // graph:CLI dump → 精炼图
-    codegraph: 'graph',
     // log:分级 / 折叠 / 尾偏置
     run_command: 'log',
     // code:保行号(edit_file 依赖,最敏感)
@@ -31,7 +29,6 @@ const BY_NAME = {
     edit_file: 'status',
     write_file: 'status',
     ask_human: 'status',
-    switch_mode: 'status',
     drop_context: 'status',
     memory_save: 'status',
     memory_update: 'status',
@@ -47,7 +44,7 @@ function classifyByShape(output) {
     // file:line: content 形(grep 风格)
     if (/^[^\n:]+:\d+:[^\n]*$/m.test(output))
         return 'search';
-    // [退出码 N] 前缀(run_command / codegraph 风格)
+    // [退出码 N] 前缀(run_command 风格)
     if (/^\[退出码 \d+\]/m.test(output))
         return 'log';
     // 路径列表:多行都是含分隔符的相对路径(glob 风格)

package/dist/context/encoders/_util.js

@@ -6,8 +6,9 @@ export function stripAnsi(s) {
 }
 /**
  * 折叠连续空行(只含空白字符的行)≥ threshold → 单个空行。
- * 用于 prose / source dump(web_fetch / use_skill / task / codegraph):HTML→文本与 markdown 常留多余空行,
+ * 用于 prose / source dump(web_fetch / use_skill / task):HTML→文本与 markdown 常留多余空行,
  * 多空行与单空行语义等价,折叠无损。默认 threshold=3(只动真正过量的空行,常见 ≤2 空行不动)。
+ * 注:codegraph 已 skill 化(用 run_command 调 CLI,落到 log encoder),graph kind 现仅作保留值。
  *
  * 注意:用 `.trim() === ''` 判空——故 read_file 的 `     2\t`(行号前缀 + tab,trim 后剩 `2`)不会被
  * 视作空行。read_file 的空行折叠见 code encoder(前缀感知)。

package/dist/context/encoders/index.js

@@ -4,8 +4,9 @@
 // Phase 2:tree / search / log / table / memory(高价值低风险)。
 // Phase 2.5:code / graph / doc / summary(覆盖剩余有 encoder 的 kind)。
 //   - code(read_file):仅折叠 ≥3 连续空行,行号保真(edit_file 依赖)。
-//   - graph(codegraph)/ doc(web_fetch, use_skill)/ summary(task):去 ANSI + 折叠空行,保守不重构结构。
-//   - status(edit/write/ask_human/switch_mode/mem 增删改)无 encoder:本就是一行,无需编码。
+//   - graph(保留 kind,暂无 builtin 工具直接命中)/ doc(web_fetch, use_skill)/ summary(task):
+//     去 ANSI + 折叠空行,保守不重构结构。
+//   - status(edit/write/ask_human/mem 增删改)无 encoder:本就是一行,无需编码。
 //
 // 加 encoder:新建 encoders/xxx.ts 导出 ContextEncoder,在此数组加一行。无需动 agent / llm / core。
 import { passthroughEncoder } from './passthrough.js';
@@ -15,7 +16,6 @@ import { commandEncoder } from './command.js';
 import { tableEncoder } from './table.js';
 import { memoryEncoder } from './memory.js';
 import { codeEncoder } from './code.js';
-import { graphEncoder } from './graph.js';
 import { docEncoder } from './doc.js';
 import { summaryEncoder } from './summary.js';
 export const builtinEncoders = [
@@ -26,7 +26,6 @@ export const builtinEncoders = [
     tableEncoder,
     memoryEncoder,
     codeEncoder,
-    graphEncoder,
     docEncoder,
     summaryEncoder,
 ];

package/dist/context/lifecycle.js

@@ -1,7 +1,7 @@
 // Observation Lifecycle Engine:tool 消息的「观察者生命周期」状态机。
 //
 // 在 Relevance Pruner 之上的第二层被动裁剪。Relevance Pruner 只管 read_file 的「同 path 新旧替换 +
-// mutation 覆写」,本层补足「grep/glob/codegraph 这类观察类工具」的引用追踪。
+// mutation 覆写」,本层补足「grep/glob/web_search/web_fetch 这类观察类工具」的引用追踪。
 //
 // 四态机(LIVE → REFERENCED → OBSOLETE → STUB):
 //   - LIVE:刚 push 进 history 的工具结果,尚未被任何下游工具消费。
@@ -10,7 +10,7 @@
 //   - STUB:已被替换为存根(物理上 content 变成「⌦[无消费者:...]」)。
 //
 // 观察类工具两阶段衰减(避免误伤):
-//   - grep/glob/codegraph/web_search/web_fetch 等「观察/检索类」工具两阶段衰减:
+//   - grep/glob/web_search/web_fetch 等「观察/检索类」工具两阶段衰减:
 //     Phase 1(10 步):LIVE → REFERENCED,保留完整内容(返回多个候选,剩余候选可能后续被消费)。
 //     Phase 2(+5 步):REFERENCED → DIGEST,替换为摘要存根(保留文件列表+命中数+参数,丢弃详情),
 //     释放 ~90% token。states 仍为 REFERENCED,不引入新状态。
@@ -34,7 +34,6 @@ import { canonicalizePath, extractPath, isToolResultSuccess, lastUserIndex, toTe
 const OBSERVER_TOOLS = new Set([
     'grep',
     'glob',
-    'codegraph',
     'web_search',
     'web_fetch',
 ]);
@@ -63,7 +62,6 @@ const OBSERVER_DIGEST_AGE = 5;
  *  - grep:content 是 `file:line: ...` 行,提取每行的 file 段(只保留绝对路径形态或与 pattern 匹配的)。
  *    简化:把所有看起来像「相对路径 + 文件名」的 token 抽出,留 narrow。
  *  - glob:content 是路径列表,按行 / 空格拆。
- *  - codegraph:content 里通常含 `path/to/file.ts:line`,按行拆,提 file 段。
  *
  *  返回值:命中过的 path 字符串集合(已 dedup)。失败返空集。 */
 function extractProducerPaths(toolName, content) {
@@ -99,14 +97,6 @@ function extractProducerPaths(toolName, content) {
                     addPath(t);
             }
         }
-        else if (toolName === 'codegraph') {
-            // codegraph 输出通常 `path\to\file.ts:line:col  symbol` 或类似;按行 + 冒号分隔。
-            for (const line of content.split(/\r?\n/)) {
-                const m = /^([^\s:][^:]*?\.[A-Za-z0-9]+):(\d+):/.exec(line);
-                if (m)
-                    addPath(m[1]);
-            }
-        }
         else if (toolName === 'web_search' || toolName === 'web_fetch') {
             // 网络结果不在文件系统路径范畴;不参与 producer 路径索引(避免误匹配)。
         }
@@ -287,7 +277,7 @@ export class LifecycleEngine {
                 })();
                 const path = canonicalizePath(extractPath(argsRaw));
                 if (path) {
-                    // 1) 找该 path 的所有上游 producer(grep/glob/codegraph)→ 标 REFERENCED。
+                    // 1) 找该 path 的所有上游 producer(grep/glob/web_search/web_fetch)→ 标 REFERENCED。
                     const producers = this.producersByPath.get(path);
                     if (producers) {
                         for (const pidx of producers) {
@@ -478,16 +468,6 @@ export class LifecycleEngine {
                 } })();
                 return `${DIGEST_PREFIX}glob(${args}) — 历史结果文件 ${files}，${origLen}→摘要]\n如需完整列表或最新信息请重新调用 glob`;
             }
-            case 'codegraph': {
-                const args = (() => { try {
-                    const a = JSON.parse(argsRaw);
-                    return `"${a.query ?? ''}"`;
-                }
-                catch {
-                    return '...';
-                } })();
-                return `${DIGEST_PREFIX}codegraph(${args}) — 历史结果文件 ${files}，${origLen}→摘要]\n如需完整详情或最新信息请重新调用 codegraph`;
-            }
             case 'web_search': {
                 // 统计结果数
                 let resultCount = 0;