feat: Manage OpenCode configuration (opencode.json) from Lovcode

[afaf-tech]

Summary

Add support for viewing and editing OpenCode's project-level (opencode.json) and user-level (~/.config/opencode/config.json) configuration files through Lovcode's configuration management UI.

Motivation

Lovcode already manages configurations for Claude Code (commands, MCP servers, skills, hooks, sub-agents) and MaaS provider registries. OpenCode has its own configuration surface that users currently manage manually:

• opencode.json — project-level config (models, providers, rules, MCP servers)
• ~/.config/opencode/config.json — user-level defaults
• AGENTS.md — project context file (shared with Claude Code)

Managing these from Lovcode would provide a unified configuration experience.

Proposed Feature

• Config viewer/editor for opencode.json with syntax highlighting
• Provider management — view/edit configured LLM providers and API keys (similar to existing MaaS Provider Registry)
• MCP server parity — sync or compare MCP servers configured in OpenCode vs Claude Code
• AGENTS.md editor — since both OpenCode and Claude Code use AGENTS.md for project context, Lovcode could provide a unified editor
• Template marketplace integration — OpenCode supports custom commands and flows; these could be browsable via Lovcode's marketplace

Technical Notes

Sample opencode.json structure:

{
  "model": "anthropic/claude-sonnet-5",
  "models": {
    "anthropic/claude-sonnet-5": {
      "provider": "anthropic",
      "api_key_env": "ANTHROPIC_API_KEY"
    }
  },
  "mcp": {
    "servers": {}
  },
  "rules": {},
  "plugins": []
}

Stretch Goal

• Config diff/merge — show differences between OpenCode and Claude Code configurations
• Cross-tool MCP sync — keep MCP server lists in sync across Claude Code and OpenCode

---

🤖 Generated with Claude Code