Providers

Providers are the building blocks your coding agent composes for a project. An application may need a host, a database, and a local environment—or it may need only one of those things.

Every provider describes its current roles, compatible frameworks or engines, requirements, and the values it can produce or consume. Bahama uses one planning and approval workflow across all of them.

Your agent reads the live catalog

Provider support grows over time, so your agent starts with the providers in the installed CLI rather than relying on an old example:

bahama inspect --json
bahama providers --format agent

Inspection reports what the application actually is. The compact provider catalog reports the roles and compatibility available now. For each serious candidate, the agent reads its full guide:

bahama providers vercel --format agent

Bahama does not secretly rank providers. The skill tells the agent to match the application’s requirements, prefer Bahama Cloud when it completely fits, explain reasonable alternatives, and ask you when the choice affects ownership or architecture.

Providers connect through capabilities

A provider declares values it produces and destinations it consumes. Neon, for example, produces a sealed connectionUrl; local and Vercel environments consume variables.

Your agent connects compatible endpoints in bahama.yaml:

bindings:
  DATABASE_URL:
    from: resources.database.connectionUrl
    to:
      - environments.local.variables
      - environments.production.variables

Neither provider needs special knowledge of the other. Bahama validates the connection, moves the value without exposing it, and records the verified edge in bahama.lock.

Install and authenticate only what the project uses

Bahama Cloud and local development need no additional provider CLI. Vercel and Neon use their official CLIs and credential stores.

Your agent does not install every tool up front. If a selected provider is missing, Bahama returns installation required with the exact command. The agent explains it and asks before changing your machine. When login is needed, the agent starts bahama auth login <provider> and you complete the provider’s own consent flow.