Greptile Summary

This PR adds the OpenCode Go channel (opencode_go), wiring it end-to-end across the frontend schema, provider/channel config, localisations, the ent database enum, the GraphQL schema, and the backend transformer/endpoint registrations. The new channel follows the OpenAI chat-completions format and reuses the existing generic OpenAI-compatible transformer path.

• Backend: opencode_go is added to the ent enum and auto-generated code, registered under the channel.TypeOpenai-compatible transformer in channel_llm.go, and assigned openAIChatOnlyDefaultEndpoints in channel_endpoint.go — consistent with other single-format providers such as fireworks and cerebras.
• Frontend: The channel is added to channelTypeSchema, CHANNEL_CONFIGS, CHANNEL_TYPE_TO_PROVIDER, and PROVIDER_CONFIGS with the OpenCode icon sourced from @lobehub/icons@5.8.0, which required bumping the icon package from ^3.0.0 to ^5.8.0; this version jump introduces a peer dependency conflict with @lobehub/ui (v3 installed vs. v5 required) that should be investigated.

Confidence Score: 3/5

The new channel implementation is complete and consistent across backend and frontend, but the two-major-version icon package bump introduces a peer dependency conflict that could cause runtime rendering failures for icon components.

The Go backend changes are clean and follow established patterns exactly. The concern is on the frontend: bumping @lobehub/icons from v3 to v5 just to import one new icon brings in a stated peer requirement of @lobehub/ui@^5.0.0, while the project only has @lobehub/ui@3.4.6. pnpm resolves this without error depending on strict-peer-deps config, but any icon that calls into v5-only @lobehub/ui APIs at runtime would silently break. All existing channel icons are also served by the upgraded package, so the blast radius is not limited to the OpenCode symbol alone.

frontend/package.json and frontend/pnpm-lock.yaml — the @lobehub/icons upgrade and the resulting @lobehub/ui peer dependency mismatch deserve a second look before merging.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant AxonHub
    participant ChannelService
    participant OpenAITransformer
    participant OpenCodeAPI

    Client->>AxonHub: POST /v1/chat/completions (model: opencode-go-v1)
    AxonHub->>ChannelService: Route to opencode_go channel
    ChannelService->>ChannelService: buildChannelWithTransformer (TypeOpencodeGo → OpenAI-compatible path)
    ChannelService->>OpenAITransformer: NewOutboundTransformerWithConfig(PlatformOpenAI, baseURL)
    AxonHub->>OpenAITransformer: Transform request
    OpenAITransformer->>OpenCodeAPI: POST /chat/completions (Bearer key)
    OpenCodeAPI-->>OpenAITransformer: Streaming response
    OpenAITransformer-->>Client: Forwarded response

_{Reviews (1): Last reviewed commit: "feat: opencode go channel, close #1614" | Re-trigger Greptile}