Before installation
Install and activate your premium ZIP in WordPress. Version 1.1.0 requires WordPress 6.9 or later and PHP 8.1 or later. Keep your regular site backup.
PAGUP Agent Control 1.1.0
PAGUP Agent Control features and compatibility
What the plugin lets you do on each plan, what it needs from your WordPress site and your AI account, and the limits that matter before you buy.
What you can do on each plan
Reading published pages works as soon as the connection is active. Everything else goes through a temporary task that you authorize in WordPress.
| Capability | Solo | Pro | Agency |
|---|---|---|---|
| Public pages read by your assistant | Included | Included | Included |
| Assistant analysis of selected content | Included | Included | Included |
| Assistant-created drafts | Included | Included | Included |
| Assistant proposals for your review | Included | Included | Included |
| Assistant publishing as a separate task | Included | Included | Included |
| Licensed WordPress sites | 1 | 5 | 20 |
Included Not included
Compatibility and requirements
Check these conditions before installing. An integration that is not listed here is not covered by the guided path.
Connect your AI
Use your own compatible AI account. Custom connections depend on your provider, plan and workspace permissions. Agent Control does not include an AI subscription.
Client interfaces and verification
ChatGPT's documented web access requires Plus, Pro, Business, Enterprise or Education. Claude custom-connector availability and organization permissions depend on the account. Check the linked provider instructions, reviewed on September 7, 2026.
Which assistant do you use?Advanced REST access remains a separate path.
The guided private folder for Claude Code or Codex uses WordPress REST and an Application Password with a dedicated read-only profile. Existing Read Only, Draft, Content Editor and Publisher profiles remain under Advanced. They are not automatically converted to OAuth and do not inherit the remote task and exact-approval model.
Temporary permissions and advanced REST profiles.Limits worth knowing
Know what leaves WordPress.
Content returned by the connection is sent to the AI service you chose. Only grant access to information you may share with that service, and review its account and workspace data settings. Do not put passwords, keys or customer secrets in prompts. Revoking access does not erase content already delivered to the provider.
Check member-only and paywalled sites before connecting.
WordPress publication status alone does not prove that a page is public to every visitor. Inventory metadata can include content restricted by another plugin. Page inspection uses an anonymous request from the WordPress server, without cookies or JavaScript; server or proxy exceptions can change the result. Have your integrator compare an external signed-out visit and apply the restrictive public-content filter before enabling this access.
Recovery has a defined scope.
Snapshots support recovery for supported content changes. They do not replace a full site backup and do not scan out secrets. The guided path does not provide plugin, theme, user, setting, file or deletion operations. WooCommerce, ACF, builders and SEO integrations need their own assessment.
A task, an approval and a connection have different endings.
Finish a task to remove its temporary permissions. Public reading can continue while the connection remains active. Revoke an approval to withdraw that decision. Pause or revoke the connection in Manage connections to stop its tools; pausing and revoking are separate actions.
Full Power Access is a separately licensed administrative add-on. It is outside the guided task model, outside the protected REST modes, and is not included in Solo, Pro or Agency. It is not required for ordinary questions or drafts.