Toolsets Reference

Toolsets are named groups of model-visible tools. They decide which tools are presented to a turn; they are not a permission boundary. Tool risk, approval, audit, and execution policies still apply after a toolset is selected.

The primary config field is toolsets.default in config.yaml.

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

When toolsets.default is omitted, Anyy uses the built-in default list above. When it is present, new sessions copy that profile default into session metadata. Existing sessions keep the toolset list they already stored.

Config Format

Use a YAML list for committed config:

toolsets:
  default:
    - web
    - sessions
    - memory
    - terminal

The loader also accepts a string split on commas, spaces, tabs, and newlines, but the list form is easier to review and avoids accidental splitting.

Duplicate or blank entries are ignored. Unknown toolset names are accepted as names, but they expose no built-in tools unless an extension, active skill, MCP server, or runtime-selected capability provides that toolset.

Default Visible Toolsets

These toolsets are visible by default on a fresh profile:

Toolset	Purpose
web	Public web search and retrieval tools.
sessions	Session recall and session-level operations.
memory	The structured long-term memory edit tool.
tasks	Task and reminder helpers.
automation	Scheduled or recurring automation helpers.
clarify	Ask the user for missing information when a tool needs it.
file	Workspace file read/write/search helpers.
messaging	Channel and message delivery tools.
skills	Skill discovery and skill runtime tools.
subagents	Delegation, background job, and subagent control tools.
terminal	Shell/process execution tools.
tts	Text-to-speech output tools.

The exact tool list can change as capabilities are enabled, but the default toolset names are fixed by the product contract and test suite. There is no built-in home toolset in the current runtime.

Optional Toolsets

Optional toolsets must be explicitly selected by config, command metadata, a runtime condition, or a setup command.

Toolset	How it becomes visible
computer_use	Enabled through anyy computer-use enable; not activated by skill metadata.
artifact	Added only for turns with current-turn attachments or artifacts.
mcp-<server>	Added when an MCP server toolset is activated or selected.
browser	Added by browser setup when Browser integration is enabled; exposes Anyy-managed browser tools.
mcp-browser	Raw MCP browser backend toolset for explicit diagnostics; browser setup does not add it by default.

computer_use stays out of the built-in default list because it represents a higher-impact capability. Enabling it updates both its config block and toolsets.default.

Selection Order

For a turn, Anyy resolves toolsets in this order:

1. Explicit turn metadata toolsets wins for that turn.
2. Active skill toolsets are considered next. They can merge into the normal profile-derived session defaults, or into the built-in defaults when the session has no stored list.
3. If the session has a stored toolsets list that differs from the current profile default, Anyy treats it as deliberate narrowing and does not merge active-skill toolsets.
4. Without active skill additions, stored session metadata toolsets is used for sessions that have it.
5. If no explicit or stored list applies, the built-in default-visible list is used.

Active skills can add toolsets to a normal profile default, but they do not add computer_use. If a turn already supplied an explicit toolset list, active-skill toolsets are not implicitly added.

When a turn has attachments, Anyy may add the runtime artifact toolset so attachment-specific tools can be used. This runtime addition is not applied to a turn that supplied explicit toolsets metadata.

Sessions And Channels

New resident sessions copy the profile default toolsets at creation time. Updating toolsets.default changes future sessions, not already-running ones.

Channel sessions use the same selection rules as gateway sessions. A channel may carry metadata that narrows a turn or session, but there is no separate channel-only toolset namespace.

Cron jobs have their own --toolsets option when created from the CLI. That option controls the tools available to the scheduled run and does not rewrite toolsets.default.

MCP Toolsets

Every configured MCP server contributes a toolset named from its server id:

mcp-<sanitized-server-id>

For example, a server id GitHub.Prod becomes mcp-github_prod. Tools from that server are named with the mcp_<server>_<tool> prefix and only load when the matching MCP toolset is selected.

Use anyy mcp add ... --activate-toolset or anyy mcp configure ... --activate-toolset to add an enabled MCP server's toolset to toolsets.default. Activation requires an enabled server and a non-empty include list.

If an existing session stored an older default list before an MCP toolset was added, that session does not automatically gain the MCP tools. Start a new session or send an explicit toolset selection for that turn.

Governance

Toolsets only control visibility. A visible tool can still require approval, audit, confirmation, or a ChangePlan because of its descriptor, an MCP server policy, or a tool_governance.overrides entry.

To change risk or approval behavior, edit the tool's policy, not the toolset list.