IDEA integration fails with V2 #54133

Activity

1. github-actions

   assigned

   jlongster

   on Oct 9, 2026
2. opencode-agent commented on Oct 9, 2026

   

   opencode-agentBot

   on Oct 9, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report, @Tcharl!

   The process IntelliJ starts is OpenCode v1 (opencode-ai), not the v2.0.26 you installed. v1 and v2 read the same ~/.config/opencode/opencode.json. v1 deliberately refuses a config that has a v2 permissions block (#45421), which is the error you're seeing. So the request is to have the IntelliJ/ACP-registry OpenCode agent launch v2. Maintainers will consider that.

   In the meantime, v2 has its own acp command, so you can point IntelliJ at it with a custom agent in acp.json (JetBrains ACP docs):

   {
     "agent_servers": {
       "OpenCode v2": {
         "command": "/absolute/path/to/opencode",
         "args": ["acp"]
       }
     }
   }

   Use the full path to the v2 opencode binary (which opencode will show it; opencode --version should print 2.x). Then select OpenCode v2 in the AI Chat agent selector instead of the built-in OpenCode agent.

   Related issues:

   • feat(opencode): load supported v2 config in v1 #45421: the v1 change that rejects v2 permissions in the shared config
   • config: published schema at opencode.ai/config.json rejects documented V2 fields (skills, mcp.*, permissions) #43748: the published config schema rejects valid v2 fields such as permissions
3. opencode-agent

   added

   2.0

   on Oct 9, 2026
4. hussain commented on Oct 11, 2026

   

   hussain

   on Oct 11, 2026

   More actions

   The ACP registry, which IntelliJ's agent list is built from, has an open PR adding OpenCode 2 as a separate opencode-v2 entry alongside the v1 opencode one: agentclientprotocol/registry#657. We tested it on Linux and Windows (report in the PR). It's waiting on review, and a word from an OpenCode maintainer there would likely help it land.
5. opencode-agent commented on Oct 16, 2026

   

   opencode-agentBot

   on Oct 16, 2026 – with OpenCode Agent

   Contributor

   More actions

   Closing this. OpenCode itself isn't at fault here. IntelliJ starts its built-in OpenCode agent, which is OpenCode V1, and V1 deliberately refuses a shared opencode.json that contains V2 permissions. The error you saw comes from that check.

   You can switch now by adding a custom agent in IntelliJ's acp.json that runs your V2 binary with opencode acp, as described in the earlier comment. The change that adds OpenCode 2 to IntelliJ's agent list is tracked in the ACP registry at agentclientprotocol/registry#657.
6. opencode-agent

   closed this as not plannedon Oct 16, 2026
7. hussain commented on Oct 21, 2026

   

   hussain

   on Oct 21, 2026

   More actions

   For anyone landing here: OpenCode V2 is now in the ACP registry as opencode-v2 (agentclientprotocol/registry#657), so IntelliJ's agent list offers it directly, with no acp.json entry needed.