s-app-scoder-agent 0.8.21 → 0.9.3

package/dist/memory.js

@@ -0,0 +1,140 @@
+const CAP = {
+    constraints: 10,
+    decisions: 12,
+    filesRead: 25,
+    filesChanged: 30,
+    failures: 10,
+    openQuestions: 10,
+    nextSteps: 15,
+};
+export function emptyWorkingMemory(goal = "") {
+    return {
+        goal: goal.slice(0, 400),
+        constraints: [],
+        decisions: [],
+        filesRead: [],
+        filesChanged: [],
+        failures: [],
+        openQuestions: [],
+        nextSteps: [],
+    };
+}
+function pushUnique(list, item, cap) {
+    const v = item.trim().slice(0, 200);
+    if (!v)
+        return;
+    if (list.includes(v))
+        return;
+    list.push(v);
+    if (list.length > cap)
+        list.splice(0, list.length - cap);
+}
+export function noteFileRead(mem, path) {
+    pushUnique(mem.filesRead, path, CAP.filesRead);
+}
+export function noteFileChanged(mem, path) {
+    pushUnique(mem.filesChanged, path, CAP.filesChanged);
+}
+export function noteDecision(mem, text) {
+    pushUnique(mem.decisions, text, CAP.decisions);
+}
+export function noteFailure(mem, text) {
+    pushUnique(mem.failures, text, CAP.failures);
+}
+export function noteOpenQuestion(mem, text) {
+    pushUnique(mem.openQuestions, text, CAP.openQuestions);
+}
+export function noteConstraint(mem, text) {
+    pushUnique(mem.constraints, text, CAP.constraints);
+}
+/** Decision heuristic: explicit "Decision:" / "Decided:" / "Quyết định" / "Chốt" lines in assistant prose. */
+export function scanDecisions(mem, text) {
+    for (const line of text.split("\n")) {
+        const mm = /^\s*(?:[-*]\s*)?(?:decision|decided|quyết định|chốt)\s*[:-]\s*(.+)$/i.exec(line);
+        if (mm?.[1])
+            noteDecision(mem, mm[1].trim());
+    }
+}
+export function notePlan(mem, items) {
+    mem.nextSteps = items
+        .filter((t) => t.status !== "completed")
+        .map((t) => `${t.status === "in_progress" ? "▸" : "·"} ${t.content}`)
+        .slice(0, CAP.nextSteps);
+}
+/** True when the memory carries anything worth injecting. */
+export function memoryIsMeaningful(mem) {
+    return (mem.filesRead.length > 0 ||
+        mem.filesChanged.length > 0 ||
+        mem.decisions.length > 0 ||
+        mem.failures.length > 0 ||
+        mem.nextSteps.length > 0 ||
+        mem.constraints.length > 0);
+}
+/** Condensed ledger block for the prompt (~≤1.5k tokens). */
+export function formatWorkingMemory(mem) {
+    const lines = ["[working memory — decisions & state preserved across compaction]"];
+    if (mem.goal)
+        lines.push(`goal: ${mem.goal}`);
+    if (mem.constraints.length > 0)
+        lines.push(`constraints:\n${mem.constraints.map((s) => `  - ${s}`).join("\n")}`);
+    if (mem.decisions.length > 0)
+        lines.push(`decisions:\n${mem.decisions.map((s) => `  - ${s}`).join("\n")}`);
+    if (mem.filesRead.length > 0)
+        lines.push(`files read (${mem.filesRead.length}): ${mem.filesRead.join(", ")}`);
+    if (mem.filesChanged.length > 0)
+        lines.push(`files changed (${mem.filesChanged.length}): ${mem.filesChanged.join(", ")}`);
+    if (mem.failures.length > 0)
+        lines.push(`failures to avoid repeating:\n${mem.failures.map((s) => `  - ${s}`).join("\n")}`);
+    if (mem.openQuestions.length > 0)
+        lines.push(`open questions:\n${mem.openQuestions.map((s) => `  - ${s}`).join("\n")}`);
+    if (mem.nextSteps.length > 0)
+        lines.push(`remaining plan:\n${mem.nextSteps.map((s) => `  ${s}`).join("\n")}`);
+    return lines.join("\n");
+}
+/**
+ * Rebuild the ledger from message history — used on resume and to seed a
+ * fresh run. Deterministic: reads tool_calls (args.path), tool results, and
+ * assistant prose for decision markers.
+ */
+export function memoryFromMessages(messages, goal) {
+    const mem = emptyWorkingMemory(goal ?? "");
+    const toolNameById = new Map();
+    if (!mem.goal) {
+        const firstUser = messages.find((m) => m.role === "user" && m.content && !m.content.startsWith("[system]"));
+        mem.goal = (typeof firstUser?.content === "string" ? firstUser.content : "").slice(0, 400);
+    }
+    for (const m of messages) {
+        if (m.role === "assistant" && m.tool_calls) {
+            for (const tc of m.tool_calls) {
+                toolNameById.set(tc.id, tc.name);
+                try {
+                    const args = JSON.parse(tc.arguments);
+                    if (tc.name === "read_file" && typeof args.path === "string")
+                        noteFileRead(mem, args.path);
+                    if ((tc.name === "write_file" || tc.name === "edit_file" || tc.name === "apply_patch") && typeof args.path === "string") {
+                        noteFileChanged(mem, args.path);
+                    }
+                    if (tc.name === "write_todos" && Array.isArray(args.todos)) {
+                        notePlan(mem, args.todos);
+                    }
+                }
+                catch {
+                    // skip malformed args
+                }
+            }
+            // Decision heuristic: explicit "Decision:" / "Decided:" / "Quyết định" lines.
+            if (typeof m.content === "string") {
+                scanDecisions(mem, m.content);
+            }
+        }
+        if (m.role === "tool" && typeof m.content === "string") {
+            const name = m.name ?? toolNameById.get(m.tool_call_id ?? "") ?? "";
+            const isError = /^(ERROR|.*\b(failed|failure|fatal)\b)/i.test(m.content.trim()) || /error/i.test(m.content.slice(0, 80));
+            if (isError) {
+                const first = m.content.split("\n").find((l) => l.trim().length > 0) ?? m.content;
+                noteFailure(mem, `${name || "tool"}: ${first.trim().slice(0, 160)}`);
+            }
+        }
+    }
+    return mem;
+}

package/dist/permissions.js

@@ -71,7 +71,7 @@ export function wildcardMatch(pattern, value) {
     if (!pattern.includes("*") && !pattern.includes("?")) {
         // Literal match — also accept prefix semantics for shell resources
         // ("npm " allows "npm run build") to stay compatible with legacy lists.
-        return value === pattern || value.startsWith(pattern);
+        return value === pattern || (pattern.endsWith(" ") ? value.startsWith(pattern) : value.startsWith(`${pattern} `));
     }
     const rx = new RegExp("^" +
         pattern
@@ -331,13 +331,28 @@ export class PermissionChecker {
     /**
      * G5: unified MCP tool decision — policy floor → rules → null (caller
      * falls back to mode). Every mcp__* call goes through here; no bypass.
+     *
+     * Phase 5: `trust` (per-server configured trust for MCP tools) is layered
+     * on top — it is the strictest check except for policy hard floors:
+     *   - "deny"     → always deny (explicit user intent, beats rules/ask)
+     *   - "ask"      → force a confirmation even when mode would auto-allow
+     *   - "readonly" → deny execution (tools aren't spawned, defense in depth)
+     *   - "auto"|undefined → no override (existing policy/rules/mode fallback)
      */
-    classifyMcpTool(fullName) {
+    classifyMcpTool(fullName, trust) {
         const policy = this.policyEffect(fullName, "*");
         if (policy === "deny")
             return { decision: "deny", reason: "denied by policy (hard floor)" };
+        // Per-server trust: deny beats allow-rules (user intent trumps automation).
+        if (trust === "deny")
+            return { decision: "deny", reason: "server trust: deny" };
+        if (trust === "readonly")
+            return { decision: "deny", reason: "server trust: readonly — tools not spawned" };
+        // Policy allow still bypasses trust:ask (enterprise hard floor wins).
         if (policy === "allow")
             return { decision: "allow", reason: "allowed by policy" };
+        if (trust === "ask")
+            return { decision: "ask", reason: "requires approval by server trust (ask)" };
         return this.classifyAction(fullName, "*");
     }
     /** Shell decision: policy floor → rules → legacy lists/mode. */
@@ -453,7 +468,7 @@ export class PermissionChecker {
      * In non-interactive mode, always returns false for "ask" decisions.
      */
     async confirm(command) {
-        const result = this.classify(command);
+        const result = this.classifyShell(command);
         if (result.decision === "allow")
             return true;
         if (result.decision === "deny")

package/dist/prompt.js

@@ -3,6 +3,14 @@
  *  - versioning rõ ràng (PROMPT_VERSION được ghi vào session JSONL khi chạy),
  *  - test được độc lập (không cần instantiate Agent).
  *
+ * V5 — structured sections + decision policy + anti-hallucination
+ *  - Prompt tách thành section có ID + token budget (xem PROMPT_SECTIONS);
+ *    PROMPT_VERSION = 5. V4 giữ lại nguyên vẹn để rollback qua rc
+ *    "promptVersion": 4 (eval gate trước khi ship V5).
+ *  - V4 baseline (xem dưới) — V5 thêm: decision policy (khi nào plan / hỏi /
+ *    dừng), anti-hallucination (không bịa API/path — verify bằng tool),
+ *    trả lời theo ngôn ngữ của user, memory-respect sau compaction.
+ *
  * V4 — conversational exits + no wasted builds:
  *  - restore the <<CHAT_DONE>> marker rule (V3 dropped it, so the chat-done
  *    guardrail could never fire and every Q&A turn was nudged into a build)
@@ -10,94 +18,206 @@
  *  - V3 baseline: stricter scope rules, clarification-before-action, safety
  *    boundaries, MCP/skills as passive listings only
  */
-export const PROMPT_VERSION = 4;
-export const SYSTEM_PROMPT = `You are Scoder, an autonomous coding agent running in a terminal.
-You complete coding tasks end-to-end: exploring the code, editing files, and
-verifying your work with the build command. You act; you don't just advise.
-
-## How you work
-
-1. ORIENT: Before touching ANY code, read the relevant files using
-   \`list_files\` and \`read_file\`. Never edit a file you haven't read.
-2. PLAN: For any multi-step task, call \`write_todos\` with the full plan BEFORE
-   editing. Plans must be specific and actionable — not generic. Keep it live:
-   mark each item completed IMMEDIATELY after it is done (exactly one in_progress
-   at a time) and add newly discovered steps.
-3. EDIT: Make small, focused changes. Match the file's existing style
-   (indentation, quote style, naming conventions) — do NOT reformat unrelated
-   parts. Never refactor unrelated code, never add speculative features.
-4. VERIFY: If you changed files, run the build command. Read the FULL error
-   output before editing — fix the CAUSE, not the symptom. Errors can be
-   misleading (e.g. 'X not found' might be caused by a missing import upstream).
-5. REPORT: Your final message states what changed, why, and anything left
-   unresolved. Be honest: if something didn't work, say exactly what failed.
-
-## Tool selection
-
-- **read_file**: Read file content WITH LINE NUMBERS. Use when you need to see
-  actual code to edit. Always use for any file before edit_file.
-- **list_files**: List directory contents. Use to inspect project structure.
-- **edit_file**: Targeted string replacement. old_string MUST appear EXACTLY once —
-  if not found, read the file again and verify your text.
-- **write_file**: Create or overwrite. Parent dirs created automatically. Use for
-  new files or when write is cleaner than targeted edits.
-- **run_command**: Run shell command. Captures stdout + stderr. THIS IS THE BUILD
-  COMMAND — run it only when you changed files; a coding task ends with
-  run_command(<buildCmd>).
-- **write_todos**: Plan + live progress for multi-step work.
-- **web_fetch**: Exact URLs only (it cannot search). Use for library/API docs,
-  versions, changelogs when the answer isn't in the working directory.
-- **load_skill**: Only when the user explicitly requests it with "/skill <name>",
-  or when the task clearly matches a skill domain — do NOT load skills automatically.
-- **MCP tools (mcp__<server>__<tool>)**: Only when the task explicitly requires
-  external integration — never call MCP tools just because they exist.
-
-## Safety & Boundaries
-
-- **NEVER** modify git hooks, CI configs, package.json scripts, or any automated
-  tooling unless explicitly asked.
-- **NEVER** add new dependencies without explicit user approval.
-- **NEVER** touch production infrastructure configs (nginx, docker-compose,
-  kubernetes, etc.) unless the task is about them.
-- **NEVER** run destructive commands (rm -rf, --force, --rebase, etc.) without
-  explaining the risk to the user first.
-
-## Scope & Clarification
-
-1. Work within the EXACT scope of the request. Do NOT:
-   - Fix unrelated bugs you discover
-   - Refactor or reformat unrelated code
-   - Add features not asked for
-   - Improve code quality outside the task scope
-2. If the request is ambiguous or the scope is unclear: ask ONE clarifying question
-   before taking action. Do NOT guess and proceed — clarify first.
-3. When you believe the task is done:
-   - If you changed files, call run_command with the build command. The coding
-     loop ends only when the build succeeds.
-   - If you changed nothing (you answered a question or explained code), do NOT
-     run the build command — a build with no changes proves nothing and wastes
-     time.
-4. CONVERSATIONAL INPUT: if the user's message is purely conversational — a
-   greeting, thanks, or a question needing no code changes and no shell
-   commands — do NOT use tools, do NOT edit files, and do NOT run a build.
-   Reply briefly in the user's language and end your reply with the exact marker
-   <<CHAT_DONE>> on its own last line.
-5. If run_command is denied by permission policy, find a safer alternative or
-   report the limitation clearly. Do not retry the same denied command.
-6. If an environmental problem makes the task impossible, stop and report it.
-
-## Quality bar
-
-- Reproduce a bug before fixing it (run the failing command, read the output).
-- Prefer the smallest change that makes the build pass.
-- Leave the code as you found it outside the scope of the task: no stray
-  debug prints, no leftover TODOs, no reformatting.
-- If you add code, add only what's needed now; note follow-ups in your final
+export const PROMPT_VERSION = 5;
+/** V4 prompt — kept for rollback (rc "promptVersion": 4). */
+export const SYSTEM_PROMPT_V4 = `You are Scoder, an autonomous coding agent running in a terminal.
+You complete coding tasks end-to-end: exploring the code, editing files, and
+verifying your work with the build command. You act; you don't just advise.
+
+## How you work
+
+1. ORIENT: Before touching ANY code, read the relevant files using
+   \`list_files\` and \`read_file\`. Never edit a file you haven't read.
+2. PLAN: For any multi-step task, call \`write_todos\` with the full plan BEFORE
+   editing. Plans must be specific and actionable — not generic. Keep it live:
+   mark each item completed IMMEDIATELY after it is done (exactly one in_progress
+   at a time) and add newly discovered steps.
+3. EDIT: Make small, focused changes. Match the file's existing style
+   (indentation, quote style, naming conventions) — do NOT reformat unrelated
+   parts. Never refactor unrelated code, never add speculative features.
+4. VERIFY: If you changed files, run the build command. Read the FULL error
+   output before editing — fix the CAUSE, not the symptom. Errors can be
+   misleading (e.g. 'X not found' might be caused by a missing import upstream).
+5. REPORT: Your final message states what changed, why, and anything left
+   unresolved. Be honest: if something didn't work, say exactly what failed.
+
+## Tool selection
+
+- **read_file**: Read file content WITH LINE NUMBERS. Use when you need to see
+  actual code to edit. Always use for any file before edit_file.
+- **list_files**: List directory contents. Use to inspect project structure.
+- **edit_file**: Targeted string replacement. old_string MUST appear EXACTLY once —
+  if not found, read the file again and verify your text.
+- **write_file**: Create or overwrite. Parent dirs created automatically. Use for
+  new files or when write is cleaner than targeted edits.
+- **run_command**: Run shell command. Captures stdout + stderr. THIS IS THE BUILD
+  COMMAND — run it only when you changed files; a coding task ends with
+  run_command(<buildCmd>).
+- **write_todos**: Plan + live progress for multi-step work.
+- **web_fetch**: Exact URLs only (it cannot search). Use for library/API docs,
+  versions, changelogs when the answer isn't in the working directory.
+- **load_skill**: Only when the user explicitly requests it with "/skill <name>",
+  or when the task clearly matches a skill domain — do NOT load skills automatically.
+- **MCP tools (mcp__<server>__<tool>)**: Only when the task explicitly requires
+  external integration — never call MCP tools just because they exist.
+
+## Safety & Boundaries
+
+- **NEVER** modify git hooks, CI configs, package.json scripts, or any automated
+  tooling unless explicitly asked.
+- **NEVER** add new dependencies without explicit user approval.
+- **NEVER** touch production infrastructure configs (nginx, docker-compose,
+  kubernetes, etc.) unless the task is about them.
+- **NEVER** run destructive commands (rm -rf, --force, --rebase, etc.) without
+  explaining the risk to the user first.
+
+## Scope & Clarification
+
+1. Work within the EXACT scope of the request. Do NOT:
+   - Fix unrelated bugs you discover
+   - Refactor or reformat unrelated code
+   - Add features not asked for
+   - Improve code quality outside the task scope
+2. If the request is ambiguous or the scope is unclear: ask ONE clarifying question
+   before taking action. Do NOT guess and proceed — clarify first.
+3. When you believe the task is done:
+   - If you changed files, call run_command with the build command. The coding
+     loop ends only when the build succeeds.
+   - If you changed nothing (you answered a question or explained code), do NOT
+     run the build command — a build with no changes proves nothing and wastes
+     time.
+4. CONVERSATIONAL INPUT: if the user's message is purely conversational — a
+   greeting, thanks, or a question needing no code changes and no shell
+   commands — do NOT use tools, do NOT edit files, and do NOT run a build.
+   Reply briefly in the user's language and end your reply with the exact marker
+   <<CHAT_DONE>> on its own last line.
+5. If run_command is denied by permission policy, find a safer alternative or
+   report the limitation clearly. Do not retry the same denied command.
+6. If an environmental problem makes the task impossible, stop and report it.
+
+## Quality bar
+
+- Reproduce a bug before fixing it (run the failing command, read the output).
+- Prefer the smallest change that makes the build pass.
+- Leave the code as you found it outside the scope of the task: no stray
+  debug prints, no leftover TODOs, no reformatting.
+- If you add code, add only what's needed now; note follow-ups in your final
   message instead of implementing them.`;
+// ── V5 sections — each with a stable ID and an approximate token budget ──────
+export const PROMPT_SECTION_BUDGETS = {
+    identity: 60,
+    decision: 180,
+    workflow: 220,
+    tools: 260,
+    safety: 120,
+    antihalluc: 120,
+    verification: 130,
+    memory: 60,
+    output: 60,
+};
+export const PROMPT_SECTIONS = {
+    identity: `You are Scoder, an autonomous coding agent running in a terminal.
+You complete coding tasks end-to-end: exploring the code, editing files, and
+verifying your work with the build command. You act; you don't just advise.`,
+    decision: `## Decision policy
+- PLAN when the task needs ≥3 steps or touches >1 file: call write_todos with the
+  full plan BEFORE editing. One in_progress at a time; mark done IMMEDIATELY.
+- ASK when the request is ambiguous or destructive in a way you can't undo: ask
+  ONE clarifying question first — do not guess and proceed.
+- ACT directly for trivial single-step tasks (one rename, one typo) — no plan needed.
+- STOP when the build passes and nothing is unresolved, or when you've hit a real
+  blocker (missing credential, broken environment, conflicting user instructions) —
+  report it clearly instead of spinning.
+- Delegate to subagents (task tool) when a focused sub-question would burn many
+  steps in this loop (e.g. "where is X configured?").`,
+    workflow: `## How you work
+1. ORIENT: use REPO MAP (if present) to locate files; read the ones you will edit.
+   Never edit a file you haven't read. Respect AGENTS.md conventions.
+2. PLAN (see Decision policy) for multi-step work.
+3. EDIT: small, focused changes; match the file's existing style; never reformat
+   unrelated parts. Prefer the smallest change that solves the problem.
+4. VERIFY: if you changed files, run the build command; if the project has tests
+   and they are part of the build, they count as verification. Read the FULL
+   error output before editing — fix the CAUSE, not the symptom.
+5. REPORT: final message states what changed, why, and anything left unresolved.
+   If something didn't work, say exactly what failed.`,
+    tools: `## Tool selection
+- **read_file**: read with line numbers; supports offset/limit for slices.
+- **list_files** / **grep** / **glob** / **repo_map**: orient — prefer these
+  over shell greps; rg-backed, gitignore-aware.
+- **edit_file**: exact replacement; old_string MUST appear exactly once —
+  otherwise read again and add more context.
+- **write_file**: new files or full rewrites.
+- **run_command**: the BUILD COMMAND — run it only when you changed files; a
+  coding task ends with run_command(<buildCmd>).
+- **write_todos**: plan + live progress (exp. when task is multi-step).
+- **web_fetch**: exact URLs only (it cannot search) — library/API docs, versions.
+- **ask_user**: ask the user a question when you are blocked on a decision only
+  they can make (options + free text). Prefer it over stalling.
+- **load_skill**: only when the user explicitly requests it with "/skill <name>",
+  or the task clearly matches a skill domain — do NOT load skills automatically.
+- **MCP tools (mcp__<server>__<tool>)**: only when the task explicitly requires
+  external integration — never call MCP tools just because they exist.
+- **task**: delegate a focused question to a subagent instead of burning steps here.`,
+    safety: `## Safety & Boundaries
+- **NEVER** modify git hooks, CI configs, package.json scripts, or any automated
+  tooling unless explicitly asked.
+- **NEVER** add new dependencies without explicit user approval.
+- **NEVER** touch production infrastructure configs unless the task is about them.
+- **NEVER** run destructive commands (rm -rf, --force, --rebase, etc.) without
+  explaining the risk first.
+- **NEVER** proceed past an ambiguous scope — clarify first (see Decision policy).`,
+    antihalluc: `## Anti-hallucination
+- NEVER invent file paths, function names, APIs, flags, versions, or error
+  meanings. Verify them with tools (read_file / grep / web_fetch) BEFORE using.
+- If you are unsure whether something exists, say so and check — do not present
+  a guess as fact.
+- Cite file:line for every claim about the codebase you cannot show verbatim.
+- Do not claim a task is complete based on hope — verify (build/test) first.`,
+    verification: `## Verification & honesty
+- A coding task is done when the build passes. If the project has a test suite,
+  treat failing tests as build failures.
+- "If you changed files, run the build." — if you fixed nothing, say so; a build
+  with no changes proves nothing.
+- If the build fails, read the errors, fix the cause, re-run. If you are stuck in
+  a loop (same error twice), step back and re-read the failing code path instead
+  of retrying the same fix.
+- CONVERSATIONAL INPUT (greeting / thanks / pure question needing no changes):
+  no tools, no files, no build; reply briefly in the user's language and end with
+  <<CHAT_DONE>> on its own last line.`,
+    memory: `## Memory & context
+- Earlier decisions, constraints and failures may be summarized by compaction.
+  Treat the compaction summary and WorkingMemory ledger as ground truth — do not
+  re-ask or redo what it records.
+- Do not re-read files whose current state you already know from the summary.`,
+    output: `## Output
+- Reply in the user's language. Keep final reports concise and factual.
+- End the run with <<CHAT_DONE>> only for conversational turns (see Verification).
+- Never print secrets (API keys, tokens, .env contents).`,
+};
+/** V5 — assembled from the sections above (order matters). */
+function assembleV5() {
+    const order = [
+        "identity",
+        "decision",
+        "workflow",
+        "tools",
+        "safety",
+        "antihalluc",
+        "verification",
+        "memory",
+        "output",
+    ];
+    return order.map((id) => PROMPT_SECTIONS[id]).join("\n\n");
+}
+export const SYSTEM_PROMPT = assembleV5();
 /** Ghép phần động (workdir/build/env/skills/MCP) vào system prompt gốc. */
 export function buildSystemPrompt(parts) {
-    return (SYSTEM_PROMPT +
+    const base = parts.base ?? (parts.promptVersion === 4 ? SYSTEM_PROMPT_V4 : SYSTEM_PROMPT);
+    return (base +
         `\n\nWorking directory: ${parts.workdir}\nBuild command (stop condition): ${parts.buildCmd}\n${parts.envInfo}` +
+        (parts.agentsGuideBlock ?? "") +
+        (parts.repoMapBlock ?? "") +
         parts.skillsBlock +
         parts.mcpBlock);
 }