| 开发者 | abdalsalaam |
|---|---|
| 更新时间 | 2026年10月18日 06:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
sodium and openssl extensions/wp-content/plugins/ai-provider-for-chatgpt/, or install through the WordPress plugin browser.http://127.0.0.1:1455/auth/callback), paste it on the settings screen, or use Paste from clipboard, and click Connect.Settings > ChatGPT shows the steps under How connecting works:
http://127.0.0.1:1455/auth/callback.After you approve, ChatGPT sends your browser to http://127.0.0.1:1455/auth/callback, an address on your own computer where nothing is listening, so the tab shows an error such as "This site can't be reached". That is expected: nothing is wrong. Copy the full address from that tab's address bar and paste it on the settings screen. The page address carries a one-time code; your site exchanges it for tokens when you paste it. The code is useless without the secret your site kept when you clicked Continue with ChatGPT.
ChatGPT Plus, Pro and Go accounts. OpenAI grants plan usage to other apps only on these plans. If your account does not grant plan usage, the plugin shows a message and saves nothing.
Disconnect keeps the site's registration with OpenAI, so the next sign-in reuses it and must use the same ChatGPT account. To switch accounts, click Use a different ChatGPT account on Settings > ChatGPT. It revokes any stored tokens and deletes the site's copy of the registration (the issued client id and the account's id, email and name); the app stays listed under ChatGPT Settings > Security and login > Sign in with ChatGPT, where you can disconnect it. Then sign in with the other account.
Usage and per-app limits are at https://chatgpt.com/settings/usage. The settings screen links there with Manage usage in ChatGPT. To disconnect the plugin from your ChatGPT account, go to ChatGPT Settings > Security and login > Sign in with ChatGPT and select Disconnect.
Version 1.0.0 connects with Sign in with ChatGPT and no longer uses the command line tool or auth.json files. Existing connections are removed on update; sign in again under Settings > ChatGPT. Free accounts are no longer eligible.
No. The plugin registers ChatGPT with the AI Client provider registry, so the AI Client must be available, either bundled in WordPress 7.0+ or installed as a separate package on 6.9.
No. OpenAI does not allow image generation for apps that use a ChatGPT plan through Sign in with ChatGPT; it is only available with an OpenAI API key. If your site needs image generation, use the official AI Provider for OpenAI plugin with an API key next to this one. This plugin covers text generation, chat, tool use, structured output and image input (reading images you attach).
No. This plugin runs only on your website. The plugin developer never receives your ChatGPT sign-in, your tokens or anything you send, and has no way to see or use your account. Your website keeps the connection encrypted in its own database and talks to OpenAI directly; the plugin contacts no other service (see External services). The connection cannot read your ChatGPT conversations or memories; it only lets your site use your plan for AI requests. OpenAI says so in Using your ChatGPT plan in other apps and sites (conversations and memories) and in the Sign in with ChatGPT documentation (conversations). You can disconnect at any time on Settings > ChatGPT, or under ChatGPT Settings > Security and login > Sign in with ChatGPT.
Tokens are stored in the WordPress options table on your own site, encrypted with sodium_crypto_secretbox using a key derived from your wp-config.php salts. They are sent only to OpenAI, to make requests and to refresh or revoke the connection.
connectors_ai_chatgpt_api_key option from the connection and diagnostics REST endpoints. The connector's configured state is now read solely through the AI Client API (isProviderConfigured()); the option is still written so the WordPress AI plugin can detect the connector's credentials, but it is no longer read back by this plugin.halawa_chatgpt_ to avoid collisions in WordPress's shared namespaces.__return_true) while keeping its single-use-token security boundary and per-IP rate limiting./responses stream.