From b957986f5b4fb31de870d0b0b6c2f87e363bc8c9 Mon Sep 17 00:00:00 2001
From: jeffa-block <233853744+jeffa-block@users.noreply.github.com>
Date: Fri, 27 Mar 2026 04:05:54 +1100
Subject: [PATCH] docs: add available_tools field to extension config
 documentation (#7725)

---
 documentation/docs/guides/config-files.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/documentation/docs/guides/config-files.md b/documentation/docs/guides/config-files.md
index 680ab355..b50e43c8 100644
--- a/documentation/docs/guides/config-files.md
+++ b/documentation/docs/guides/config-files.md
@@ -122,6 +122,7 @@ extensions:
     name: "extension_name"    # Internal name
     timeout: 300              # Operation timeout in seconds
     type: "builtin"/"stdio"   # Extension type
+    available_tools: []       # Filter to specific tools (empty = all)
     
     # Additional settings for stdio extensions:
     cmd: "command"            # Command to execute
@@ -131,6 +132,10 @@ extensions:
     envs: {}                  # Environment values
 ```
 
+### Tool Filtering
+
+Use the `available_tools` field to limit which tools are loaded from an extension. List the tool names you want — only those will be available to goose. Leave it empty (the default) to load all tools. This can help reduce token overhead in sessions where you only need a subset of an extension's capabilities.
+
 ## Search Path Configuration
 
 Extensions may need to execute external commands or tools. By default, goose uses your system's PATH environment variable. You can add additional search directories in your config file: