DUOPORT CONNECTOR FOR OPENCODE
DuoPort Connector for OpenCode compatibility with REEID Translate
DuoPort Connector for OpenCode compatibility with REEID Translate is being reviewed using official plugin documentation. Registers two distinct WordPress AI Client providers (OpenCode Go and OpenCode Zen) via the native Connectors interface. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What DuoPort Connector for OpenCode does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
DuoPort Connector for OpenCode is documented in the Other category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How DuoPort Connector for OpenCode compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Registers two distinct WordPress AI Client providers (OpenCode Go and OpenCode Zen) via the native Connectors interface.
- Integrates with the WordPress AI Client provider registry for model selection and request transport without creating a separate site-wide router.
- Enforces a default-deny policy where only reviewed chat/completions models are routable, while non-chat or unverified models remain inaccessible unless explicitly enabled.
- Provides independent API key validation fields for each catalog, allowing users to test connectivity separately even when using a unified authentication token.
- Includes a credential-free Model Radar feature that monitors public catalog changes to queue new or free-model candidates for manual verification.
- Utilizes bounded availability probes with transient caching to validate keys and report connection states without repeatedly calling the full model list API.
TRANSLATION BOUNDARY
DuoPort Connector for OpenCode capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
DuoPort Connector for OpenCode and REEID Translate FAQ.
What does DuoPort Connector for OpenCode do?
DuoPort Connector for OpenCode has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does DuoPort Connector for OpenCode have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from DuoPort Connector for OpenCode?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate DuoPort Connector for OpenCode in a multilingual WordPress workflow.
REEID documents DuoPort Connector for OpenCode functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.