Skip to content

fix: configure gateway for external runtimes - #361

Merged
chubes4 merged 1 commit into
mainfrom
fix/360-external-ai-gateway
Aug 15, 2026
Merged

fix: configure gateway for external runtimes#361
chubes4 merged 1 commit into
mainfrom
fix/360-external-ai-gateway

Conversation

@chubes4

@chubes4 chubes4 commented Aug 15, 2026

Copy link
Copy Markdown
Member

Summary

  • configure the existing credential-free wp-ai-gateway/site-default provider for external OpenCode runtimes
  • continue skipping WordPress plugin installation, route mutation, token minting, and gateway env-file writes
  • keep endpoint and API key delivery in the Kimaki/OpenCode process environment
  • compile the existing external-endpoint profile selection into --with-ai-gateway

Closes #360.

Verification

  • bash tests/external-wordpress-runtime.sh
  • bash tests/ai-gateway.sh
  • node tests/setup-profile-compiler.mjs
  • bash tests/opencode-local-plugin-path.sh
  • bash tests/repair-opencode-json.sh
  • bash tests/ci-coverage.sh
  • shell syntax and git diff --check

The external regression injects fake endpoint/key values and proves neither value nor .opencode/wp-ai-gateway.env is persisted.

AI Assistance

OpenAI gpt-5.6-sol via OpenCode was used to trace the external runtime and gateway contracts, implement the focused fix, and run verification. Chris Huber reviewed and is responsible for every line.

@chubes4
chubes4 merged commit 3fa41ff into main Aug 15, 2026
48 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configure environment-backed AI Gateway for external runtimes

1 participant