feat: OpenCode agent component (ENG-100) #236
Conversation
Adds the new OpenCode agent component with configurable 'providerConfig'. Refactors common gateway token logic into a shared 'utils.ts' used by both AI Agent and OpenCode. Signed-off-by: betterclever <paliwal.pranjal83@gmail.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a03de01336
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| env: { | ||
| // OpenCode might need API keys. | ||
| // If the definition includes an API Key in the 'model' contract, we should pass it. | ||
| ...(model?.apiKey | ||
| ? { OPENAI_API_KEY: model.apiKey, ANTHROPIC_API_KEY: model.apiKey } | ||
| : {}), |
There was a problem hiding this comment.
The component accepts the shared LLMProviderSchema, which includes gemini and openrouter providers, but the container environment only forwards OPENAI_API_KEY/ANTHROPIC_API_KEY. When a user selects gemini or openrouter and supplies an API key in the model input, no provider-specific key is passed into the OpenCode container, so authentication will fail unless they manually duplicate it via providerConfig. This makes those providers effectively unusable despite being allowed by the contract.
Useful? React with 👍 / 👎.
ENG-100 — OpenCode Agent Component
Summary
What changed
worker/src/components/ai/opencode.ts.How it works (high level)
Testing
Notes
Refs: ENG-100