WordPress/ai

Display additional AI provider plugins on Connectors page (alongside default Anthropic, Google, and OpenAI ones)

Open

#27 opened on Oct 6, 2025

View on GitHubContributor guide
 (12 comments) (0 reactions) (0 assignees)PHP (136 forks)auto 404
Help Wanted[Type] Enhancement

Repository metrics

Stars
 (246 stars)
PR merge metrics
 (Avg merge 5d 4h) (72 merged PRs in 30d)

Description

Description

Enable developers, agencies, and hosts to pre-configure AI providers that will be automatically recognized by the plugin. This supports a “progressive provider selection” approach (where existing providers are utilized and only presents provider configuration needs if no applicable provider has been configured) and reduces the need for manual setup.

Goals

  • Define a configuration system (using constants, filters, or configuration files) to allow pre-configured providers.
  • Ensure the system is modular so each feature can independently detect and use available providers.
  • When a valid pre-configured provider exists, the UI for provider selection should be hidden.
  • Document the configuration process with clear examples for hosts and network administrators.
  • Align with the encapsulated feature architecture so each feature can extend or override provider handling if needed.

Acceptance Criteria

  • Plugin detects and auto-selects any pre-configured providers.
  • Provider selection UI is suppressed when configuration is detected.
  • Features automatically inherit available provider connections.
  • Developer documentation includes at least one working example.

Contributor guide

Research direction
Examine the current plugin architecture for AI providers, identify where default providers (Anthropic, Google, OpenAI) are registered, and implement a configuration system (via filters or constants) that allows additional providers to be added. Ensure the provider selection UI is hidden when a valid pre configured provider exists. Test with a custom provider example.
Tech stack
php
Domain
backendfull stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
WordPress plugin developmentPHPGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50