CODE_AGENT_PROVIDER_PROFILE_IDS was missing ofcx-go, causing session
creation to normalize ofcx-go back to the default deepseek profile.
Adding ofcx-go to the allowlist ensures sessions are created with the
correct providerProfile that propagates to AgentRun backend profile routing.
Refs pikasTech/HWLAB#1034
ofcx-go uses deepseek-v4-flash model (not deepseek-chat) and identifies
as provider ofcx-go (not deepseek). Without these mappings, the adapter
falls back to deepseek defaults, causing ofcx-go sessions to route through
the wrong model.
Refs pikasTech/HWLAB#1034
Add ofcx-go (DeepSeek V4 Flash via OpenCode Zen Go) to the public provider
profiles list and wire its bridge summary to the existing hwlab-deepseek-proxy
Moon Bridge service. This allows cloud-api to accept ofcx-go as a valid
provider profile for Code Agent sessions and delegate to AgentRun.
Changes:
- Add ofcx-go to publicProfiles Set in provider-profile-management.ts
- Add opencodeZenGoBridgeSummary() returning the shared Moon Bridge URL
- Wire ofcx-go profile to bridge summary in normalizeProfileData()
The Moon Bridge side (opencode provider + deepseek-v4-flash route) was
already deployed in commit c19b6ef5. This commit completes the cloud-api
routing for the ofcx-go profile.
Refs pikasTech/HWLAB#1034
- Add ofcx-go to backendProfiles allowlist in agentrun-dispatch.mjs
- Extend deepseek-proxy Moon Bridge config with opencode provider
- Add deepseek-v4-flash model and opencode route to Moon Bridge config
- Add OPENCODE_API_KEY env var injection from hwlab-v02-code-agent-provider Secret
- Support both deepseek and opencode providers in shared Moon Bridge instance
lyon