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

[FEATURE]: opencode could automatically use different models based on task type #5783

New Issue
Open
opened 2026-02-16 17:56:44 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:56:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @saidelike on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

What feature would you like to see?

Leading agentic coding tools enable configurable model selection for different task types executed by the agent; opencode would benefit from adopting a similar approach.

Enable configuration of defaults via environment variables:
- model_reasoning: the model for complex reasoning and architecture decisions (e.g. anthropic/claude-opus-4-20250514")
- model_execution: the model for code generation and implementation (e.g. anthropic/claude-sonnet-4-20250514)
- model_tool: the model for tool execution or background functionality (e.g. anthropic/claude-haiku-4-20250514)

By default, in plan mode, opencode would automatically use model_reasoning for complex reasoning and architecture decisions and use model_tool for efficient execution of tools (find, grep, etc.). By delegating tool execution to the more efficient model and reasoning to the stronger model, we get the best of all worlds for efficient, speed and cost.

Support hybrid settings (e.g., plan), which use a stronger model (model_reasoning) for planning (still using model_tool when appropriate), then switch to a more efficient model (model_execution) for execution (still using model_tool when appropriate).

So in ~/.config/opencode/config.json:

{
  "model": "anthropic/claude-opus-4-20250514",
  "model_reasoning": "anthropic/claude-opus-4-20250514",
  "model_execution": "anthropic/claude-sonnet-4-20250514",
  "model_tool": "anthropic/claude-haiku-4-20250514"
}

or for hybrid mode:

{
  "model": "codeplan",
  "model_reasoning": "anthropic/claude-opus-4-20250514",
  "model_execution": "anthropic/claude-sonnet-4-20250514",
  "model_tool": "anthropic/claude-haiku-4-20250514"
}

Similar issues:

Related issues:

Originally created by @saidelike on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ### What feature would you like to see? Leading agentic coding tools enable [configurable model selection](https://code.claude.com/docs/en/model-config#environment-variables) for different task types executed by the agent; opencode would benefit from adopting a similar approach. Enable configuration of defaults via environment variables: - `model_reasoning`: the model for complex reasoning and architecture decisions (e.g. `anthropic/claude-opus-4-20250514"`) - `model_execution`: the model for code generation and implementation (e.g. `anthropic/claude-sonnet-4-20250514`) - `model_tool`: the model for tool execution or background functionality (e.g. `anthropic/claude-haiku-4-20250514`) By default, in plan mode, opencode would automatically use `model_reasoning` for complex reasoning and architecture decisions and use `model_tool` for efficient execution of tools (`find`, `grep`, etc.). By delegating tool execution to the more efficient model and reasoning to the stronger model, we get the best of all worlds for efficient, speed and cost. Support hybrid settings (e.g., `plan`), which use a stronger model (`model_reasoning`) for planning (still using `model_tool` when appropriate), then switch to a more efficient model (`model_execution`) for execution (still using `model_tool` when appropriate). So in `~/.config/opencode/config.json`: ```json { "model": "anthropic/claude-opus-4-20250514", "model_reasoning": "anthropic/claude-opus-4-20250514", "model_execution": "anthropic/claude-sonnet-4-20250514", "model_tool": "anthropic/claude-haiku-4-20250514" } ``` or for hybrid mode: ```json { "model": "codeplan", "model_reasoning": "anthropic/claude-opus-4-20250514", "model_execution": "anthropic/claude-sonnet-4-20250514", "model_tool": "anthropic/claude-haiku-4-20250514" } ``` Similar issues: - https://github.com/anomalyco/opencode/issues/6976 - https://github.com/anomalyco/opencode/issues/8278 Related issues: - https://github.com/anomalyco/opencode/issues/6558 - https://github.com/anomalyco/opencode/issues/6645 - https://github.com/anomalyco/opencode/issues/6645 - https://github.com/anomalyco/opencode/issues/6651 - https://github.com/anomalyco/opencode/issues/7713
yindo added the discussion label 2026-02-16 17:56:44 -05:00
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 discussion
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#5783
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?