Sync opencode tool changes from v1.4.11#31
Merged
Conversation
This was referenced Apr 19, 2026
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
Sync the
packages/opencodetool slice toward the upstreamv1.4.11shape for PR2.filetimeandlisttool pathsread,write,edit,glob,grep,skill, and registry wiring with upstream behaviortrashtool and restore its guardrails and testsWhy
Issue #27 tracks the broader multi-PR graft from upstream
opencode v1.4.6tov1.4.11.This PR only lands the
opencode-toolslice, including the localtrashtool difference that PawWork keeps on purpose.Related Issue
Part of #27
How To Verify
Screenshots or Recordings
N/A, no visible UI changes.
Checklist
devbranch