lmin/zmo-cli
1
0
Fork 0
Code Issues Pull Requests Actions 89 Packages Projects Releases Wiki Activity

docs: mark tools config as deprecated (#17951)

Browse Source
This commit is contained in:
OpeOginni
2026-03-17 10:07:35 -05:00
committed by GitHub
parent ba22976568
commit 6708c3f6cf
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/web/src/content/docs/agents.mdx
+5 -3
View File
@@ -366,9 +366,11 @@ The model ID in your OpenCode config uses the format `provider/model-id`. For ex
--- ---
### Tools ### Tools (deprecated)
Control which tools are available in this agent with the `tools` config. You can enable or disable specific tools by setting them to `true` or `false`. `tools` is **deprecated**. Prefer the agent's [`permission`](#permissions) field for new configs, updates and more fine-grained control.
Allows you to control which tools are available in this agent. You can enable or disable specific tools by setting them to `true` or `false`. In an agent's `tools` config, `true` is equivalent to `{"*": "allow"}` permission and `false` is equivalent to `{"*": "deny"}` permission.
```json title="opencode.json" {3-6,9-12} ```json title="opencode.json" {3-6,9-12}
{ {
@@ -392,7 +394,7 @@ Control which tools are available in this agent with the `tools` config. You can
The agent-specific config overrides the global config. The agent-specific config overrides the global config.
::: :::
You can also use wildcards to control multiple tools at once. For example, to disable all tools from an MCP server: You can also use wildcards in legacy `tools` entries to control multiple tools at once. For example, to disable all tools from an MCP server:
```json title="opencode.json" ```json title="opencode.json"
{ {