AI Provider for exo

1.0.3

• Update npm development dependencies and resolve npm audit findings.

1.0.2

• Fix AI plugin connector detection on WordPress 7.0 RC3 by pointing the hidden sentinel connector at its synced setting.

1.0.1

• Added GitHub Actions workflow for deployment to WordPress.org.

1.0.0

• Prefix all declarations, globals, and stored data for WordPress.org compliance.
• Namespace changed to Aiprfoex.
• Constants, options, REST namespace, script handles, and provider slug all use the aiprfoex prefix.
• Environment variable names changed: AIPRFOEX_ENDPOINT, AIPRFOEX_API_KEY, AIPRFOEX_MODEL.
• Add sanitize_callback to register_setting() for capabilities option.
• Remove load_plugin_textdomain() — WordPress.org handles translations automatically.

0.3.0

• Fix: resolve “RequestAuthenticationInterface instance not set” error in AI plugin title generation.
• Fix: emulate multi-candidate responses — exo ignores OpenAI n parameter, now issues N sequential requests.
• Implement createRequest() abstract method required by SDK.
• Always register authentication even with empty API key (SDK requires an instance).
• Whitelist localhost and non-standard ports for wp_safe_remote_request().
• Prepend exo models to wpai_preferred_text_models filter for correct provider selection.
• Increase request timeout to 300s for local inference.
• Default max_tokens to 1024 to prevent unbounded reasoning in thinking models.
• Add model selection guidance to documentation.

0.2.0

• Add sentinel connector for WordPress AI plugin compatibility.
• AI plugin now recognizes exo as a valid, configured provider.
• Filter to hide internal sentinel connector from Connectors settings page.
• Custom exo wordmark logo (40×40 square) for the Connectors page.
• Fix: AI plugin showed “requires a valid AI Connector” despite exo being configured.

0.1.0

• Initial release.
• Register exo as a WordPress AI provider via the AI Client SDK.
• OpenAI-compatible text generation through exo’s chat completions API.
• Auto-detect active models from the exo cluster (REST endpoint: POST /exo/v1/detect).
• Capability detection — captures and displays model capabilities (Text, Code, Thinking, Vision) as badges.
• Connector settings UI with “Connect & Detect” / “Save & Re-detect” flow.
• Detected active models displayed in a read-only panel with Refresh support.
• Custom exo logo icon for the Connectors page.
• Optional API key authentication with secure storage and masking.
• Configurable endpoint URL (default: http://localhost:52415).
• Environment variable and wp-config.php constant support (EXO_ENDPOINT, EXO_API_KEY, EXO_MODEL).
• Full i18n support with Norwegian Bokmål (nb_NO) translation.