Remove access or leave the beta

Stop work before disconnecting

Cancel active sessions and inspect any draft PRs or branches already pushed to GitHub. A cancellation or disconnection does not undo Git commits, close every PR, or remove provider-side history and charges.

Remove repository and device access

1. In Barge Settings → GitHub, select Disconnect GitHub to remove this Barge account’s GitHub authorization. This stops its active sessions. It does not uninstall the shared GitHub App or remove other members’ access.
2. In GitHub’s installed-app settings, configure the Barge App to remove selected repositories, or uninstall it from accounts you administer. Organization installations require the appropriate organization owner. Review GitHub’s authorization settings as well if you want to revoke your user authorization there.
3. Open Settings → Overview. Find CLI devices. Select Revoke for the device you want to disconnect. The token stops working on its next request. Deleting the local config alone does not revoke the server token.

Success check: your GitHub connection shows disconnected. Removed repositories no longer appear in the App’s selected access. Ask the owner before you uninstall a shared GitHub App.

Remove provider access

In Settings, use Remove for a saved API credential or Disconnect on its subscription connection. Revoke the key, token, or connected session in the provider’s own account controls as appropriate. Removing one credential from Barge is not equivalent to revoking that credential at its issuer. Cancel work first rather than relying on removal to interrupt an already-running provider request. Do not include a credential in a removal request.

Success check: Barge shows the connection unconfigured/disconnected, and any issuer-side credential you chose to revoke is revoked there too.

Data retention and deletion

Barge keeps terminal session records and events for 30 days by default. Failed local-handoff uploads may remain available for retry. Barge attempts to delete uploaded workspaces after a task ends. A failed cleanup needs investigation. GitHub branches, PRs, comments, and uploaded PR attachments are separate copies; session pruning does not remove them. Provider records and charges follow the provider’s policies.

There is no documented self-service whole-account deletion control in the current beta. Disconnecting, revoking a token, archiving a session, and signing out are not whole-account deletion. To leave or request deletion, open a sanitized request asking for a private channel, then identify the account privately when that channel is supplied. Ask which data can be deleted, which external copies remain, and how completion will be confirmed. Do not post account details publicly. No deletion deadline or guarantee of removing third-party copies is implied.