Aleph

Connections

Some agents need access to apps such as GitHub. Those requirements are declared in the agent bundle as Connections. You authorize them once for your workspace scope; Aleph then exposes the matching tools during agent turns.

Connections are separate from Channels. Channels deliver chat through Discord or Telegram bots you own. Connections authorize the agent to use third-party apps through Connect.

Who owns the connection

Connections belong to the agent's dashboard scope:

  • Personal agents share Connections across agents you own personally.
  • Organization agents share Connections for that organization.
  • Team agents share Connections for that team.

Authorizing GitHub once in a scope lets every agent in that scope that declares GitHub use it.

Connect an app

  1. Open the agent and choose Connections in the management sidebar, or finish the create/edit/clone wizard through the Connections step after Vault.
  2. For each required app, choose Connect and complete the provider sign-in in the new tab.
  3. Return to Aleph and wait for status to show Connected (the page refreshes automatically).

If a required Connection is missing, Aleph shows a configuration warning and blocks turns that need that app until you connect it.

Bundles that declare Connections

Creators may include an optional connections.toml in the bundle. Example:

[[connections]]
id = "github"
required = true

Supported toolkit ids start with github. Agents without connections.toml show an empty Connections page and do not require app OAuth.

After cloning

Cloning never copies Connections. Connect required apps again in the destination scope before enabling an agent that depends on them. Do not paste personal access tokens into chat or the Vault for apps that use Connections.