auto-coder 0.1.378__tar.gz → 0.1.380__tar.gz

{auto_coder-0.1.378 → auto_coder-0.1.380}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: auto-coder
-Version: 0.1.378
+Version: 0.1.380
 Summary: AutoCoder: AutoCoder
 Author: allwefantasy
 Classifier: Programming Language :: Python :: 3.10
@@ -43,6 +43,7 @@ Requires-Dist: python-docx
 Requires-Dist: docx2txt
 Requires-Dist: pdf2image
 Requires-Dist: docx2pdf
+Requires-Dist: pypdf
 Requires-Dist: pyperclip
 Requires-Dist: colorama
 Requires-Dist: pylint

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/auto_coder.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: auto-coder
-Version: 0.1.378
+Version: 0.1.380
 Summary: AutoCoder: AutoCoder
 Author: allwefantasy
 Classifier: Programming Language :: Python :: 3.10
@@ -43,6 +43,7 @@ Requires-Dist: python-docx
 Requires-Dist: docx2txt
 Requires-Dist: pdf2image
 Requires-Dist: docx2pdf
+Requires-Dist: pypdf
 Requires-Dist: pyperclip
 Requires-Dist: colorama
 Requires-Dist: pylint

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/auto_coder.egg-info/SOURCES.txt

@@ -196,6 +196,7 @@ src/autocoder/common/v2/agent/agentic_edit_tools/plan_mode_respond_tool_resolver
 src/autocoder/common/v2/agent/agentic_edit_tools/read_file_tool_resolver.py
 src/autocoder/common/v2/agent/agentic_edit_tools/replace_in_file_tool_resolver.py
 src/autocoder/common/v2/agent/agentic_edit_tools/search_files_tool_resolver.py
+src/autocoder/common/v2/agent/agentic_edit_tools/test_execute_command_tool_resolver.py
 src/autocoder/common/v2/agent/agentic_edit_tools/test_search_files_tool_resolver.py
 src/autocoder/common/v2/agent/agentic_edit_tools/test_write_to_file_tool_resolver.py
 src/autocoder/common/v2/agent/agentic_edit_tools/use_mcp_tool_resolver.py

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/auto_coder.egg-info/requires.txt

@@ -33,6 +33,7 @@ python-docx
 docx2txt
 pdf2image
 docx2pdf
+pypdf
 pyperclip
 colorama
 pylint

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/autocoder/agent/base_agentic/base_agent.py

@@ -616,6 +616,8 @@ class BaseAgent(ABC):
         - When using the replace_in_file tool, you must include complete lines in your SEARCH blocks, not partial lines. The system requires exact line matches and cannot match partial lines. For example, if you want to match a line containing "const x = 5;", your SEARCH block must include the entire line, not just "x = 5" or other fragments.
         - When using the replace_in_file tool, if you use multiple SEARCH/REPLACE blocks, list them in the order they appear in the file. For example if you need to make changes to both line 10 and line 50, first include the SEARCH/REPLACE block for line 10, followed by the SEARCH/REPLACE block for line 50.
         - It is critical you wait for the user's response after each tool use, in order to confirm the success of the tool use.        
+        - To display LaTeX formulas, use a single dollar sign to wrap inline formulas, like `$E=mc^2$`, and double dollar signs to wrap block-level formulas, like `$$\frac{d}{dx}e^x = e^x$$`.
+        - To include flowcharts or diagrams, you can use Mermaid syntax.
         
         {% if extra_docs %}  
         ====

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/autocoder/common/command_file_manager/manager.py

@@ -37,7 +37,7 @@ class CommandManager:
             os.makedirs(self.commands_dir, exist_ok=True)
             logger.info(f"已创建命令目录: {self.commands_dir}")
     
-    def list_command_files(self, recursive: bool = False) -> ListCommandsResult:
+    def list_command_files(self, recursive: bool = True) -> ListCommandsResult:
         """
         列出命令目录中的所有命令文件
         

{auto_coder-0.1.378 → auto_coder-0.1.380}/src/autocoder/common/v2/agent/agentic_edit.py

@@ -391,20 +391,7 @@ class AgenticEdit:
         Your final result description here
         </result>
         <command>Command to demonstrate result (optional)</command>
-        </attempt_completion>
-
-        ## plan_mode_respond
-        Description: Respond to the user's inquiry in an effort to plan a solution to the user's task. This tool should be used when you need to provide a response to a question or statement from the user about how you plan to accomplish the task. This tool is only available in PLAN MODE. The environment_details will specify the current mode, if it is not PLAN MODE then you should not use this tool. Depending on the user's message, you may ask questions to get clarification about the user's request, architect a solution to the task, and to brainstorm ideas with the user. For example, if the user's task is to create a website, you may start by asking some clarifying questions, then present a detailed plan for how you will accomplish the task given the context, and perhaps engage in a back and forth to finalize the details before the user switches you to ACT MODE to implement the solution.
-        Parameters:
-        - response: (required) The response to provide to the user. Do not try to use tools in this parameter, this is simply a chat response. (You MUST use the response parameter, do not simply place the response text directly within <plan_mode_respond> tags.)
-        - options: (optional) An array of 2-5 options for the user to choose from. Each option should be a string describing a possible choice or path forward in the planning process. This can help guide the discussion and make it easier for the user to provide input on key decisions. You may not always need to provide options, but it may be helpful in many cases where it can save the user from having to type out a response manually. Do NOT present an option to toggle to Act mode, as this will be something you need to direct the user to do manually themselves.
-        Usage:
-        <plan_mode_respond>
-        <response>Your response here</response>
-        <options>
-        Array of options here (optional), e.g. ["Option 1", "Option 2", "Option 3"]
-        </options>
-        </plan_mode_respond>
+        </attempt_completion>        
 
         ## mcp_tool
         Description: Request to execute a tool via the Model Context Protocol (MCP) server. Use this when you need to execute a tool that is not natively supported by the agentic edit tools.
@@ -596,28 +583,7 @@ class AgenticEdit:
 
         By thoughtfully selecting between write_to_file and replace_in_file, you can make your file editing process smoother, safer, and more efficient.
 
-        ====
-
-        ACT MODE V.S. PLAN MODE
-
-        In each user message, the environment_details will specify the current mode. There are two modes:
-
-        - ACT MODE: In this mode, you have access to all tools EXCEPT the plan_mode_respond tool.
-        - In ACT MODE, you use tools to accomplish the user's task. Once you've completed the user's task, you use the attempt_completion tool to present the result of the task to the user.
-        - PLAN MODE: In this special mode, you have access to the plan_mode_respond tool.
-        - In PLAN MODE, the goal is to gather information and get context to create a detailed plan for accomplishing the task, which the user will review and approve before they switch you to ACT MODE to implement the solution.
-        - In PLAN MODE, when you need to converse with the user or present a plan, you should use the plan_mode_respond tool to deliver your response directly, rather than using <thinking> tags to analyze when to respond. Do not talk about using plan_mode_respond - just use it directly to share your thoughts and provide helpful answers.
-
-        ## What is PLAN MODE?
-
-        - While you are usually in ACT MODE, the user may switch to PLAN MODE in order to have a back and forth with you to plan how to best accomplish the task. 
-        - When starting in PLAN MODE, depending on the user's request, you may need to do some information gathering e.g. using read_file or search_files to get more context about the task. You may also ask the user clarifying questions to get a better understanding of the task. You may return mermaid diagrams to visually display your understanding.
-        - Once you've gained more context about the user's request, you should architect a detailed plan for how you will accomplish the task. Returning mermaid diagrams may be helpful here as well.
-        - Then you might ask the user if they are pleased with this plan, or if they would like to make any changes. Think of this as a brainstorming session where you can discuss the task and plan the best way to accomplish it.
-        - If at any point a mermaid diagram would make your plan clearer to help the user quickly see the structure, you are encouraged to include a Mermaid code block in the response. (Note: if you use colors in your mermaid diagrams, be sure to use high contrast colors so the text is readable.)
-        - Finally once it seems like you've reached a good plan, ask the user to switch you back to ACT MODE to implement the solution.
-
-        ====
+        ====        
 
         PACKAGE CONTEXT INFORMATION
 
@@ -691,6 +657,9 @@ class AgenticEdit:
         - When using the replace_in_file tool, you must include complete lines in your SEARCH blocks, not partial lines. The system requires exact line matches and cannot match partial lines. For example, if you want to match a line containing "const x = 5;", your SEARCH block must include the entire line, not just "x = 5" or other fragments.
         - When using the replace_in_file tool, if you use multiple SEARCH/REPLACE blocks, list them in the order they appear in the file. For example if you need to make changes to both line 10 and line 50, first include the SEARCH/REPLACE block for line 10, followed by the SEARCH/REPLACE block for line 50.
         - It is critical you wait for the user's response after each tool use, in order to confirm the success of the tool use. For example, if asked to make a todo app, you would create a file, wait for the user's response it was created successfully, then create another file if needed, wait for the user's response it was created successfully, etc.        
+        - To display LaTeX formulas, use a single dollar sign to wrap inline formulas, like `$E=mc^2$`, and double dollar signs to wrap block-level formulas, like `$$\frac{d}{dx}e^x = e^x$$`.
+        - To include flowcharts or diagrams, you can use Mermaid syntax.
+
         
         {% if extra_docs %}  
         ====

auto_coder-0.1.380/src/autocoder/common/v2/agent/agentic_edit_tools/test_execute_command_tool_resolver.py

@@ -0,0 +1,70 @@
+import pytest
+from unittest.mock import MagicMock, patch
+from autocoder.common.v2.agent.agentic_edit_tools \
+    .execute_command_tool_resolver import ExecuteCommandToolResolver
+from autocoder.common.v2.agent.agentic_edit_types import ExecuteCommandTool
+from autocoder.common import AutoCoderArgs
+
+
+class TestExecuteCommandToolResolver:
+    @pytest.fixture
+    def mock_agent(self):
+        agent = MagicMock()
+        agent.args = AutoCoderArgs()
+        agent.args.context_prune_safe_zone_tokens = 1000
+        agent.context_prune_llm = None
+        agent.current_conversations = []
+        return agent
+
+    @pytest.fixture
+    def mock_tool(self):
+        return ExecuteCommandTool(
+            command="echo 'test output'", 
+            requires_approval=False
+        )
+
+
+    def test_command_execution_with_token_count(self, mock_agent, mock_tool):
+        """测试命令执行并验证token统计功能"""
+        resolver = ExecuteCommandToolResolver(mock_agent, mock_tool, mock_agent.args)
+        
+        # 模拟命令执行返回大量输出
+        with patch("autocoder.common.run_cmd.run_cmd_subprocess") as mock_run_cmd:
+            mock_run_cmd.return_value = (0, "test output " * 500)  # 生成大量输出
+            
+            result = resolver.resolve()
+            
+            assert result.success
+            assert "test output" in result.content
+            
+            # 验证token统计功能
+            # 这里需要修改ExecuteCommandToolResolver来添加token统计功能
+            # 测试将失败，符合TDD的红色阶段
+
+    def test_output_pruning_when_exceeds_token_limit(self, mock_agent, mock_tool):
+        """测试当输出超过token限制时的裁剪功能"""
+        resolver = ExecuteCommandToolResolver(mock_agent, mock_tool, mock_agent.args)
+        
+        # 模拟命令执行返回大量输出
+        with patch("autocoder.common.run_cmd.run_cmd_subprocess") as mock_run_cmd:
+            mock_run_cmd.return_value = (0, "test output " * 500)  # 生成大量输出
+            
+            result = resolver.resolve()
+            
+            assert result.success
+            # 验证输出是否被裁剪
+            # 这里需要修改ExecuteCommandToolResolver来添加裁剪功能
+            # 测试将失败，符合TDD的红色阶段
+
+    def test_command_execution_failure(self, mock_agent, mock_tool):
+        """测试命令执行失败的情况"""
+        resolver = ExecuteCommandToolResolver(mock_agent, mock_tool, mock_agent.args)
+        
+        # 模拟命令执行失败
+        with patch("autocoder.common.run_cmd.run_cmd_subprocess") as mock_run_cmd:
+            mock_run_cmd.return_value = (1, "command failed")
+            
+            result = resolver.resolve()
+            
+            assert not result.success
+            assert "command failed" in result.message

auto_coder-0.1.380/src/autocoder/version.py

@@ -0,0 +1,2 @@
+
+__version__ = "0.1.380"

auto_coder-0.1.378/src/autocoder/version.py

@@ -1,2 +0,0 @@
-
-__version__ = "0.1.378"