anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

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

New Issue
Open
opened 2026-02-16 18:12:15 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 18:12:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @AlexisGrrd on GitHub (Feb 14, 2026).

Originally assigned to: @rekram1-node on GitHub.

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:

  • #9828 (ACP loadSessionMode doesn't set model and mode)
  • #4001 (Configure default model is not used in ACP)
  • #8680 (ACP and headless mode does not respect default agent definition)

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

Originally created by @AlexisGrrd on GitHub (Feb 14, 2026). Originally assigned to: @rekram1-node on GitHub. ### 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: - #9828 (ACP loadSessionMode doesn't set model and mode) - #4001 (Configure default model is not used in ACP) - #8680 (ACP and headless mode does not respect default agent definition) ### 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_
yindo added the bug label 2026-02-16 18:12:15 -05:00
yindo commented 2026-02-16 18:12:15 -05:00
Author
Owner
Copy Link
Copy Source

@AlexisGrrd commented on GitHub (Feb 14, 2026):

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.

@AlexisGrrd commented on GitHub (Feb 14, 2026): **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.
yindo commented 2026-02-16 18:12:15 -05:00
Author
Owner
Copy Link
Copy Source

@marcdeop commented on GitHub (Feb 16, 2026):

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
@marcdeop commented on GitHub (Feb 16, 2026): I am also facing this problem when attempting to integrate with [codecompanion](https://codecompanion.olimorris.dev/configuration/adapters-acp#setup-opencode) 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: <img width="665" height="222" alt="Image" src="https://github.com/user-attachments/assets/97ea6e05-af88-4b3a-b349-0723e590dd65" />
yindo commented 2026-02-16 18:12:15 -05:00
Author
Owner
Copy Link
Copy Source

@AlexisGrrd commented on GitHub (Feb 16, 2026):

Linking this for potential further investigations

@AlexisGrrd commented on GitHub (Feb 16, 2026): Linking [this](https://x.com/alexatallah/status/2023117967853334591?s=20) for potential further investigations
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9353
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?