Documentation
Integrations
Compatibility has several layers. Detecting a provider does not automatically make its workflows public or safe to execute.
This matrix applies to Core 0.3.49, available from the official WordPress.org listing.
Product surfaces
| Surface | Current scope | Control boundary |
|---|---|---|
| Content | Posts, navigation, search, taxonomies, site information, and public discovery. | Read-only Standard Tools form the default baseline. |
| Forms | Provider-aware discovery and reviewed publication for Contact Form 7 and WPForms Lite. | Every form is reviewed separately. Submission support is limited to tested single-page forms, requires approval, cannot be undone, and is disabled by default. |
| Commerce | WooCommerce product discovery, comparison, cart inspection, and selected cart changes. | Cart writes require approval. Checkout, payment, orders, authentication, and accounts are excluded. |
Forms compatibility matrix
This table reflects the provider support in Core 0.3.49. Tested support still has per-form enablement, field, workflow, and approval boundaries.
| Capability | Contact Form 7 | WPForms Lite |
|---|---|---|
| Detection | Tested | Tested |
| Schema discovery | Supported fields discovered | Supported fields discovered |
| Reviewed publication | Tested | Tested |
| Tested form submission | Tested for supported single-page forms | Tested for supported single-page forms |
| Default enablement | Detector on; execution off | Detector on; execution off |
| Tested versions | 6.1.5 and 6.1.6 | 1.9.9.2 and 1.10.2.1 |
| Known limitations | Single-page forms only. Quiz, acceptance, CAPTCHA, uploads, payment, account, signature, calculations, and checkout are blocked. | Single-page forms only. CAPTCHA, uploads, payment, account, signature, calculations, and checkout are blocked. |
What form execution means
Eligible tools are registered per form, not per provider. An administrator must enable form submission and opt in to the exact reviewed form. Immediately before an irreversible submission, the visitor sees the provider, exact field values, and disclosed side effects, then explicitly approves or cancels.
Provider validation and confirmation remain authoritative. Notifications, redirects, conditional logic, honeypots, and third-party feeds remain provider-controlled and must be reviewed before a form is enabled. Unsupported or high-impact fields cause the form tool to remain unavailable.
WooCommerce boundary
Read-only product search, product lookup, and categories are part of Standard Tools when WooCommerce is active. Core 0.3.49has been tested with WooCommerce 10.5.1 and 10.9.4 for discovery, public availability, cart inspection, and the supported cart tools. Separately reviewed transactional tools can inspect and change the visitor's cart with approval and idempotency controls. Open for Agents does not implement checkout, payment, order placement, login, registration, profile, or account-changing tools.