@unity-china/codely-cli 1.0.0-rc.14 → 1.0.0-rc.16

package/bundle/builtin-agents/explore.toml

@@ -3,7 +3,7 @@ description = "Fast read-only codebase search agent for finding files, patterns,
 display_name = "Explore"
 
 tools = ["*"]
-disallowed_tools = ["replace", "write_file", "save_memory"]
+disallowed_tools = ["replace", "write_file", "apply_patch", "save_memory"]
 
 [prompts]
 system_prompt = """

package/bundle/builtin-agents/plan.toml

@@ -3,7 +3,7 @@ description = "Software architect agent for designing implementation plans. Use
 display_name = "Plan"
 
 tools = ["*"]
-disallowed_tools = ["replace", "write_file", "save_memory"]
+disallowed_tools = ["replace", "write_file", "apply_patch", "save_memory"]
 
 [prompts]
 system_prompt = """

package/bundle/example-prompts/analyze.toml

@@ -7,12 +7,12 @@ Analysis Topic: {input}
 Topic-driven goals:
 1. **Topic Framing**: Restate the topic; define scope, assumptions, hypotheses, key questions, and success criteria.
 2. **Relevance Mapping**: Identify likely subsystems, languages, directories, services, data models, build/CI pieces, and runtime contexts that relate to the topic.
-3. **Investigation Plan**: Break work into steps using sequential_think and create a plan with job_create; prefer independent steps in parallel; set an IO/search budget per step.
+3. **Investigation Plan**: Break work into clear job_create items only when tracking adds value; prefer independent steps in parallel; set an IO/search budget per step.
 4. **Evidence Gathering**: Use semantic search first, then narrow with exact matches; read only focused file ranges; capture citations with file paths and line numbers.
 5. **Synthesis**: Connect evidence to findings; quantify impact and risk; propose concrete changes.
 
 Search and tooling rules (MANDATORY):
-- **MUST use sequential_think first** to define scope and create a plan with job_create before any search.
+- Define the scope and create a job_create plan before search only when the topic is broad or multi-step; skip job_create for a single straightforward lookup.
 - **ALWAYS keep searches tightly scoped** to specific directories/files; avoid using project root "./" as the target.
 - Prefer codebase_search for semantic discovery; use grep/glob only for exact symbols/strings within the scoped paths.
 - Use read_file only for specific, bounded ranges; avoid opening entire large files unless necessary.
@@ -41,7 +41,7 @@ Notes:
 - Optimize for breadth-first discovery first, then go deep where evidence indicates hotspots.
 - Keep explanations concise but precise; avoid generic claims without evidence.
 
-**CRITICAL**: You MUST NOT use Grep/Glob tool under project root "./". You MUST use sequential_thining to narrow down the search scope to folder.
+**CRITICAL**: You MUST NOT use Grep/Glob tool under project root "./". Narrow the search scope to specific folders before running exact searches.
 
 Focus on providing constructive, actionable feedback suitable for large-scale codebases.
 """