Skip to content

Guide Codex auth and optional gateway setup in setup skill #175

Description

@chubes4

Goal

Update the wp-coding-agents-setup skill so it can guide an operator through Codex auth and optional WP AI Gateway setup without putting provider-specific behavior into the gateway.

Boundary

  • ai-provider-for-openai owns Codex OAuth/token handling.
  • wp-ai-gateway remains a generic OpenAI-compatible gateway.
  • wp-coding-agents owns product wiring for OpenCode/Kimaki external clients.
  • The setup skill owns the human/operator recipe.

Scope

  • Detect whether wp-ai-gateway is installed and active.
  • Detect whether the Codex-capable provider stack is installed/active.
  • Detect whether provider codex is available/authenticated when provider CLI/admin status exists.
  • Guide the operator through provider auth when the provider exposes a login/status flow.
  • Configure wp-ai-gateway only when the operator wants external OpenCode/Kimaki to use WordPress as the OpenAI-compatible endpoint.
  • Make clear that Codebox minion fan-out does not require wp-ai-gateway; it uses Codebox connector inheritance/provider auth directly.
  • Verify gateway setup with wp ai-gateway status, /models, and a minimal chat completion when gateway mode is selected.

Acceptance criteria

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions