Tool bundles

A bundle groups related tools so you enable and configure them together rather than one at a time. Adding the bundle adds every tool in it.

Who can do what

Task	User	Agent owner	Admin
Add a bundle to an agent	— as Editor	✅	✅
Configure a bundle on an agent	— as Editor	✅	✅
Remove a bundle	— as Editor	✅	✅
Define which bundles exist	—	—	—

The catalogue of bundles is set by the platform, not per organization — which bundles you see depends on your deployment. What you control is which of them each agent gets.

Using them

Agent → Settings → Tool Bundles lists what's available and what the agent already has.

• Add a bundle and its tools appear under Tools.
• Configure it once — shared settings and credentials are entered at the bundle level rather than repeated on each tool.
• Remove it to take the whole group away.

Bundle configuration vs. tool configuration

Both exist, and the distinction is worth knowing:

• Bundle configuration holds what the group shares — an account, a credential, a workspace.
• Tool configuration holds what one tool needs on its own — a default repository, a channel.

Set the shared thing once on the bundle; override the specific thing on the tool.

Bundles and connections

A bundle covering a third-party service still needs that service connected for the organization. The bundle grants the agent the capability; the connection provides the access. Adding a Slack bundle to an agent in an organization with no Slack connection gives you tools that can't do anything yet.

Removing a bundle

Removing takes away the bundle's tools. Anything the agent built with them — the files it wrote, what it remembered — stays; it just can't do that kind of work any more. Re-adding restores the tools, and configuration you'd entered is still there.