Repository navigation
Conversation
proto 0.60+ fails to load the plugin with "missing field `tool_dir`" because it was built against proto_pdk 0.32. Upgrade to proto_pdk 0.36 and the matching dev-dependencies. Pin pest to 2.9.2 (as proto itself does): 2.9.4 pulls in stacker/psm, which imports env::rust_psm_stack_pointer and makes proto reject the wasm as an incompatible runtime. Pin iocraft-macros to 0.2.4 so the test dependencies compile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pest 2.9.2 pin previously only lived in Cargo.lock, so a plain `cargo update` would move to 2.9.4 and reintroduce the psm import that proto rejects. Add pest as an exact direct dependency so it survives lockfile updates, and stop Renovate from bumping it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
On proto 0.60+ (tested on 0.63.2),
proto install claude-codefails:The plugin is built against
proto_pdk0.32, which predates the current plugin API.Changes
proto_pdk0.32.7 → 0.36.0, plus the matching dev dependencies (proto_pdk_test_utils0.51.1,starbase_sandbox0.12.1). No API changes were needed in the plugin.get_host_environment()now returns a reference, so two redundant&envborrows are removed for clippy.pestto 2.9.2. pest 2.9.4 pulls instacker/psmthrough its defaultstdfeature, which proto'sversion_speccrate turns on. Onwasm32-wasip1this adds anenv::rust_psm_stack_pointerimport, and proto refuses to load the plugin withplugin::wasm::incompatible_runtime. pest is now an exact direct dependency (proto's own lockfile is also on 2.9.2), socargo updatecan't move it, and Renovate updates for it are turned off. The pin can go onceversion_specstops enabling pest'sstdfeature, or pest leaves outstackeron wasm.iocraft-macrosto 0.2.4 inCargo.lock. 0.2.5 breaksstarbase_console, a test-only dependency, socargo testdidn't compile.Testing
cargo fmt --check,cargo clippy --target wasm32-wasip1,cargo testand the release wasm build pass.plugins.toolsat the locally built wasm:proto install claude-codeinstalls Claude Code 2.1.308, andproto run claude-code 2.1.308 -- --versionprints2.1.308 (Claude Code).A new tagged release is needed before
github://BarretoTech/proto-claude-code-pluginusers get the fix.🤖 Generated with Claude Code