auto-coder 0.1.361__py3-none-any.whl → 0.1.363__py3-none-any.whl

autocoder/common/__init__.py

@@ -272,13 +272,13 @@ class AutoCoderArgs(pydantic.BaseModel):
     index_model_anti_quota_limit: Optional[int] = 0
 
     enable_agentic_filter: Optional[bool] = False
-    enable_agentic_edit: Optional[bool] = False
+    enable_agentic_edit: Optional[bool] = True
     
 
     index_filter_level: Optional[int] = 0
     index_filter_enable_relevance_verification: Optional[bool] = True
     index_filter_workers: Optional[int] = 1
-    index_filter_file_num: Optional[int] = -1
+    index_filter_file_num: Optional[int] = 10
     index_build_workers: Optional[int] = 1
     
     planner_model: Optional[str] = ""

autocoder/common/ignorefiles/ignore_file_utils.py

@@ -1,9 +1,9 @@
-
 import os
 from pathlib import Path
 from threading import Lock
 import pathspec
 import threading
+from typing import Optional  # 添加Optional导入
 
 # 尝试导入 FileMonitor
 try:
@@ -24,7 +24,7 @@ class IgnoreFileManager:
     _instance = None
     _lock = Lock()
 
-    def __new__(cls):
+    def __new__(cls, project_root: Optional[str] = None):
         if not cls._instance:
             with cls._lock:
                 if not cls._instance:
@@ -32,20 +32,21 @@ class IgnoreFileManager:
                     cls._instance._initialized = False
         return cls._instance
 
-    def __init__(self):
+    def __init__(self, project_root: Optional[str] = None):
         if self._initialized:
             return
         self._initialized = True
         self._spec = None
         self._ignore_file_path = None
         self._file_monitor = None
+        self._project_root = project_root if project_root is not None else os.getcwd()
         self._load_ignore_spec()
         self._setup_file_monitor()
 
     def _load_ignore_spec(self):
         """加载忽略规则文件并解析规则"""
         ignore_patterns = []
-        project_root = Path(os.getcwd())
+        project_root = Path(self._project_root)
 
         ignore_file_paths = [
             project_root / '.autocoderignore',
@@ -89,15 +90,18 @@ class IgnoreFileManager:
 
     def should_ignore(self, path: str) -> bool:
         """判断指定路径是否应该被忽略"""
-        rel_path = os.path.relpath(path, os.getcwd())
+        rel_path = os.path.relpath(path, self._project_root)
         # 标准化分隔符
         rel_path = rel_path.replace(os.sep, '/')
         return self._spec.match_file(rel_path)
 
 
-# 对外提供单例
-_ignore_manager = IgnoreFileManager()
+# 对外提供的单例管理器
+_ignore_manager = None
 
-def should_ignore(path: str) -> bool:
+def should_ignore(path: str, project_root: Optional[str] = None) -> bool:
     """判断指定路径是否应该被忽略"""
+    global _ignore_manager
+    if _ignore_manager is None:
+        _ignore_manager = IgnoreFileManager(project_root=project_root)
     return _ignore_manager.should_ignore(path)

autocoder/common/result_manager.py

@@ -16,16 +16,24 @@ class ResultItem(BaseModel):
 class ResultManager:
     """结果管理器，用于维护一个追加写入的jsonl文件"""
     
-    def __init__(self, source_dir: Optional[str] = None):
+    def __init__(self, source_dir: Optional[str] = None, event_file: Optional[str] = None):
         """
         初始化结果管理器
         
         Args:
             source_dir: 可选的源目录，如果不提供则使用当前目录
+            event_file: 可选的事件文件路径，用于生成结果文件名
         """
         self.source_dir = source_dir or os.getcwd()
         self.result_dir = os.path.join(self.source_dir, ".auto-coder", "results")
-        self.result_file = os.path.join(self.result_dir, "results.jsonl")
+        
+        if event_file:
+            # 获取文件名并去掉后缀
+            event_file_name = os.path.splitext(os.path.basename(event_file))[0]
+            self.result_file = os.path.join(self.result_dir, f"{event_file_name}.jsonl")
+        else:
+            self.result_file = os.path.join(self.result_dir, "results.jsonl")
+            
         os.makedirs(self.result_dir, exist_ok=True)
 
     def append(self, content: str, meta: Optional[Dict[str, Any]] = None) -> ResultItem:

autocoder/common/rulefiles/autocoderrules_utils.py

@@ -6,7 +6,10 @@ from typing import Dict, List, Optional
 from loguru import logger
 import re
 import yaml
+import byzerllm # Added import
 from pydantic import BaseModel, Field
+from typing import List, Dict, Optional, Any # Added Any
+from autocoder.common import AutoCoderArgs
 
 # 尝试导入 FileMonitor
 try:
@@ -230,6 +233,25 @@ class AutocoderRulesManager:
             parsed_rules.append(parsed_rule)
         return parsed_rules
 
+    @classmethod
+    def reset_instance(cls):
+        """
+        重置单例实例。
+        如果当前实例正在运行，则先取消注册监控的目录，然后重置实例。
+        """
+        with cls._lock:
+            if cls._instance is not None:
+                # 取消注册监控的目录
+                if cls._instance._file_monitor:
+                    for dir_path in cls._instance._monitored_dirs:
+                        try:
+                            cls._instance._file_monitor.unregister(dir_path)
+                            logger.info(f"已取消注册目录监控: {dir_path}")
+                        except Exception as e:
+                            logger.warning(f"取消注册目录 {dir_path} 时出错: {e}")
+                cls._instance = None
+                logger.info("AutocoderRulesManager单例已被重置")
+
 
 # 对外提供单例
 _rules_manager = None
@@ -254,3 +276,150 @@ def parse_rule_file(file_path: str, project_root: Optional[str] = None) -> RuleF
     if _rules_manager is None:
         _rules_manager = AutocoderRulesManager(project_root=project_root)
     return _rules_manager.parse_rule_file(file_path)
+
+def reset_rules_manager():
+    """重置AutocoderRulesManager单例实例"""
+    AutocoderRulesManager.reset_instance()
+    global _rules_manager
+    _rules_manager = None
+
+# 添加用于返回类型的Pydantic模型
+class RuleRelevance(BaseModel):
+    """用于规则相关性判断的返回模型"""
+    is_relevant: bool = Field(description="规则是否与当前任务相关")
+    reason: str = Field(default="", description="判断理由")
+
+
+class RuleSelector:
+    """
+    根据LLM的判断和规则元数据选择适用的规则。
+    """
+    def __init__(self, llm: Optional[byzerllm.ByzerLLM], args: Optional[AutoCoderArgs] = None):
+        """
+        初始化RuleSelector。
+
+        Args:
+            llm: ByzerLLM 实例，用于判断规则是否适用。如果为 None，则只选择 always_apply=True 的规则。
+            args: 传递给 Agent 的参数，可能包含用于规则选择的上下文信息。            
+        """
+        self.llm = llm
+        self.args = args        
+
+    @byzerllm.prompt()
+    def _build_selection_prompt(self, rule: RuleFile, context: str = "") -> str:
+        """
+        判断规则是否适用于当前任务。
+
+        规则描述:
+        {{ rule.description }}
+
+        规则内容摘要 (前200字符):
+        {{ rule.content[:200] }}
+
+        {% if context %}
+        任务上下文:
+        {{ context }}
+        {% endif %}
+
+        基于以上信息，判断这条规则 (路径: {{ rule.file_path }}) 是否与当前任务相关并应该被应用？
+        
+        请以JSON格式返回结果:
+        ```json
+        {
+            "is_relevant": true或false,
+            "reason": "判断理由"
+        }
+        ```
+        """
+        # 注意：确保 rule 对象和 context 字典能够被 Jinja2 正确访问。
+        # Pydantic模型可以直接在Jinja2中使用其属性。
+        return {
+            "rule": rule,
+            "context": context
+        }
+
+    def select_rules(self, context: str, rules: List[RuleFile]) -> List[RuleFile]:
+        """
+        选择适用于当前上下文的规则。
+
+        Args:
+            context: 可选的字典，包含用于规则选择的上下文信息 (例如，用户指令、目标文件等)。
+
+        Returns:
+            List[RuleFile]: 选定的规则列表。
+        """
+        selected_rules: List[RuleFile] = []
+        logger.info(f"开始选择规则，总规则数: {len(rules)}")
+
+        for rule in rules:
+            if rule.always_apply:
+                selected_rules.append(rule)
+                logger.debug(f"规则 '{os.path.basename(rule.file_path)}' (AlwaysApply=True) 已自动选择。")
+                continue
+
+            if self.llm is None:
+                 logger.debug(f"规则 '{os.path.basename(rule.file_path)}' (AlwaysApply=False) 已跳过，因为未提供 LLM。")
+                 continue
+
+            # 对于 alwaysApply=False 的规则，使用 LLM 判断
+            try:
+                prompt = self._build_selection_prompt.prompt(rule=rule, context=context)
+                logger.debug(f"为规则 '{os.path.basename(rule.file_path)}' 生成的判断 Prompt (片段): {prompt[:200]}...")
+
+                # **** 实际LLM调用 ****
+                # 确保 self.llm 实例已正确初始化并可用
+                if self.llm: # Check if llm is not None                    
+                    result = None
+                    try:
+                        # 使用with_return_type方法获取结构化结果
+                        result = self._build_selection_prompt.with_llm(self.llm).with_return_type(RuleRelevance).run(rule=rule, context=context)
+                        if result and result.is_relevant:
+                            selected_rules.append(rule)
+                            logger.info(f"规则 '{os.path.basename(rule.file_path)}' (AlwaysApply=False) 已被 LLM 选择，原因: {result.reason}")
+                        else:
+                            logger.debug(f"规则 '{os.path.basename(rule.file_path)}' (AlwaysApply=False) 未被 LLM 选择，原因: {result.reason if result else '未提供'}")
+                    except Exception as e:                    
+                        logger.warning(f"LLM 未能为规则 '{os.path.basename(rule.file_path)}' 提供有效响应。")
+                        # 根据需要决定是否跳过或默认不选
+                        continue # 跳过此规则
+                else: # Handle case where self.llm is None after the initial check
+                    logger.warning(f"LLM instance became None unexpectedly for rule '{os.path.basename(rule.file_path)}'.")
+                    continue
+
+                # **** 模拟LLM调用 (用于测试/开发) ****
+                # 注释掉模拟部分，使用上面的实际调用
+                # simulated_response = "yes" if "always" in rule.description.lower() or "index" in rule.description.lower() else "no"
+                # logger.warning(f"模拟LLM判断规则 '{os.path.basename(rule.file_path)}': {simulated_response}")
+                # response_text = simulated_response
+                # **** 结束模拟 ****
+
+            except Exception as e:
+                logger.error(f"使用 LLM 判断规则 '{os.path.basename(rule.file_path)}' 时出错: {e}", exc_info=True)
+                # 根据策略决定是否包含出错的规则，这里选择跳过
+                continue
+
+        logger.info(f"规则选择完成，选中规则数: {len(selected_rules)}")
+        return selected_rules
+
+    def get_selected_rules_content(self, context: Optional[Dict] = None) -> Dict[str, str]:
+        """
+        获取选定规则的文件路径和内容字典。
+
+        Args:
+            context: 传递给 select_rules 的上下文。
+
+        Returns:
+            Dict[str, str]: 选定规则的 {file_path: content} 字典。
+        """
+        selected_rules = self.select_rules(context=context)
+        # 使用 os.path.basename 获取文件名作为 key，如果需要的话
+        # return {os.path.basename(rule.file_path): rule.content for rule in selected_rules}
+        # 保持 file_path 作为 key
+        return {rule.file_path: rule.content for rule in selected_rules}
+
+def auto_select_rules(context: str, rules: List[RuleFile], llm: Optional[byzerllm.ByzerLLM] = None,args:Optional[AutoCoderArgs] = None) -> List[RuleFile]:
+    """
+    根据LLM的判断和规则元数据选择适用的规则。
+    """
+    selector = RuleSelector(llm=llm, args=args)
+    return selector.select_rules(context=context, rules=rules)

autocoder/common/save_formatted_log.py

@@ -38,7 +38,7 @@ def save_formatted_log(project_root, json_text, suffix):
     md_content = "\n".join(md_lines)
 
     # Prepare directory
-    logs_dir = os.path.join(project_root, ".cache", "logs")
+    logs_dir = os.path.join(project_root, ".auto-coder", "logs","agentic")
     os.makedirs(logs_dir, exist_ok=True)
 
     # Prepare filename

autocoder/common/v2/agent/agentic_edit.py

@@ -10,7 +10,6 @@ from rich.panel import Panel
 from pydantic import SkipValidation
 from byzerllm.utils.types import SingleOutputMeta
 
-# Removed ResultManager, stream_out, git_utils, AutoCommandTools, count_tokens, global_cancel, ActionYmlFileManager, get_event_manager, EventContentCreator, get_run_context, AgenticFilterStreamOutType
 from autocoder.common import AutoCoderArgs, git_utils, SourceCodeList, SourceCode
 from autocoder.common.global_cancel import global_cancel
 from autocoder.common import detect_env
@@ -73,7 +72,6 @@ from autocoder.common.v2.agent.agentic_edit_types import (AgenticEditRequest, To
                                                           AskFollowupQuestionTool, UseMcpTool, AttemptCompletionTool
                                                           )
 
-
 # Map Pydantic Tool Models to their Resolver Classes
 TOOL_RESOLVER_MAP: Dict[Type[BaseTool], Type[BaseToolResolver]] = {
     ExecuteCommandTool: ExecuteCommandToolResolver,
@@ -87,7 +85,7 @@ TOOL_RESOLVER_MAP: Dict[Type[BaseTool], Type[BaseToolResolver]] = {
     AskFollowupQuestionTool: AskFollowupQuestionToolResolver,
     AttemptCompletionTool: AttemptCompletionToolResolver,  # Will stop the loop anyway
     PlanModeRespondTool: PlanModeRespondToolResolver,
-    UseMcpTool: UseMcpToolResolver,
+    UseMcpTool: UseMcpToolResolver
 }
 
 
@@ -234,7 +232,7 @@ class AgenticEdit:
         # Tools
 
         ## execute_command
-        Description: Request to execute a CLI command on the system. Use this when you need to perform system operations or run specific commands to accomplish any step in the user's task. You must tailor your command to the user's system and provide a clear explanation of what the command does. For command chaining, use the appropriate chaining syntax for the user's shell. Prefer to execute complex CLI commands over creating executable scripts, as they are more flexible and easier to run. Commands will be executed in the current working directory: ${cwd.toPosix()}
+        Description: Request to execute a CLI command on the system. Use this when you need to perform system operations or run specific commands to accomplish any step in the user's task. You must tailor your command to the user's system and provide a clear explanation of what the command does. For command chaining, use the appropriate chaining syntax for the user's shell. Prefer to execute complex CLI commands over creating executable scripts, as they are more flexible and easier to run. Commands will be executed in the current working directory: {{current_project}}
         Parameters:
         - command: (required) The CLI command to execute. This should be valid for the current operating system. Ensure the command is properly formatted and does not contain any harmful instructions.
         - requires_approval: (required) A boolean indicating whether this command requires explicit user approval before execution in case the user has auto-approve mode enabled. Set to 'true' for potentially impactful operations like installing/uninstalling packages, deleting/overwriting files, system configuration changes, network operations, or any commands that could have unintended side effects. Set to 'false' for safe operations like reading files/directories, running development servers, building projects, and other non-destructive operations.
@@ -256,7 +254,7 @@ class AgenticEdit:
         ## read_file
         Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
         Parameters:
-        - path: (required) The path of the file to read (relative to the current working directory ${cwd.toPosix()})
+        - path: (required) The path of the file to read (relative to the current working directory {{ current_project }})
         Usage:
         <read_file>
         <path>File path here</path>
@@ -265,7 +263,7 @@ class AgenticEdit:
         ## write_to_file
         Description: Request to write content to a file at the specified path. If the file exists, it will be overwritten with the provided content. If the file doesn't exist, it will be created. This tool will automatically create any directories needed to write the file.
         Parameters:
-        - path: (required) The path of the file to write to (relative to the current working directory ${cwd.toPosix()})
+        - path: (required) The path of the file to write to (relative to the current working directory {{ current_project }})
         - content: (required) The content to write to the file. ALWAYS provide the COMPLETE intended content of the file, without any truncation or omissions. You MUST include ALL parts of the file, even if they haven't been modified.
         Usage:
         <write_to_file>
@@ -278,15 +276,15 @@ class AgenticEdit:
         ## replace_in_file
         Description: Request to replace sections of content in an existing file using SEARCH/REPLACE blocks that define exact changes to specific parts of the file. This tool should be used when you need to make targeted changes to specific parts of a file.
         Parameters:
-        - path: (required) The path of the file to modify (relative to the current working directory ${cwd.toPosix()})
+        - path: (required) The path of the file to modify (relative to the current working directory {{ current_project }})
         - diff: (required) One or more SEARCH/REPLACE blocks following this exact format:
-        \`\`\`
+        ```
         <<<<<<< SEARCH
         [exact content to find]
         =======
         [new content to replace with]
         >>>>>>> REPLACE
-        \`\`\`
+        ```
         Critical rules:
         1. SEARCH content must match the associated file section to find EXACTLY:
             * Match character-for-character including whitespace, indentation, line endings
@@ -314,7 +312,7 @@ class AgenticEdit:
         ## search_files
         Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
         Parameters:
-        - path: (required) The path of the directory to search in (relative to the current working directory ${cwd.toPosix()}). This directory will be recursively searched.
+        - path: (required) The path of the directory to search in (relative to the current working directory {{ current_project }}). This directory will be recursively searched.
         - regex: (required) The regular expression pattern to search for. Uses Rust regex syntax.
         - file_pattern: (optional) Glob pattern to filter files (e.g., '*.ts' for TypeScript files). If not provided, it will search all files (*).
         Usage:
@@ -327,7 +325,7 @@ class AgenticEdit:
         ## list_files
         Description: Request to list files and directories within the specified directory. If recursive is true, it will list all files and directories recursively. If recursive is false or not provided, it will only list the top-level contents. Do not use this tool to confirm the existence of files you may have created, as the user will let you know if the files were created successfully or not.
         Parameters:
-        - path: (required) The path of the directory to list contents for (relative to the current working directory ${cwd.toPosix()})
+        - path: (required) The path of the directory to list contents for (relative to the current working directory {{ current_project }})
         - recursive: (optional) Whether to list files recursively. Use true for recursive listing, false or omit for top-level only.
         Usage:
         <list_files>
@@ -338,7 +336,7 @@ class AgenticEdit:
         ## list_code_definition_names
         Description: Request to list definition names (classes, functions, methods, etc.) used in source code files at the top level of the specified directory. This tool provides insights into the codebase structure and important constructs, encapsulating high-level concepts and relationships that are crucial for understanding the overall architecture.
         Parameters:
-        - path: (required) The path of the directory (relative to the current working directory ${cwd.toPosix()}) to list top level source code definitions for.
+        - path: (required) The path of the directory (relative to the current working directory {{ current_project }}) to list top level source code definitions for.
         Usage:
         <list_code_definition_names>
         <path>Directory path here</path>
@@ -637,7 +635,7 @@ class AgenticEdit:
         - Your current working directory is: {{current_project}}
         - You cannot \`cd\` into a different directory to complete a task. You are stuck operating from '{{ current_project }}', so be sure to pass in the correct 'path' parameter when using tools that require a path.
         - Do not use the ~ character or $HOME to refer to the home directory.
-        - Before using the execute_command tool, you must first think about the SYSTEM INFORMATION context provided to understand the user's environment and tailor your commands to ensure they are compatible with their system. You must also consider if the command you need to run should be executed in a specific directory outside of the current working directory '${cwd.toPosix()}', and if so prepend with \`cd\`'ing into that directory && then executing the command (as one command since you are stuck operating from '${cwd.toPosix()}'). For example, if you needed to run \`npm install\` in a project outside of '${cwd.toPosix()}', you would need to prepend with a \`cd\` i.e. pseudocode for this would be \`cd (path to project) && (command, in this case npm install)\`.
+        - Before using the execute_command tool, you must first think about the SYSTEM INFORMATION context provided to understand the user's environment and tailor your commands to ensure they are compatible with their system. You must also consider if the command you need to run should be executed in a specific directory outside of the current working directory '{{ current_project }}', and if so prepend with \`cd\`'ing into that directory && then executing the command (as one command since you are stuck operating from '{{ current_project }}'). For example, if you needed to run \`npm install\` in a project outside of '{{ current_project }}', you would need to prepend with a \`cd\` i.e. pseudocode for this would be \`cd (path to project) && (command, in this case npm install)\`.
         - When using the search_files tool, craft your regex patterns carefully to balance specificity and flexibility. Based on the user's task you may use it to find code patterns, TODO comments, function definitions, or any text-based information across the project. The results include context, so analyze the surrounding code to better understand the matches. Leverage the search_files tool in combination with other tools for more comprehensive analysis. For example, use it to find specific code patterns, then use read_file to examine the full context of interesting matches before using replace_in_file to make informed changes.
         - When creating a new project (such as an app, website, or any software project), organize all new files within a dedicated project directory unless the user specifies otherwise. Use appropriate file paths when creating files, as the write_to_file tool will automatically create any necessary directories. Structure the project logically, adhering to best practices for the specific type of project being created. Unless otherwise specified, new projects should be easily run without additional setup, for example most projects can be built in HTML, CSS, and JavaScript - which you can open in a browser.
         - Be sure to consider the type of project (e.g. Python, JavaScript, web application) when determining the appropriate structure and files to include. Also consider what files may be most relevant to accomplishing the task, for example looking at a project's manifest file would help you understand the project's dependencies, which you could incorporate into any code you write.
@@ -692,6 +690,15 @@ class AgenticEdit:
         3. Remember, you have extensive capabilities with access to a wide range of tools that can be used in powerful and clever ways as necessary to accomplish each goal. Before calling a tool, do some analysis within <thinking></thinking> tags. First, analyze the file structure provided in environment_details to gain context and insights for proceeding effectively. Then, think about which of the provided tools is the most relevant tool to accomplish the user's task. Next, go through each of the required parameters of the relevant tool and determine if the user has directly provided or given enough information to infer a value. When deciding if the parameter can be inferred, carefully consider all the context to see if it supports a specific value. If all of the required parameters are present or can be reasonably inferred, close the thinking tag and proceed with the tool use. BUT, if one of the values for a required parameter is missing, DO NOT invoke the tool (not even with fillers for the missing params) and instead, ask the user to provide the missing parameters using the ask_followup_question tool. DO NOT ask for more information on optional parameters if it is not provided.
         4. Once you've completed the user's task, you must use the attempt_completion tool to present the result of the task to the user. You may also provide a CLI command to showcase the result of your task; this can be particularly useful for web development tasks, where you can run e.g. \`open index.html\` to show the website you've built.
         5. The user may provide feedback, which you can use to make improvements and try again. But DO NOT continue in pointless back and forth conversations, i.e. don't end your responses with questions or offers for further assistance.                    
+        
+        {% if file_paths_str %}
+        ====
+        The following are files that the user is currently focusing on. 
+        Make sure you always start your analysis by using the read_file tool to get the content of the files.
+        <files>
+        {{file_paths_str}}
+        </files>
+        {% endif %}
         """
         import os
         extra_docs = get_rules()
@@ -702,6 +709,8 @@ class AgenticEdit:
             shell_type = "cmd"
         elif shells.is_running_in_powershell():
             shell_type = "powershell"
+
+        file_paths_str = "\n".join([file_source.module_name for file_source in self.files.sources])
         return {
             "conversation_history": self.conversation_history,
             "env_info": env_info,
@@ -716,6 +725,7 @@ class AgenticEdit:
             "mcp_server_info": self.mcp_server_info,
             "enable_active_context_in_generate": self.args.enable_active_context_in_generate,
             "extra_docs": extra_docs,
+            "file_paths_str": file_paths_str,
         }
 
     # Removed _execute_command_result and execute_auto_command methods
@@ -773,27 +783,15 @@ class AgenticEdit:
         conversations = [
             {"role": "system", "content": system_prompt},
         ] 
-        
-        logger.info("Adding initial files context to conversation")
-        conversations.append({
-            "role":"user","content":f'''
-The following are context files that the user is currently focusing on. These files are presented with their complete paths and up-to-date content, providing essential context to help you better understand the user's needs. If you need more detailed information about specific files or directories not shown here, you can use tools like read_file, search_files, or list_files to explore the codebase further.
-<files>
-{self.files.to_str()}
-</files>'''
-        })
-
-        conversations.append({
-            "role":"assistant","content":"Ok"
-        })
-        
-        logger.info("Adding conversation history")        
+                                
         conversations.append({
             "role": "user", "content": request.user_input
         })        
         
         logger.info(
             f"Initial conversation history size: {len(conversations)}")
+        
+        logger.info(f"Conversation history: {json.dumps(conversations, indent=2,ensure_ascii=False)}")
 
         iteration_count = 0
         tool_executed = False
@@ -814,17 +812,18 @@ The following are context files that the user is currently focusing on. These fi
 
             assistant_buffer = ""
             logger.info("Initializing stream chat with LLM")
+
+            ## 实际请求大模型
             llm_response_gen = stream_chat_with_continue(
                 llm=self.llm,
                 conversations=conversations,
                 llm_config={},  # Placeholder for future LLM configs
                 args=self.args
             )
-
-            meta_holder = byzerllm.MetaHolder()
+            
             logger.info("Starting to parse LLM response stream")
             parsed_events = self.stream_and_parse_llm_response(
-                llm_response_gen, meta_holder)
+                llm_response_gen)
 
             event_count = 0
             for event in parsed_events:
@@ -943,8 +942,9 @@ The following are context files that the user is currently focusing on. These fi
                     # logger.error("Stopping analyze loop due to parsing error.")
                     # return
 
-            logger.info("Yielding token usage event")
-            yield TokenUsageEvent(usage=meta_holder.meta)
+                elif isinstance(event, TokenUsageEvent):
+                    logger.info("Yielding token usage event")
+                    yield event
             
             if not tool_executed:
                 # No tool executed in this LLM response cycle
@@ -960,16 +960,21 @@ The following are context files that the user is currently focusing on. These fi
                     elif last_message["role"] == "assistant":
                         logger.info("Appending to existing assistant message")
                         last_message["content"] += assistant_buffer
-                # If the loop ends without AttemptCompletion, it means the LLM finished talking
-                # without signaling completion. We might just stop or yield a final message.
-                # Let's assume it stops here.
-                logger.info("No tool executed and LLM finished. Breaking out of main loop.")
-                break
-
+                
+                # 添加系统提示，要求LLM必须使用工具或明确结束，而不是直接退出
+                logger.info("Adding system reminder to use tools or attempt completion")
+                conversations.append({
+                    "role": "user",
+                    "content": "NOTE: You must use an appropriate tool (such as read_file, write_to_file, execute_command, etc.) or explicitly complete the task (using attempt_completion). Do not provide text responses without taking concrete actions. Please select a suitable tool to continue based on the user's task."
+                })
+                # 继续循环，让 LLM 再思考，而不是 break
+                logger.info("Continuing the LLM interaction loop without breaking")
+                continue
+            
         logger.info(f"AgenticEdit analyze loop finished after {iteration_count} iterations.")
 
     def stream_and_parse_llm_response(
-        self, generator: Generator[Tuple[str, Any], None, None], meta_holder: byzerllm.MetaHolder
+        self, generator: Generator[Tuple[str, Any], None, None]
     ) -> Generator[Union[LLMOutputEvent, LLMThinkingEvent, ToolCallEvent, ErrorEvent], None, None]:
         """
         Streamingly parses the LLM response generator, distinguishing between
@@ -1046,7 +1051,8 @@ The following are context files that the user is currently focusing on. These fi
                 logger.exception(
                     f"Failed to parse tool XML for <{tool_tag}>: {e}\nXML:\n{tool_xml}")
                 return None
-
+        
+        meta_holder = byzerllm.MetaHolder()
         for content_chunk, metadata in generator:
             global_cancel.check_and_raise(token=self.args.event_file)
             meta_holder.meta = metadata            
@@ -1264,6 +1270,9 @@ The following are context files that the user is currently focusing on. These fi
                     output_cost = (
                         last_meta.generated_tokens_count * output_price) / 1000000
 
+                    # 添加日志记录
+                    logger.info(f"Token Usage Details: Model={model_name}, Input Tokens={last_meta.input_tokens_count}, Output Tokens={last_meta.generated_tokens_count}, Input Cost=${input_cost:.6f}, Output Cost=${output_cost:.6f}")
+
                     get_event_manager(self.args.event_file).write_result(
                         EventContentCreator.create_result(content=EventContentCreator.ResultTokenStatContent(
                             model_name=model_name,
@@ -1447,6 +1456,9 @@ The following are context files that the user is currently focusing on. These fi
                     output_cost = (
                         last_meta.generated_tokens_count * output_price) / 1000000
 
+                    # 添加日志记录
+                    logger.info(f"Token Usage: Model={model_name}, Input Tokens={last_meta.input_tokens_count}, Output Tokens={last_meta.generated_tokens_count}, Input Cost=${input_cost:.6f}, Output Cost=${output_cost:.6f}")
+
                     self.printer.print_in_terminal(
                             "code_generation_complete",
                             duration=0.0,

autocoder/common/v2/agent/agentic_edit_tools/read_file_tool_resolver.py

@@ -22,20 +22,23 @@ class ReadFileToolResolver(BaseToolResolver):
         abs_project_dir = os.path.abspath(source_dir)
         abs_file_path = os.path.abspath(os.path.join(source_dir, file_path))
 
-        # Security check: ensure the path is within the source directory
-        if not abs_file_path.startswith(abs_project_dir):
-            return ToolResult(success=False, message=f"Error: Access denied. Attempted to read file outside the project directory: {file_path}")
+        # # Security check: ensure the path is within the source directory
+        # if not abs_file_path.startswith(abs_project_dir):
+        #     return ToolResult(success=False, message=f"Error: Access denied. Attempted to read file outside the project directory: {file_path}")
 
         try:
-            if self.shadow_manager:
-                shadow_path = self.shadow_manager.to_shadow_path(abs_file_path)
-                # If shadow file exists, read from it
-                if os.path.exists(shadow_path) and os.path.isfile(shadow_path):
-                    with open(shadow_path, 'r', encoding='utf-8', errors='replace') as f:
-                        content = f.read()
-                    logger.info(f"[Shadow] Successfully read shadow file: {shadow_path}")
-                    return ToolResult(success=True, message=f"Successfully read file (shadow): {file_path}", content=content)
-                # else fallback to original file
+            try:
+                if self.shadow_manager:
+                    shadow_path = self.shadow_manager.to_shadow_path(abs_file_path)
+                    # If shadow file exists, read from it
+                    if os.path.exists(shadow_path) and os.path.isfile(shadow_path):
+                        with open(shadow_path, 'r', encoding='utf-8', errors='replace') as f:
+                            content = f.read()
+                        logger.info(f"[Shadow] Successfully read shadow file: {shadow_path}")
+                        return ToolResult(success=True, message=f"Successfully read file (shadow): {file_path}", content=content)
+            except Exception as e:
+                pass
+            # else fallback to original file
             # Fallback to original file
             if not os.path.exists(abs_file_path):
                 return ToolResult(success=False, message=f"Error: File not found at path: {file_path}")