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 Request: Integrate MorphLLM for edit-tool #1099

New Issue
Closed
opened 2026-02-16 17:29:27 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:29:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @ethan-huo on GitHub (Aug 4, 2025).

Originally assigned to: @thdxr on GitHub.

Consider integrating MorphLLM as a configurable engine for applying AI-generated diffs.

It's specialized for this task, offering high speed and accuracy, with an OpenAI-compatible API. This could improve the reliability of applying complex, multi-file changes.

Originally created by @ethan-huo on GitHub (Aug 4, 2025). Originally assigned to: @thdxr on GitHub. Consider integrating [MorphLLM](https://morphllm.com) as a configurable engine for applying AI-generated diffs. It's specialized for this task, offering high speed and accuracy, with an OpenAI-compatible API. This could improve the reliability of applying complex, multi-file changes.
yindo closed this issue 2026-02-16 17:29:27 -05:00
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@garrett-hopper commented on GitHub (Aug 29, 2025):

Been having great luck with the MorphLLM MCP server. Great thing about opencode vs claude-code is that the builtin file tools can be disabled instead of having to beg Claude in a context file to always use the right one.

https://morphllm.com/mcp
https://docs.morphllm.com/guides/claude-code

In my opencode.jsonc file:

{
  "mcp": {
    "filesystem": {
      "enabled": true,
      "type": "local",
      "command": ["npx", "@morph-llm/morph-fast-apply"],
      "environment": {
        "MORPH_API_KEY": "sk-...",
        "ALL_TOOLS": "true",
      },
    },
  },
  "tools": {
    "read": false,
    "edit": false,
    "write": false,
    "list": false,
    "glob": false,
    "grep": false,
    "filesystem_read_file": true,
    "filesystem_read_multiple_files": true,
    "filesystem_list_directory": true,
    "filesystem_list_directory_with_sizes": true,
    "filesystem_directory_tree": true,
    "filesystem_search_files": true,
    "filesystem_get_file_info": true,
    "filesystem_create_directory": true,
    "filesystem_move_file": true,
    "filesystem_edit_file": true, // <-- Only ALL_TOOLS=false tool
    "filesystem_tiny_edit_file": true,
    "filesystem_write_file": true,
    "filesystem_list_allowed_directories": true,
    // OR: "filesystem*": true,
  },
}

Of course the filesystem tools don't need to be listed in tools unless you intend to disable some of them.

I'm currently using ALL_TOOLS=true to try all of them. I don't really know if the non-morph filesystem tools the MCP provides are better or worse than the builtin opencode tools. 🤷

filesystem_list_allowed_directories is not useful until MCP Roots are supported.

@garrett-hopper commented on GitHub (Aug 29, 2025): Been having great luck with the MorphLLM MCP server. Great thing about opencode vs claude-code is that the builtin file tools can be disabled instead of having to beg Claude in a context file to always use the right one. https://morphllm.com/mcp https://docs.morphllm.com/guides/claude-code In my `opencode.jsonc` file: ```jsonc { "mcp": { "filesystem": { "enabled": true, "type": "local", "command": ["npx", "@morph-llm/morph-fast-apply"], "environment": { "MORPH_API_KEY": "sk-...", "ALL_TOOLS": "true", }, }, }, "tools": { "read": false, "edit": false, "write": false, "list": false, "glob": false, "grep": false, "filesystem_read_file": true, "filesystem_read_multiple_files": true, "filesystem_list_directory": true, "filesystem_list_directory_with_sizes": true, "filesystem_directory_tree": true, "filesystem_search_files": true, "filesystem_get_file_info": true, "filesystem_create_directory": true, "filesystem_move_file": true, "filesystem_edit_file": true, // <-- Only ALL_TOOLS=false tool "filesystem_tiny_edit_file": true, "filesystem_write_file": true, "filesystem_list_allowed_directories": true, // OR: "filesystem*": true, }, } ``` Of course the `filesystem` tools don't need to be listed in `tools` unless you intend to disable some of them. I'm currently using `ALL_TOOLS=true` to try all of them. I don't really know if the non-morph filesystem tools the MCP provides are better or worse than the builtin opencode tools. 🤷 `filesystem_list_allowed_directories` is not useful until [MCP Roots](https://github.com/sst/opencode/issues/2308) are supported.
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@garrett-hopper commented on GitHub (Aug 29, 2025):

Note: There appears to be issues when the Morph MCP server detects the root as being above the working directory that opencode is running in. Bash tool will show as the working directory, however files created by the MCP tools will be in the root, leading to confusion.
Not an issue as long as you start opencode in the directory that will be discovered by the MCP server as the root anyways. (.git, package.json, probably other markers as well)

@garrett-hopper commented on GitHub (Aug 29, 2025): Note: There appears to be issues when the Morph MCP server detects the root as being above the working directory that opencode is running in. Bash tool will show as the working directory, however files created by the MCP tools will be in the root, leading to confusion. Not an issue as long as you start opencode in the directory that will be discovered by the MCP server as the root anyways. (`.git`, `package.json`, probably other markers as well)
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
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
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#1099
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?