# Private connections and OAuth

Connect your own account, recover a saved request, and disconnect access.

A personal integration uses your account at the external service. The agent manifest selects
the connector and allowed tools; you authorize your own account separately.
Your personal credential is not a shared workspace credential and is not put in `agent.yaml`.

> **Availability:** This guide applies to supported personal connectors where
> integrations are enabled. See [Availability](/reference/availability).

## Connect your account

1. Select the workspace where you will use the agent.
2. Open **Agents → your agent → Integrations** and select the intended version.
3. If the declared connector is disabled or unavailable, ask an administrator to repair it.
   Signing in does not override connector restrictions or an agent disable.
4. Choose **Connect your account**. Console opens the configured connection; choose **Connect**
   and complete the provider's OAuth flow. An existing provider authorization may be reused.
5. Check the returned account label. Wait for connection preparation to finish if it is still in
   progress, then return to the agent or saved request.

The provider decides which consent or installation steps are required. GitHub sign-in alone is
not proof that its App can access a particular repository. This MCP guide does not configure native
Git clone, push, or PR creation.

## Continue a saved request

When a required personal integration is unavailable, Console saves your exact prompt and attachment
references instead of running the agent. **Continue** stays disabled until setup is ready.
Returning from OAuth does not start a run. Return to the same request and click **Continue** once.
Concurrent retries do not create additional executions of that saved request.

Saved requests expire after 24 hours. **Discard request** deletes the saved request without running
it; it does not delete the separately uploaded files. Cancelling OAuth leaves the request blocked.
Use the same signed-in user and workspace to return to your saved request.

## Reconnect or check preparation

If your account needs authorization again, use the connection's Connect action and complete the
provider flow. If Console says your account is connected but the connection is still being prepared,
use **Check setup** or refresh status. Repeated OAuth consent is not a remedy for route preparation.
A missing or disabled workspace grant needs an administrator, not another personal sign-in.

## Disconnect

Open the connection in **Connectors**, choose **Disconnect** for your account, and confirm.
This revokes your platform connection; it does not delete the shared connector or another user's
account. Subsequent portable tool calls using that credential are denied. An operation already
accepted by the provider is not undone. A new request requiring this account stays blocked until
you reconnect and explicitly continue.

Administrators can separately remove the agent's access in **Agent → Integrations**. A successful
personal connection does not override that decision. Personal-account sessions use the verified
run initiator's account and require that person to own the session; they do not borrow another
member's credential.