Merge pull request #1537 from bor/fix/query-project-drop-is-active-assertion

Allow query_project tool to apply read-only tools excluded by the current context

CHANGELOG.md

@@ -13,6 +13,7 @@ Status of the `main` branch. Changes prior to the next official version change w
   - Fix: context or mode argument referencing a known name (e.g. `--context anitgravity`) could result in   
     incorrect file access if a corresponding local file existed (e.g. `./antigravity` binary);
     file access is now guarded with path detection (file ending or path separator must be present)
+  - Allow `query_project` tool to access read-only tools that are not enabled in the current configuration
 
 * Language Servers:
   - `typescript_vts`: Add `initialization_options` setting in `ls_specific_settings.typescript_vts`.

src/serena/tools/query_project_tools.py

@@ -53,7 +53,6 @@ class QueryProjectTool(Tool, ToolMarkerOptional, ToolMarkerDoesNotRequireActiveP
         :param tool_params_json: the parameters to pass to the tool, encoded as a JSON string
         """
         tool = self.agent.get_tool_by_name(tool_name)
-        assert tool.is_active(), f"Tool {tool_name} is not active."
         assert tool.is_readonly(), f"Tool {tool_name} is not read-only and cannot be executed in another project."
         if self._is_project_server_required(tool):
             client = ProjectServerClient()