Summary
Add native OpenCode as an opt-in integration target for APM.
When .opencode/ directory exists in a project, apm install deploys:
- Agents →
.opencode/agents/<name>.md
- Commands →
.opencode/commands/<name>.md (from .prompt.md files)
- Skills →
.opencode/skills/<name>/SKILL.md
- MCP →
opencode.json (new OpenCodeClientAdapter)
OpenCode reads AGENTS.md natively, so apm compile already works for instructions.
Background
@timvw opened PR #257 with initial OpenCode support. That PR conflicts with the architecture refactoring done in PR #301 (Cursor integration), which introduced TargetProfile + KNOWN_TARGETS + data-driven prefix resolution. This issue tracks a proper implementation using the current architecture.
Acceptance Criteria
Summary
Add native OpenCode as an opt-in integration target for APM.
When
.opencode/directory exists in a project,apm installdeploys:.opencode/agents/<name>.md.opencode/commands/<name>.md(from.prompt.mdfiles).opencode/skills/<name>/SKILL.mdopencode.json(newOpenCodeClientAdapter)OpenCode reads
AGENTS.mdnatively, soapm compilealready works for instructions.Background
@timvw opened PR #257 with initial OpenCode support. That PR conflicts with the architecture refactoring done in PR #301 (Cursor integration), which introduced
TargetProfile+KNOWN_TARGETS+ data-driven prefix resolution. This issue tracks a proper implementation using the current architecture.Acceptance Criteria
opencodeTargetProfile in KNOWN_TARGETS.opencode/folderOpenCodeClientAdapterforopencode.jsonMCP format--target opencode)