OAuth apps
Configure customer-owned OAuth without changing existing connection bindings.
Provider authentication and agent authentication are separate. This page covers the OAuth client that Arc0 uses to connect to a provider. Arc0 MCP authentication covers an agent connecting to Arc0.
Arc0 can use a configured managed OAuth client, or a customer-owned client on an eligible paid plan. The current runtime supports customer-owned configurations for GitHub and the local test provider. The broader app catalog does not imply that every provider adapter or managed OAuth registration is already active.
Review project auth configs
Open Auth configs under Integrations to review one table per configured app. Each supported authentication lane shows the credential source, enabled status and existing connection count. Manage OAuth clients opens the existing client settings on Apps. Client secrets and API tokens are never displayed here. Members without administrative access still see lane status and connection counts; restricted client details say Admin only.
Last recorded change reports client creation, disablement or retirement where recorded. App enablement and client-selection change times are currently unavailable. Connection counts retain each account's original client binding, including accounts that need attention.
Add and select a configuration
Create an OAuth client with the provider and register the callback URL shown by the
running Arc0 environment. The local API callback is
http://localhost:4312/connect/callback. Production callback and custom-domain routing
must be configured and verified for that deployment; a verified domain alone is not an
active callback route.
Save a descriptive name, client ID and client secret. Arc0 encrypts the secret in the API runtime; catalog and management listings return only metadata. Select the configuration for the project's app before creating new connection links. Customer-owned OAuth requires the corresponding plan entitlement.
Connections keep their original client
Each connection link, connection and provider-token cleanup record retains its OAuth configuration. Selecting a new configuration changes future connections; it does not silently change the client used to refresh or revoke an existing connection. Reconnecting an existing account also retains its original configuration and provider identity.
Configurations are immutable. Create a new configuration when changing credentials. Disabling one prevents new authorization flows using it. Existing credentials still need their original client for safe refresh and retirement; disabling a configuration does not revoke all existing provider grants. Revoke those connections explicitly when required.
Customer-owned OAuth does not change who may use a connection or bypass policies. Managed OAuth is also separate from Premium access: managing an OAuth handshake does not supply or pay for access to the provider's product.
See Token export for the credential-export boundary.