Toolsets

Toolsets are how Anyy keeps the model-visible tool list focused for a turn. They are groups such as web, memory, terminal, messaging, subagents, and mcp-docs.

Toolsets control visibility, not trust. A tool that is visible can still require approval, audit, confirmation, or a ChangePlan.

Default Visible Toolsets

Fresh profiles use Anyy's built-in default-visible list:

toolsets:
  default:
    - web
    - sessions
    - memory
    - tasks
    - automation
    - clarify
    - file
    - messaging
    - skills
    - subagents
    - terminal
    - tts

If toolsets.default is omitted, Anyy uses that built-in list. If you define toolsets.default, new sessions copy your profile list into their session metadata.

Existing sessions keep the list they already stored. Start a new session when you want a default-toolset change to apply cleanly.

Enable And Disable Toolsets

There is no separate anyy toolsets enable command in this build. Toolsets are enabled by the feature that owns them, or by editing toolsets.default.

Common paths:

Need	Path
Change ordinary defaults	Edit toolsets.default in config.yaml.
Add an MCP server's tools	Use anyy mcp add ... --activate-toolset or anyy mcp configure ... --activate-toolset.
Enable computer use	Use anyy computer-use enable.
Give a cron job narrower tools	Use the cron command's --toolsets option.

Use YAML list form for committed config:

toolsets:
  default:
    - web
    - memory
    - terminal

Unknown toolset names do not fail config load, but they do not expose built-in tools unless a runtime provider supplies that toolset. The current built-in runtime does not supply a home toolset.

Surface-specific Toolsets

Gateway, dashboard chat, CLI-created sessions, and messaging channels all use the same selection rules. A turn can carry explicit toolsets metadata; that list wins for the turn. Otherwise Anyy uses the session's stored toolsets metadata. If the session has no stored list, the built-in default-visible list is used.

The profile default normally affects turns by being copied into new session metadata at session creation. It does not rewrite older sessions on each send.

Active skills may add toolsets declared in their metadata when the turn is using the normal profile-derived session defaults or the built-in defaults. They do not add computer_use, and they do not widen a turn that supplied an explicit toolset list or a deliberately narrowed session list.

Turns with attachments can receive the runtime artifact toolset so attachment tools are available only when needed. If the turn supplied explicit toolsets metadata, Anyy does not add artifact implicitly.

Channel Toolsets

Messaging channels do not have a separate channel-only toolset namespace. A Telegram or other channel session uses the same stored session defaults as resident gateway sessions.

If a channel workflow should not expose a broad toolset, narrow the session or role metadata used for that channel. Do not rely on channel name alone as a tool policy.

MCP Toolsets

Each MCP server gets a toolset named mcp-<server>, after sanitizing the server id. For example, server id GitHub.Prod becomes mcp-github_prod.

MCP tools only load when the matching MCP toolset is selected. This prevents a configured MCP server from becoming model-visible just because it exists in config.yaml.

Use:

anyy mcp add docs --command CMD --enable --include search --activate-toolset
anyy mcp configure docs --include search,read_doc --enable --activate-toolset

Activation requires the MCP server to be enabled and to have a non-empty include list. Field-level MCP policy is documented in MCP Config Reference.

Computer Use Toolset

computer_use is intentionally hidden from the default-visible list. It is a higher-impact capability and is not activated by skill metadata.

Enable it through its setup command so Anyy writes the related capability config and updates toolsets.default together:

anyy computer-use enable

Disable it through the matching computer-use flow or by removing computer_use from toolsets.default and clearing the related capability config.

For exact field behavior and selection order, see Toolsets Reference.