execute 模式可能运行仓库定义的构建、测试或检查脚本
原文依据:2 处execute 会派代理实施计划,而计划模板要求给出并运行 typecheck、lint、build 等验证命令。此类命令通常由仓库配置定义,可能执行任意项目脚本;“仓库内容是数据”的保护没有明确延伸到执行这些命令。
恶意或被篡改的项目脚本可能在执行代理的权限范围内读取文件、使用可用凭据、修改工作区或尝试联网。隔离 worktree 只能限制部分文件影响,不能自动限制进程权限。
`execute` 会让子代理实际实施计划;模板又要求计划列出 typecheck、lint、build 等“确切命令”。若执行代理运行这些由目标仓库定义的命令,仓库脚本可能产生副作用。源码没有说明在执行前审查脚本或限制命令;用户可要求作者明确命令白名单、逐项确认及沙箱边界。
| `plan <description>` | Skip the audit; recon just enough to specify, then write a single plan for the described improvement || `execute <plan>` | Dispatch an executor subagent to implement the plan in an isolated worktree, then review its diff with the `review-animations` bar and render a verdict || `reconcile` | Re-check `plans/` against the current code: mark done plans DONE, refresh stale file:line references, retire fixed findings |查看另外 1 个位置
## Verification- **Mechanical**: <exact commands — typecheck, lint, build — with expected outcome>.- **Feel check**: run the UI, trigger <interaction>, and confirm: - <observable check, e.g. "the dropdown scales from its trigger, not from center">