Integrations

An agent is only as capable as the tools you give it. A research agent needs the web; a coding agent needs a terminal and Git; a support agent needs your Slack. Buda lets you decide this per agent — switch tools on, connect accounts, and keep everything else off — so each agent does exactly what its job requires and nothing more.

Two kinds of integration

Buda has two layers of capability, both managed from Settings → Integrations:

• Built-in agent tools — capabilities that ship with the cloud computer: runtime (terminal, files), web search and browsing, automation, image and video, channels, and audio. You toggle these per agent.
• OAuth connections — link an external account (like Linear or Slack) to an agent so it can act on your behalf in that service. Connecting runs a standard OAuth consent flow where you approve a defined set of scopes.

Per-agent connections

Tools and connections are scoped to a single agent, not the whole Space. Pick the agent from the selector at the top of the Integrations page, then enable what it needs. This keeps permissions tight: your finance agent never gets your code repos, and your support agent never gets your billing tools.

OAuth and scopes

When you connect an external service, Buda sends you to that provider's consent screen. You see exactly which scopes (permissions) the agent is requesting — for example, read access to issues — and you approve them explicitly. Buda stores the resulting token securely and uses it only for that agent's actions.

Revoking access

You can disconnect a service from the agent at any time on the Integrations page — Buda discards the stored token. For a belt-and-braces revoke, also remove Buda from the provider's own connected-apps settings.

Related