WooCommerce plugin docs / General

General settings

Navigation: WordPress Admin → WooCommerce → AI Assistant → Settings → General

Stored in option aiwsa_settings. Saved via the WordPress Settings API (options.php).


Enable AI Agent

What it does Master switch for the assistant. When off, REST routes refuse traffic and the storefront widget does not render.

Default value Off (false). You must turn this on after install.

Available options On / Off.

Recommended configuration On, after WooCommerce is ready and you have reviewed appearance and privacy limits.

When to use it Use Off for staging, or to hide the assistant without deactivating the plugin.

Effect on the frontend Off: no launcher, no shortcode chat, no public REST turns. On: widget and REST become available (subject to other settings).

Dependencies WooCommerce. Does not require an AI API key.

Important notes This is separate from “AI Provider configured”. Catalog search still works when the agent is on and no key is saved.

Example A merchant installs the plugin, enables this toggle, and shoppers immediately search the catalog with no OpenAI account.


Transport

What it does Chooses how the widget is *told* to send conversation turns: a blocking POST, or streaming (SSE) with automatic fallback.

Default value postBlocking request (most compatible).

Available options

ValueLabel
postBlocking request (most compatible)
sseStreaming, with automatic fallback

Recommended configuration Blocking request. The shipped widget.js does not consume the sse transport; it uses POST.

When to use it Leave on blocking unless a custom storefront client implements SSE against the advertised config.

Effect on the frontend With the bundled widget: no visible difference. Turns are sent as REST POST requests either way.

Dependencies Streaming would need a host that does not buffer PHP output. That path is not complete in the bundled UI.

Important notes The REST GET /aiwsa/v1/config response includes "transport": "post" or "sse". Developers can filter aiwsa_transport. Storefront SSE is incomplete.

Example Most shops keep Blocking request so replies appear after the server finishes one turn.