Configuration
Some tools have configurable settings that can be customized per assistant. When a tool supports configuration, a Configure badge appears next to it in the assistant’s Tools tab. Click the badge to open the tool’s configuration page.
Tools ship with sensible defaults, so configuration is optional — you only need to change settings when you want to override the default behavior. A Reset to Defaults button is available to clear any customizations.
search_knowledge
The search_knowledge tool has the following configurable settings:
- Similarity Threshold — Sets the maximum cosine distance (0–2) for search results. Lower values are stricter, filtering out results that aren’t closely related to the query. Leave empty for no filtering. A value around 0.5 is a good starting point.
- Source Types to Search — Controls which types of knowledge are included in search results: websites/URLs, facts, documents, conversations, and code. Uncheck a type to exclude it.
- Knowledge Boundary Instructions — Rules that constrain the assistant to answer from its knowledge base. Used by Knowledge Only mode assistants. Leave empty to use the defaults. See Modes for details.
Plugin Tool Configuration
Plugin tools can also define their own configuration schemas. Any configurable plugin tool will show a Configure badge in the same way. See Tool Plugins for how plugin authors define configuration.
Technical Details
Config resolution pipeline — Each tool class can define a config_schema specifying field types, default values, labels, and help text. When an assistant customizes a tool, the overrides are saved per-assistant. At execution time, the system merges the schema defaults with the saved overrides to produce the final configuration — so any field not explicitly customized falls back to its default value.
Runtime loading — All per-assistant tool configurations are loaded once at the start of each agent loop and cached in memory. Before dispatching each tool call, the system injects the correct configuration for that specific tool into the execution context. This means tools always receive their resolved configuration automatically, with no per-call database lookups.