feat(runner): wizard tools as pi custom tools — real integration on pi (#524)#694
feat(runner): wizard tools as pi custom tools — real integration on pi (#524)#694gewenyu99 wants to merge 1 commit into
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
f31aa09 to
c6c7870
Compare
2c64ec7 to
4ca7292
Compare
|
I defer to your superior insight on the current state of things, but if you'd prefer NOT to own MCP, you might find a project like this interestiing: https://github.com/nicobailon/pi-mcp-adapter Built in tool search and all the other stuff we want. but also I DO remember the MCP shenanigans we once encountered, so building the tools bespoke for the agent makes a lot of sense. |
|
Noted! @daniloc |
d020534 to
6283374
Compare
4ca7292 to
d859fb8
Compare
6283374 to
bd5cee4
Compare
809cce2 to
bbb2215
Compare
bd5cee4 to
93a0b5d
Compare
pi registers the wizard env-file tools (createWizardPiTools) as pi custom tools, so a pi run can manage .env keys the same way the anthropic path does. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
93a0b5d to
1ad2caf
Compare
bbb2215 to
9fc690c
Compare

Epic #520 · part of #524 (pi has no MCP — wizard capabilities become custom tools).
Problem
Changes
load_skill_menu/install_skill+ fenced.envops (check_env_keys/set_env_values) as pidefineToolcustom tools, reusing the shared env-file logic.Test plan
.envvia the env tool (not raw file writes) and loads/exercises the same framework skill asanthropic.