docs: Added documentation for the new .tool/mcp enable/disable commands
+42
@@ -289,6 +289,32 @@ The following settings can be adjusted at runtime:
|
||||
|
||||
|
||||
|
||||
## `.tool` / `.mcp enable|disable` - Toggle a single tool or MCP server
|
||||
Setting `enabled_tools` or `enabled_mcp_servers` via `.set` requires retyping the whole comma-separated list. The
|
||||
`.tool` and `.mcp` toggles adjust one entry at a time instead:
|
||||
|
||||
| Command | Description |
|
||||
|----------------------------|-----------------------------------------------------------------------------------|
|
||||
| `.tool enable <name>` | Add a single tool to the enabled list in the current context |
|
||||
| `.tool disable <name>` | Remove a single tool from the enabled list in the current context |
|
||||
| `.mcp enable <server>` | Add a single MCP server to the enabled list and start it |
|
||||
| `.mcp disable <server>` | Remove a single MCP server from the enabled list and stop it |
|
||||
|
||||
These write through the same layer cascade as `.set` (session > role, else the global in-memory config), and the
|
||||
confirmation message tells you which layer was written. Tab completion is state-aware: `enable` offers only entries
|
||||
not currently enabled, `disable` offers only the current list.
|
||||
|
||||
Notes on edge cases:
|
||||
|
||||
* If the current list is `all`, disabling one entry expands `all` into the concrete list first (minus the disabled
|
||||
entry). For tools, this means tools added later will no longer be enabled automatically.
|
||||
* Entries enabled indirectly through a `mapping_tools`/`mapping_mcp_servers` alias cannot be disabled individually;
|
||||
disable the alias or set the full list via `.set` instead.
|
||||
* Disabling an MCP server that a loaded [skill](Skills) granted keeps it running until the skill is unloaded.
|
||||
* `.tool enable/disable` is unavailable in an agent context outside a session, and `.mcp enable/disable` is
|
||||
unavailable in agent contexts entirely — agent MCP servers are defined by the agent's own config
|
||||
(`.edit agent-config`).
|
||||
|
||||
## `.edit` - Modify configuration files
|
||||
The `.edit` command lets you modify configuration files for the current mode of the REPL. It will open the selected
|
||||
configuration in your preferred text editor. It lets you modify the following configurations:
|
||||
@@ -312,6 +338,22 @@ directory or file corresponding to the target entity. You can use it to delete t
|
||||
* `.delete rag` - Delete select RAGs
|
||||
* `.delete agent-data` - Delete select agent's configurations and all tools
|
||||
|
||||
## `.list` - List available assets
|
||||
The `.list` command lists the assets of a given kind, making them discoverable without relying on tab completion:
|
||||
|
||||
| Command | Description |
|
||||
|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `.list roles` | List all roles (including built-ins) |
|
||||
| `.list sessions` | List saved sessions for the current context |
|
||||
| `.list agents` | List installed agents, with their descriptions when available |
|
||||
| `.list rags` | List all RAGs |
|
||||
| `.list macros` | List all macros |
|
||||
| `.list skills` | List skills available in this context, with descriptions and a `(loaded)` marker for active skills |
|
||||
| `.list tools` | List the tools that can be enabled/disabled via `.tool [enable\|disable] <name>` (excludes internal `user__`/`todo__`/`agent__`/`mcp_` tools) |
|
||||
| `.list mcp-servers` | List the MCP servers that can be enabled/disabled via `.mcp [enable\|disable] <name>` (configured servers plus mapping aliases) |
|
||||
|
||||
`.list skills` honors the same visibility and policy filters as the model-facing `skill__list` tool, so it shows exactly what the model can load in the current role/agent/session context.
|
||||
|
||||
## `.install` - Reinstall bundled assets
|
||||
Coyote's built-in agents, macros, and tool functions (and an MCP config template) are written to your configuration
|
||||
directory on first run and are **not** overwritten afterward, so your local edits survive Coyote updates. The `.install`
|
||||
|
||||
+2
-1
@@ -138,6 +138,7 @@ your current context with git knowledge, frontend conventions, or any other modu
|
||||
|
||||
| Command | Effect |
|
||||
|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `.list skills` | List skills available in this context. Applies the same visibility and policy filters as the model-facing `skill__list` tool; loaded skills are marked `(loaded)`. |
|
||||
| `.skill loaded` | List currently-loaded skills in this session. |
|
||||
| `.skill load <name>` | Load a skill. Validates policy + compatibility, then refreshes the tool scope. |
|
||||
| `.skill unload <name>` | Unload a loaded skill. Releases any MCP servers it pulled in. |
|
||||
@@ -448,4 +449,4 @@ When skills are enabled, the model has three tools available for managing them i
|
||||
These are how the model discovers and uses skills mid-conversation. You can disable this discovery channel by setting
|
||||
`skills_enabled: false` at any level; the three tools then disappear from the model's function list entirely. The same
|
||||
happens if `function_calling_support: false` is set globally. Without function calling, the skill system has no surface
|
||||
to operate on, so it is silently disabled across REPL, CLI, agents, and the model's tool list.
|
||||
to operate on, so it is silently disabled across REPL, CLI, agents, and the model's tool list.
|
||||
Reference in New Issue
Block a user