Allow query_project to use read-only tools even if they are excluded by the current context

This commit is contained in:
Sergiy Borodych authored and Dominik Jain committed 2026-06-09 12:16:58 +02:00
1 parent e4af86be05
commit 572e00e6d4
2 files changed
+1 -1

No files matched your search

+1
View File
@@ -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`.
-1
View File
@@ -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()