Add pi install instructions to pi-extensions READMEs
Session from pi-mono-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Click a segment to jump to that moment
11msession
1interventions
by library · 1d
GOAL
Sync a local repo with upstream, then add pi package-manager install commands to the README of each extension in the tmustier/pi-extensions repo.
- +0Prompt · +0git pull origin main
- +0mFail · +0mPull failed due to local changes and untracked files blocking merge
- +0mPrompt · +0mDiscard local changes
- +0mAgent did · +0mDiscarded local changes and untracked .gitignore files, then pulled and fast-forwarded to latest main
- +0mPrompt · +0mApparently there's now a way to install pi extensions with a command?
- +0mAgent did · +0mSearched pi-coding-agent docs and pi-mono source to find the new pi install/remove/list/update package commands and explained their settings.json integration
- +2mPrompt · +2mCan we please look at pi-extensions and then add installation commands in the readmes of each extension?
- +6mIntervention · +6mDeveloper stopped the agent from editing files inside pi-mono and redirected it to the separate ~/pi-extensions repoWhy: It started poking around in the pi-mono source again instead of the actual extensions repo I wanted changed, so I had to point it at the right folder.
- +6mAgent did · +6mSurveyed every extension folder in ~/pi-extensions, then edited each README (agent-guidance, arcade, code-actions, usage-extension, raw-paste, ralph-wiggum, relaunch, tab-status, files-widget, top-level README) to add pi install commands, and added a new package.json manifest listing extension entrypoints
- +10mPrompt · +10mCommit/push all the readmes and the new package.json, but don't touch other unrelated changes
- +11mOutcome · +11mCommitted and pushed exactly 11 touched files (10 READMEs + package.json) to pi-extensions main, leaving other local changes untouched
VERDICT
Next time I'd start by pointing straight at ~/pi-extensions instead of letting it dig around in pi-mono's source first - that redirect was the correction that actually got it moving in the right direction. Once scoped correctly it did a clean sweep of all the READMEs and respected my instruction to only commit the files it had actually touched, which mattered since there were other unrelated local changes sitting in that repo.