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
{{ message }}
Repository navigation
Support OpenCode agents and document MCP/LSP setup #1359
I use the .NET skills with OpenCode 1.19.0 on Windows. I installed the portable skills from this repository using gh skill install --agent opencode, and OpenCode discovers them successfully.
I would also like to use the accompanying agents and integrations through an upstream-supported setup, without maintaining my own converters or adapted copies.
The README already distinguishes portable skills/MCP servers from host-specific agents. Is native OpenCode support planned for the remaining components?
In particular:
Agents and delegation: Is there a supported way to use the test-generation workflow and its specialist agents in OpenCode? Copilot tool lists, agent references and handoffs are not automatically imported by OpenCode.
Skill invocation controls: OpenCode 1.x does not interpret fields such as user-invocable and disable-model-invocation. How should skills intended only for internal workflow use be exposed?
MCP and LSP: Could you document the supported OpenCode configuration for the Binlog MCP server and clarify whether OpenCode’s built-in Roslyn integration is the recommended C# language-server setup?
Ideally, the repository would provide native OpenCode definitions where needed, along with installation and update instructions. If some components are intentionally Copilot-only, an explicit compatibility matrix would also help.
Summary: This requests first-class OpenCode compatibility for host-specific agents and skill invocation controls, plus supported MCP/LSP configuration guidance. The primary area is area-infrastructure because the work is cross-cutting across plugin packaging, host integration, installation, and compatibility documentation.
Type: enhancement Assigned owners:@webreidi and @AbhitejJohn Confidence: Medium Similar issues:#1006 tracks broader Agent Plugins 1.0 adoption, and #1112 explores overlays for portable skills. Both are related, but neither appears to duplicate the OpenCode-specific support and documentation request.
Triage details
Area mapping rationale: Although the examples include testing agents, Binlog MCP, and Roslyn LSP, the core request is native support for another agent host across several components.
CODEOWNERS path match: No single plugin path covers the request, so the repository-wide * ownership rule applies.
Confidence rationale: The enhancement classification is clear, but individual implementation pieces may later be split among testing, MSBuild/diagnostics, and Roslyn owners.
Suggested next step: Define the intended OpenCode support boundary and compatibility matrix, then decide whether native definitions belong in the existing plugin packages or a host-specific overlay.
Activity
github-actions commentedon Oct 27, 2026
🎯 Issue Triage
Summary: This requests first-class OpenCode compatibility for host-specific agents and skill invocation controls, plus supported MCP/LSP configuration guidance. The primary area is
area-infrastructurebecause the work is cross-cutting across plugin packaging, host integration, installation, and compatibility documentation.Type: enhancement
Assigned owners:
@webreidiand@AbhitejJohnConfidence: Medium
Similar issues: #1006 tracks broader Agent Plugins 1.0 adoption, and #1112 explores overlays for portable skills. Both are related, but neither appears to duplicate the OpenCode-specific support and documentation request.
Triage details
*ownership rule applies.