Skip to content

ACP sessions ignore model selection from Intent (and other ACP clients) #13644

Closed

Description

@AlexisGrrd

Description

When using Opencode via ACP (Agent Client Protocol) with Intent (or potentially other ACP clients), the model selected in the client is not properly applied to the session. Instead, Opencode defaults to big-pickle.

Expected behavior:

  • The message should be processed using the model selected in Intent (e.g., kimi-k2.5-free)
    Actual behavior:
  • The message is processed using big-pickle (the default model)
  • However, the agent context in the system prompt correctly shows the selected model

Evidence:

  • Agent context correctly shows: "Selected Model": "opencode:opencode/kimi-k2.5-free"
  • But message record shows: "model":{"providerID":"opencode","modelID":"big-pickle"}

Potential root cause:
Looking at packages/opencode/src/acp/session.ts, the create() method doesn't properly handle the model parameter when passed by ACP clients. The fix in PR #9829 addressed loading existing sessions, but not creating new sessions with a specific model.

Related issues:

Plugins

No response

OpenCode version

1.2.2

Steps to reproduce

  1. Open Intent and select Kimi 2.5 (or any non-default model) as the model
  2. Send a message to Opencode via ACP
  3. Check the session in Opencode database - the message will show the wrong model

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. AlexisGrrd commented on Feb 14, 2026

    @AlexisGrrd
    Author

    Additional evidence captured (Feb 14, 2026):

    • Message sent: "Test for opencode git issue"
    • Agent context shows: "Selected Model": "opencode:opencode/kimi-k2.5-free" ✅
    • Message metadata shows: "model":{"providerID":"opencode","modelID":"big-pickle"} ❌

    This confirms the bug is consistent - the agent context correctly displays the selected model, but Opencode internally processes messages with the wrong model.

  2. marcdeop commented on Feb 16, 2026

    @marcdeop

    I am also facing this problem when attempting to integrate with codecompanion

    I have a custom config on opencode.json

    {
      "$schema": "https://opencode.ai/config.json",
      "theme": "tokyonight",
      "provider": {
        "amazon-bedrock": {
          "options": {
            "region": "eu-central-1"
          },
          "models": {
            "my-fancy-model": {
              "id": "arn:aws:bedrock:eu-central-confidential-information-here"
            }
          }
        }
      }
    }
    

    I always get this in the debug output: currentModelId = "opencode/big-pickle"

    and when asking the agent itself:

    Image
  3. AlexisGrrd commented on Feb 16, 2026

    @AlexisGrrd
    Author

    Linking this for potential further investigations

  4. AlexisGrrd commented on Feb 18, 2026

    @AlexisGrrd
    Author

    Did you find a workaround @marcdeop ? This is breaking my workflow

  5. AlexisGrrd commented on Feb 23, 2026

    @AlexisGrrd
    Author

    Fixed by AugmentCode team

  6. velouria commented on Jun 30, 2026

    @velouria

    I'm still seeing this issue in OpenCode 1.17.11 with Xcode 27 beta 2 as the ACP client. It always defaults to big-pickle in create: model.id=big-pickle model.providerID=opencode.
    Is there any workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions