How to Disconnect Apps from an AI Agent and Revoke Access

Side by side

First identify what you are trying to stop

There are several possible goals: stop a recurring task, prevent new account reads, prevent sending or editing, remove saved information, or close the agent account. They are related but not interchangeable. Write down which outcome you need before clicking a broadly labeled disconnect button.

For an ordinary cleanup, start with the active workflow and its connections. If a task has already sent a message or modified a document, revoking access does not reverse that action. Use the original service to inspect and address the completed change.

Image source and original context

Disconnect inside the agent

Open the agent’s connected-app or integration settings and locate the correct service and account. If the product offers separate read and action permissions, inspect both. Remove the connection you no longer need and cancel or pause the related recurring assignment where the product supports it.

Anthropic’s Duet guide says connections can be managed through Claude settings. It also states that disconnecting stops future access while memory from earlier conversations can remain. That is a useful reminder to treat connection cleanup and information cleanup as two separate passes.

Anthropic: get started with Claude Duet

Then review the source account

For Google accounts, use the linked-app page and select the relationship that concerns access to the Google account. Open the details, review the granted information and remove access for the linked app. Google documents sign-in links and agent-interaction permissions separately, so choose the category that matches your goal.

Check the account address at the top of the page before changing anything. Many people have several browser sessions open, and removing a grant from the wrong account leaves the intended connection untouched. Other providers use different labels; follow their own account-security documentation rather than applying Google’s labels universally.

Google: manage linked apps and agent permissions

Review history, memory and exported copies

Return to the agent and inspect the project or conversation that used the connection. Decide whether to retain the result, remove saved memory or delete the conversation. If you need a record, save the useful output before taking an irreversible deletion action.

Do not assume that clearing a visible thread removes every server-side copy immediately. Retention and backup handling depend on the provider’s current policy. If complete account deletion is your goal, use that provider’s documented route and review any separate billing relationship as well.

Confirm that the cleanup matches the goal

Reopen the connected-service list and the source account’s access list. Check that the relevant account and grant are absent or disabled. Review the task list for any recurring job that still expects the connection, and remove stale instructions so it does not repeatedly ask to reconnect.

Keep the cleanup simple enough to repeat after each project. A short list of connected services and their purposes is more useful than relying on memory. The result should be a clear answer to two questions: what can still be accessed, and what information is still stored?

Sources & scope

Reviewed October 24, 2026. Product facts follow the linked provider documentation. Selection advice and example prompts are iApp4Me editorial guidance. Screenshots and provider examples are credited beside each image. Availability and plan terms are dated October 24, 2026.

1. Anthropic: get started with Claude Duet

   Eligibility, setup, connectors and current preview limits.

2. Google: manage linked apps and agent permissions

   Distinguishes sign-in, data access and agent permissions.

More on this update

App guides

Continue researching