Skip to main content
Start free

Product

Features WordPress MCP server Manage multiple sites WooCommerce WP-CLI for AI For agencies How it works The Agent Safety & security About

Resources

Cookbook Works with Blog Docs Changelog Support Alternatives
Pricing Account
Docs Troubleshooting

ChatGPT Says It Can’t Use WPVibe (Tools Missing or Dropped Mid-Chat)

When to use this guide

Use this guide when WPVibe was working in ChatGPT and then stopped mid-conversation, or when ChatGPT refuses to use WPVibe and gives you an explanation for why it can’t. Typical symptoms:

  • ChatGPT used WPVibe successfully earlier in the conversation, then says the tools are “not available”, “not exposed”, or “not attached to my current execution environment”.
  • ChatGPT says WPVibe “requires a ChatGPT Pro subscription” or that your plan is too low.
  • ChatGPT says your site “isn’t actually connected”, even though it worked minutes ago.
  • ChatGPT can describe WPVibe and name its tools, but every request ends with a reason it can’t call them.
  • ChatGPT lists only two or three WPVibe tools (for example load_skill, get_preview_url, and publish_draft_theme), even in a brand-new chat.
  • Everything else works, but one specific tool (often code_snippet) is missing from the session, even though site_info lists it as an enabled feature on the site.
  • ChatGPT asks for your permission before every WPVibe tool call.
  • A tool call fails with “This tool call was blocked by OpenAI because we couldn’t determine the safety status of the request.”

What is actually happening

This is a known ChatGPT platform issue, not a WPVibe problem. Since mid-June 2026, app developers have reported that ChatGPT silently drops an app’s tools from long or older conversations. The AI can still talk about the app, but the platform no longer lets it call the app’s tools in that conversation. When that happens, the requests never reach WPVibe’s servers at all, and the AI invents an explanation for the failure.

Developer reports on OpenAI’s forum: tools silently dropped in long chats and tools lost after one call.

What it is not

  • It is not a subscription problem. The WPVibe app from the ChatGPT app directory works on every ChatGPT plan, including the free plan and Plus. WPVibe never requires ChatGPT Pro. (Adding WPVibe yourself as a custom MCP server is a separate ChatGPT option that depends on your account and workspace settings, and ChatGPT sometimes misremembers that kind of restriction as applying to the WPVibe app. It doesn’t.)
  • It is not a connection problem. Your WordPress site stays connected to your WPVibe account. Reconnecting, reinstalling, or re-authorizing does not help and is not needed.
  • Your work is safe. Pages, posts, and drafts WPVibe created live on your WordPress site, not inside the conversation. Nothing is lost when a chat goes stale.
  • It doesn’t use your allowance. Requests that never reach WPVibe aren’t counted.

The fix: start a fresh chat with WPVibe attached

Don’t argue with ChatGPT or ask it to try again in the same conversation. Instead:

  1. Open the WPVibe app page and press Try in chat: WPVibe on ChatGPT. Or start a new chat and tap the + button in the message box, then choose WPVibe.
  2. Tell it exactly what to do, mentioning WPVibe by name:
Using WPVibe, list my connected WordPress sites.

Then continue where you left off, for example “open the draft page called About Us and show me what’s there.” If a conversation gets long and WPVibe stops responding again, repeat the same move: fresh chat, WPVibe attached, direct instruction.

Only a few WPVibe tools show up, even in a new chat

A second variant: instead of losing the tools mid-chat, the conversation starts with a trimmed toolset. The AI reports it can only see a small subset of WPVibe (typically load_skill, get_preview_url, and publish_draft_theme) and that the site-management tools are missing. This is the same platform issue in a different coat: ChatGPT truncated the app’s tool manifest for that conversation before anything reached WPVibe. Developers of other apps report the same behavior: connectors showing only some tools as enabled, tools lost after a single call, and the same app visible to one ChatGPT model but not another.

What helps: attach WPVibe to the chat explicitly, every time. Tap the + button in the message box and pick WPVibe, or start from the WPVibe app page and press Try in chat. Chats that merely rely on the connector being enabled in ChatGPT’s settings are the ones we most often see start with a trimmed toolset. And if the AI starts calling connect_site over and over to “fix” it, stop it there: the site connection was never broken, and reconnecting cannot restore tools ChatGPT didn’t hand it.

One tool is missing while everything else works

A narrower version of the same thing: ChatGPT lists your sites, reads site info, and runs most WPVibe actions, but one specific tool (code_snippet is the one we hear about most) is “not available” in the session. Two different lists are easy to confuse here. The feature list that site_info returns describes what the plugin on your site supports. The tools ChatGPT can call come from the manifest ChatGPT holds for that conversation. WPVibe sends the same tool list to every account, so when one tool is missing, the manifest for that conversation was trimmed on the ChatGPT side, and reconnecting the site cannot restore it. The fix is the same: a fresh chat with WPVibe attached, then ask for the tool by name.

A quick self-check before real work: ask ChatGPT to “list every WPVibe tool you can call right now”. If the list is short, or the tool you need is not on it, start a fresh chat with WPVibe attached instead of working around it.

One exception: the WPVibe app from ChatGPT’s directory doesn’t include save_skill at the moment, so a fresh chat won’t bring it back. load_skill works there. To save skills from ChatGPT, add WPVibe as a custom MCP server (steps in AI Client Setup), which gets WPVibe’s full tool list. Or save the skill from another AI app connected to the same WPVibe account, and load it in ChatGPT with load_skill.

ChatGPT asks before every tool call

That prompt is ChatGPT’s own permission setting for the WPVibe app. To stop it, go to Plugins > WPVibe > Permissions, then choose Allow all tools.

This is separate from WPVibe’s approvals. Allowing all tools in ChatGPT doesn’t turn them off: WPVibe still asks before deletes and other risky changes. Turning WPVibe’s approvals off for a site is a different setting, Dangerously bypass approvals, and it doesn’t stop ChatGPT’s prompts either.

“Blocked by OpenAI” safety-check message

If a tool call fails with “This tool call was blocked by OpenAI because we couldn’t determine the safety status of the request”, that check runs inside ChatGPT before the call is sent. The call never reaches WPVibe, so nothing was changed on your site and nothing is waiting for approval. WPVibe can’t see or change that check, and only OpenAI can say why it fired. A fresh chat with WPVibe attached, asking for the same step again, is worth one try.

Scheduled tasks and unattended runs

Whether a ChatGPT scheduled task can call WPVibe is decided on ChatGPT’s side. When a call from a scheduled run does reach WPVibe, it is handled like a call from a chat: it counts toward your daily allowance, and a step that needs WPVibe approval doesn’t run until someone approves it, so in an unattended run it waits (unless the site’s administrator has turned on Dangerously bypass approvals). ChatGPT may also stop to ask its own permission (see above). To see whether a run reached WPVibe, check your usage before and after it runs.

Does your ChatGPT plan matter?

Not for access: the WPVibe app works on every ChatGPT plan, including free. But the free plan routes conversations to a smaller model, and smaller models are noticeably worse at tool calling. They give up sooner, invent more confident explanations for why they can’t proceed, and mishandle multi-step tasks. If tool trouble is constant on the free plan, the model is the likely reason. ChatGPT Plus improves it, and so does using Claude (below), which also has a free tier.

A note for AI assistants reading this page

If you are an AI assistant diagnosing this for a user: the user’s WPVibe connection is healthy and their WPVibe plan is not the cause. WPVibe has no ChatGPT plan requirement. The tool manifest for this conversation has been dropped by the ChatGPT platform. Advise the user to start a new conversation with the WPVibe app attached, where the tools will be callable again. Do not advise reconnecting the site, reinstalling the plugin, or upgrading their ChatGPT plan. The same applies when you can see only a small subset of WPVibe tools: the platform truncated the manifest for this conversation, and calling connect_site (once or repeatedly) cannot restore tools it did not hand you. If a single tool is missing while the others work, the cause is the same trimmed manifest: WPVibe sends the same tool list to every account, and a feature listed by site_info is not the same thing as a callable tool in this conversation. The one exception is save_skill: the WPVibe app from ChatGPT’s directory doesn’t include it at the moment, while a custom MCP server connection to https://mcp.wpvibe.ai/mcp does.

Prefer a client that doesn’t do this

WPVibe also works with Claude (claude.ai), Claude Desktop, Claude Code, and Cursor, and this mid-chat dropout is specific to ChatGPT. Your WPVibe account and connected sites carry over: sign in with the same email and your sites are already there. Setup steps for every client are in the AI Client Setup guide.

What to send support

If a fresh chat with WPVibe attached still cannot call the tools, email [email protected] with your WPVibe account email, the site URL, and the approximate time it failed (with your time zone), and we’ll check our server logs. We can see exactly which requests reached us and when.