If I Disconnect an AI Connector From My Social Accounts, Does It Actually Stop?
Last Updated:
Disconnecting Planoly in Claude cuts off Claude's access, so it can't take new actions. Posts already on your Planoly schedule stay scheduled after you disconnect, so check them yourself, because disconnecting the assistant doesn't unschedule anything. For the full picture of how Planoly works with Claude, see our full guide to MCP.
Maybe you're testing a new setup, handing an account to a teammate, or you just want to know the off switch works before you turn anything on. Either way, here's what disconnecting covers, and what it leaves in place.
Where Do I Revoke Access?
In Claude. Disconnecting there is the one step that cuts off Claude's access.
1. Disconnect Planoly in Claude. In Claude, open your list of connectors and click Disconnect on Planoly. That cuts off Claude's access to your Planoly account, so Claude can't call any Planoly tool. There's no separate step to take inside Planoly. Posts already scheduled in Planoly stay scheduled, which is covered below.
2. Check the social accounts themselves. Your Instagram, TikTok or other channels are connected to Planoly, not to Claude directly. Disconnecting Claude leaves those channel connections in place, which is usually what you want, since Planoly still needs them to publish posts you schedule by hand.
Why it works: disconnecting cuts off access at the connection itself, so the stop doesn't depend on the model following an instruction.
Why Might an Agent Keep Retrying After Access Is Gone?
Because the model doesn't always treat an auth error as final. A builder on r/mcp described an agent that kept calling a tool after being told the API key was revoked, and asked: "Where do you put that stop so a definite auth error blocks the very next call to that tool?"
The replies explain the behavior. One noted that "the model reads 'revoked' as a hint to retry," and recommended that "on a definite auth error, mark that credential dead for the session." Another put it more simply: "The stop belongs in the transport rather than the instructions."
In practice, this is why you disconnect instead of just asking. If you only tell Claude "stop using Planoly," you're relying on the model to listen. Once you click Disconnect on Planoly, Claude's access is cut off, so a retry has nothing to reach.
Why it works: retries after you disconnect fail harmlessly. Retries while access is still live, with only an instruction in the way, are the case you're trying to rule out.
What Happens to Posts Already Scheduled?
This is the part most people miss. When you disconnect an AI assistant from a scheduler, the posts it already put in the queue usually stay there. They belong to the scheduler now, and the scheduler publishes them at their set time unless you remove them. Disconnecting Claude does not reach into the queue and cancel anything.
That's the general pattern across scheduling tools, and it's how Planoly works: posts already on your Planoly schedule stay scheduled after you disconnect the Claude connector, including posts Claude created.
So before or right after you disconnect:
1. Open your schedule in Planoly. Look at everything queued for the next few days, not just today.
2. Identify posts Claude placed there. Planoly shows which posts were created or scheduled through Claude, so you can pick them out before you disconnect.
3. Remove or reschedule anything you don't want going out. Do this from Planoly, since Claude no longer has access once you've disconnected. To hold a post instead of losing it, move it to drafts, or switch its posting method from Auto-post to Reminder, which keeps it on the schedule but has Planoly notify you instead of publishing. Deleting a post is permanent. If you haven't disconnected yet, you can also ask Claude to move the posts it scheduled back to drafts first.
Why it works: you're separating "can the assistant act again?" from "what did it already set in motion?" Disconnecting answers the first question. Only checking the queue answers the second.
Will I Know Which Agent Did What?
Not always as clearly as you'd like. A thread titled "Why OAuth isn't enough" pointed out that "OAuth can show which client got access without giving you a clean audit trail for which agent or delegated action used it." In other words, the service may know that Claude had access without telling you which conversation triggered a given change.
That's another reason to review the schedule directly rather than trying to reconstruct history from a chat log. It also pairs with our guide on what data a Claude connector sees and keeps, which covers the other side of disconnecting: what's left behind.
If you're weighing whether to reconnect with tighter limits, our piece on whether it's safe to let AI post to your social accounts walks through that decision. To set the connection back up with approval steps in place, follow the Planoly Claude walkthrough.
Frequently Asked Questions
How do I disconnect the Claude connector from Planoly?
In Claude, open your list of connectors and click Disconnect on Planoly. That one step cuts off Claude's access. Posts already scheduled in Planoly stay scheduled.
Do scheduled posts still go out after I disconnect?
Yes. Posts already on your Planoly schedule stay scheduled after you disconnect the Claude connector, and they publish unless you remove them. Check your Planoly schedule before you disconnect, and move anything you want to hold to drafts or switch it to Reminder.
Can Claude keep posting after I revoke access?
Not successfully. Once you've disconnected Planoly in Claude, Claude's access is cut off, so any call it attempts fails. The model may still try to retry in an open conversation, which is why the stop needs to live in the connection, not the instructions.
Does disconnecting Claude disconnect my Instagram from Planoly?
No. Your social accounts are connected to Planoly, not to Claude. Removing the Claude connector leaves those in place.
Can I reconnect later?
Yes. You'll log in to Planoly and click Allow again from your list of connectors in Claude. Consider setting posting tools to require approval when you do.
