Beta readiness

Evaluate whether your WP-PFAgent installation is ready for production use. The readiness check inspects the environment, your provider setup, and the host plugins, and gives a green / yellow / red verdict.

What it checks

• At least one LLM provider configured and its probe healthy.
• WP-PFWorkflow installed, activated, licensed, and reachable.
• At least one connection in WP-PFWorkflow (so the agent has something to talk to when it builds workflows that need external services).
• PHP version ≥ 8.1.
• WordPress version ≥ 6.5.
• WordPress encryption salts defined in wp-config.php.
• WP-Cron healthy.
• No PHP fatal errors in the plugin namespace in the last 24h.
• Rate limit / budget settings are not all zero (zero = disabled = unsafe in production).

Where to run it

• Admin: Setyenv → Agent → Settings → Beta Readiness.
• REST: GET /pfw/v1/agent-runtime/beta-readiness.

How to read the verdict

• Green: every check passes. The agent is safe to use in production.
• Yellow: a non-critical check is failing (e.g. only one provider configured). The agent works; address the warnings before production.
• Red: a critical check fails (no provider, no Workflow plugin, recent fatals). The agent will misbehave or refuse new sessions until you fix the underlying cause.

When to re-check

The check re-runs every time you open the page. Underlying probes (provider health, etc.) are cached for a few minutes to avoid hammering external services.

Re-run it after:

• upgrading WP-PFAgent
• changing provider credentials
• installing or upgrading WP-PFWorkflow
• hitting unexpected errors in agent conversations

Common fixes