# Using connected tools

A connection's tools are available to your agents automatically — but you decide which agent gets which. The agent editor's Connections tab lets you enable or disable each connected app per agent.

## Available to every session

Tools from an active connection are merged into the agent toolbelt when a session starts — you don’t re-connect per project. Each app’s tools are namespaced under its name, so the agent sees, say, github_* tools distinct from linear_* tools.

## Per-agent enable / disable

Not every agent should reach every app. Open an agent in the editor and go to its Connections tab to toggle which connected apps that agent can use. A reviewer agent might get GitHub and Sentry but not your database; a data analyst the reverse.

See the agent editor for the full set of tabs, and Tools & skills for how connected tools sit alongside built-in tools and skills.

> Least privilegeGive each agent only the connections it needs. Fewer tools means a sharper, faster-deciding agent — and a smaller blast radius if something goes wrong.

> Half-configured? Skipped.If a connection is missing required config, its server simply doesn’t launch and its tools don’t appear — the rest of your tools are unaffected. Re-open the connection to finish configuring it.
