@yeaft/webchat-agent 1.0.355 → 1.0.356

package/local-runtime/version.json

@@ -1 +1 @@
-{"version":"1.0.355"}
+{"version":"1.0.356"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "1.0.355",
+  "version": "1.0.356",
   "description": "Remote worker agent for Yeaft Web Code Agent — connects the native Yeaft engine, CLI providers, and workbench tools",
   "main": "index.js",
   "type": "module",

package/yeaft/templates/tool-guidance.md

@@ -5,11 +5,11 @@
 ## General Rules
 
 - Always read a file before editing it — never edit blind
-- Use the most specific tool for the job: `grep` for content search, `glob` for file patterns, `file-read` for reading
+- Use the most specific tool for the job: the `Grep` tool for content search, `Glob` for file patterns, `FileRead` for reading
 - Prefer editing existing files over creating new ones
 - Use `bash` for shell commands; avoid interactive commands (no `vim`, no `less`, no `git rebase -i`)
 - When output is too large, extract the relevant portion rather than dumping everything
-- **Batch independent tool calls in a single turn.** When the next few steps don't depend on each other's output (e.g. reading three sibling files, or running `grep` + `glob` to triangulate), emit them as parallel tool calls in one assistant turn instead of one-per-turn.
+- **Batch independent tool calls in a single turn.** When the next few steps don't depend on each other's output (e.g. reading three sibling files, or running the `Grep` + `Glob` tools to triangulate), emit them as parallel tool calls in one assistant turn instead of one-per-turn.
 
 ## File Operations
 
@@ -24,15 +24,16 @@
 - Avoid destructive operations without confirmation
 - Quote file paths that contain spaces
 - Set reasonable timeouts for long-running commands
-- Use `rg` (ripgrep) over `grep` for better regex support and speed
+- Use the `Grep` tool for content search — never run `grep` or `rg` inside `bash` for file search. The tool skips binaries and `node_modules`/`.git`, enforces output budgets, and is concurrency-safe; a bare shell `grep` gets none of that
+- Don't edit files with `sed -i`; use the `FileEdit` / `ApplyPatch` tools so changes are precise and reviewable
 
 ## Search Strategy
 
 Pick the shortest path that gets you the answer — don't always start at step 1.
 
-1. **If you already know the file path** → go straight to `file-read` (or `grep` for a pattern within it). Skip `glob`.
-2. **If you know roughly which directory but not the file** → `grep` directly with a `glob` or `type` filter; that's one tool call, not two.
-3. **If you have nothing but a pattern of file names** → start with `glob`, then `grep` / `file-read`.
+1. **If you already know the file path** → go straight to `FileRead` (or the `Grep` tool for a pattern within it). Skip `Glob`.
+2. **If you know roughly which directory but not the file** → use the `Grep` tool directly with a `glob` or `type` filter; that's one tool call, not two.
+3. **If you have nothing but a pattern of file names** → start with `Glob`, then `Grep` / `FileRead`.
 4. Use `bash` only when no dedicated tool can do the job.
 
 When several of these steps are independent (e.g. reading three files you already know the paths of), issue them as **parallel tool calls in one turn**, not three sequential turns.
@@ -80,11 +81,11 @@ or pure conversational/question turns — the checklist becomes noise.
 ## 通用规则
 
 - 编辑文件前必须先读取 — 不要盲目编辑
-- 使用最具体的工具：`grep` 搜索内容、`glob` 搜索文件模式、`file-read` 读取文件
+- 使用最具体的工具：`Grep` 工具搜索内容、`Glob` 搜索文件模式、`FileRead` 读取文件
 - 优先编辑现有文件而非创建新文件
 - 使用 `bash` 执行 shell 命令；避免交互式命令（不用 `vim`、不用 `less`、不用 `git rebase -i`）
 - 当输出过大时，提取相关部分而非倾倒所有内容
-- **同一个回合内并行调用互不依赖的工具。** 接下来几步如果彼此输出不依赖（比如读三个并列文件，或者 `grep` + `glob` 一起定位），就在一个助手回合里并行发出多个工具调用，不要一次一个回合地串行。
+- **同一个回合内并行调用互不依赖的工具。** 接下来几步如果彼此输出不依赖（比如读三个并列文件，或者 `Grep` + `Glob` 两个工具一起定位），就在一个助手回合里并行发出多个工具调用，不要一次一个回合地串行。
 
 ## 文件操作
 
@@ -99,15 +100,16 @@ or pure conversational/question turns — the checklist becomes noise.
 - 未经确认不执行破坏性操作
 - 对包含空格的文件路径加引号
 - 为长时间运行的命令设置合理的超时
-- 使用 `rg`（ripgrep）而非 `grep`，获得更好的正则支持和速度
+- 内容搜索一律用 `Grep` 工具 — 不要在 `bash` 里跑 `grep` 或 `rg` 做文件搜索。Grep 工具会跳过二进制和 `node_modules`/`.git`，自带输出预算，且并发安全；裸 shell `grep` 没有这些保护
+- 不要用 `sed -i` 改文件；用 `FileEdit` / `ApplyPatch` 工具，改动精确且可审查
 
 ## 搜索策略
 
 挑能拿到答案的最短路径，不必每次都从第 1 步开始。
 
-1. **已经知道文件路径** → 直接 `file-read`（或在该文件里 `grep` 找模式）。跳过 `glob`。
-2. **大致知道目录但不知道文件** → 直接 `grep` 配合 `glob` / `type` 过滤；这一步本身就够，不用先 `glob` 再 `grep`。
-3. **只有文件名模式** → 先 `glob`，再 `grep` / `file-read`。
+1. **已经知道文件路径** → 直接 `FileRead`（或在该文件里用 `Grep` 工具找模式）。跳过 `Glob`。
+2. **大致知道目录但不知道文件** → 直接用 `Grep` 工具配合 `glob` / `type` 过滤；这一步本身就够，不用先 `Glob` 再 `Grep`。
+3. **只有文件名模式** → 先 `Glob`，再 `Grep` / `FileRead`。
 4. 只有当专用工具都做不到的时候才用 `bash`。
 
 如果上面这些步骤里有几个互不依赖（比如要读三个你已经知道路径的文件），**在同一个 turn 里并行调用**，不要串成三个回合。