Repository navigation
feat(opencode): leave lich's operations to its MCP server when lich registered it - #95
Merged
Merged
Conversation
…egistered it A lich that hands opencode its MCP server at spawn puts it under mcp.lich in OPENCODE_CONFIG_CONTENT. The module now defines no tools then, so each operation is listed once and browser_* comes with the rest. An older lich registers nothing and keeps the JavaScript tools.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
lich now hands opencode its MCP server at spawn, as
mcp.lichinOPENCODE_CONFIG_CONTENT(lichdotdev/lich,feat/opencode-mcp-at-spawn). When that entry is present,opencode/lich.jsdefines no tools. Each operation is then listed once, and thebrowser_*tools come with the rest.An older lich registers nothing, and its sessions keep the JavaScript tools as before. lich 0.79 accepts any 0.20.x plugin, so deleting the tools outright would have left those sessions without any. The reports are unaffected in both cases.
Test plan
node --test tests/*.test.mjs: 469 tests pass. Two are new: with the entry present there are no tools and the reports stay; without it, or with an inline config that is not JSON, the tools stay.