@polka-codes/cli 0.7.10 → 0.7.12

package/dist/index.js

@@ -24629,7 +24629,7 @@ var {
   Help
 } = import__.default;
 // package.json
-var version = "0.7.10";
+var version = "0.7.12";
 
 // ../core/src/AiService/AiServiceBase.ts
 class AiServiceBase {
@@ -34568,26 +34568,20 @@ ${tools.map((tool) => {
   }).join("")}
 # Tool Use Guidelines
 
-1. **Thinking**: Use \`<thinking>\` XCM tag to clearly outline your thought process *before* using any tools. This includes:
-  *  Assessing the current situation and available information.
-  *  Defining specific goals and a plan to achieve them.
-  *  Justifying the selection of a particular tool.
-  *  Explaining how you intend to use the tool and what you expect to achieve.
-2. **Tool Selection**: Choose one tool at a time per message based on the task and its description. Do not assume a tool’s outcome without explicit confirmation.
-3. **Formatting**: Formulate tool use only in the specified XML format for each tool.
-4. **User Response**: Wait for the user’s response after each tool use. Do not proceed until you have their confirmation. The user’s response may include:
-  *  Tool success or failure details
-  *  Linter errors
-  *  Terminal output or other relevant feedback
-5. **Conciseness**: Never repeat or quote the entire tool command in your final user-facing message. Summarize outcomes clearly and avoid echoing commands verbatim.
-6. **Brevity**: Respond concisely and move the conversation forward. Do not re-issue the same command or re-trigger tool use without necessity.
-7. **Iteration**: Follow these steps iteratively, confirming success and addressing issues as you go.
-8. **Error Handling**: If a tool returns an error, analyze the error message and adjust your approach accordingly. Consider alternative tools or strategies to achieve the desired outcome.
-
-By adhering to these guidelines:
-- You maintain clarity without accidentally re-invoking tools.
-- You confirm each step’s results before proceeding.
-- You provide only the necessary information in user-facing replies to prevent re-interpretation as new commands.`;
+1. **Outline Your Thought Process**
+  - Before using a tool, wrap your reasoning inside \`<thinking>\` tags. Be concise—just enough to clarify your plan and the rationale behind selecting a specific tool.
+
+2. **Wait for Feedback**
+  - After using a tool, wait for the user's response indicating success/failure or any output logs. Do not assume the result of a tool without explicit confirmation.
+
+3. **Error Handling**
+  - If a tool fails or produces an unexpected result, analyze the error, decide on an alternative approach or tool, and proceed carefully.
+
+4. **Avoid Repetition**
+  - Do not quote or repeat previous commands or prompts verbatim. Move the conversation forward by focusing on the latest required action.
+
+5. **No Unnecessary Re-invocations**
+  - Only invoke the same tool again if a genuine need arises (e.g., different parameters or updated context).`;
 };
 var agentsPrompt = (agents, name2) => `
 ====

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/cli",
-  "version": "0.7.10",
+  "version": "0.7.12",
   "license": "AGPL-3.0",
   "author": "github@polka.codes",
   "type": "module",