You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to create a code question-answering tool. I need to ask some questions from the code repository and then open code will explain it to me. Based on this, I will create an API to expose it externally. I have noticed that currently Open Code only runs on the command line and does not provide SDK or MCP services to developers (although other MCP services can be used, it cannot provide services externally). I believe that more than just me requires this feature, because the code interpretation service is a very useful function, especially in the future when we need to jointly search for answers or bugs from multiple code repositories (for example, adding Open Code's MCP service for front-end and back-end code repositories to the Claude client).
A runtime layer gives you a safe way to host OpenCode as part of another product.
For “ask questions about a repo and expose it externally,” I would avoid one global OpenCode process shared by all users/repos. I’d run isolated runtime state per repo/user, keep config/permissions scoped to that runtime, stream responses back to the external API, and have a cleanup path for stale or stuck sessions.
That runtime concern is separate from whether the control surface is MCP, HTTP, or SDK. The control surface is the interface; the runtime is the thing that owns process lifecycle, workspace isolation, health checks, and session reuse.
Activity
barshag commentedon Jul 11, 2025
Support- like claude code sdk!
thdxr commentedon Aug 27, 2025
https://www.npmjs.com/package/@opencode-ai/sdk
Refresh the Den landing page (anomalyco#865)
ashish16052 commentedon Jul 9, 2026
This is a useful distinction:
For “ask questions about a repo and expose it externally,” I would avoid one global OpenCode process shared by all users/repos. I’d run isolated runtime state per repo/user, keep config/permissions scoped to that runtime, stream responses back to the external API, and have a cleanup path for stale or stuck sessions.
That runtime concern is separate from whether the control surface is MCP, HTTP, or SDK. The control surface is the interface; the runtime is the thing that owns process lifecycle, workspace isolation, health checks, and session reuse.