You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched open and closed issues and did not find a report of this problem.
Problem
After #1274, extensions/ask-user-question.ts registers the tool name ask_user_question. Pi treats tool names as exclusive across extensions, so a previously valid install that still has npm:@juicesharp/rpiv-ask-user-question fails at extension load and never starts a session.
This is the same class as closed #607 (todo vs @juicesharp/rpiv-todo). #833 asked for a first-party questionnaire so Gentle would not depend on that external tool. #1274 shipped that replacement, but the package-side migration did not.
Two docs still tell people to install the colliding companion:
README.md optional companions table: @juicesharp/rpiv-ask-user-question for "Interactive choice support"
docs/readme-reference.md recommended install list: pi install npm:@juicesharp/rpiv-ask-user-question
The extension comment already names juicesharp, states that a duplicate name is a hard load error, and says removal from Pi settings is the migration path. That path is not user-facing: no changelog gate, no startup diagnostic with the exact pi remove command. pi update --extensions on git:github.com/Gentleman-Programming/gentle-pi@main therefore turns a working stack into a dead session.
Steps to reproduce
Keep both packages in Pi settings: npm:@juicesharp/rpiv-ask-user-question and git:github.com/Gentleman-Programming/gentle-pi@main (or any install that loads both extensions).
Sessions stay bootable after the first-party questionnaire ships.
Either the old package is removed/disabled, or load fails with one diagnostic that names the conflict and pi remove npm:@juicesharp/rpiv-ask-user-question.
README / docs/readme-reference.md stop recommending the companion once Gentle owns ask_user_question.
Error: Failed to load extension "<agent-home>/git/github.com/Gentleman-Programming/gentle-pi/extensions/ask-user-question.ts": Tool "ask_user_question" conflicts with <agent-home>/npm/node_modules/@juicesharp/rpiv-ask-user-question/index.ts
Hint: Start without extensions using "pi -ne".
Before submitting
Problem
After #1274,
extensions/ask-user-question.tsregisters the tool nameask_user_question. Pi treats tool names as exclusive across extensions, so a previously valid install that still hasnpm:@juicesharp/rpiv-ask-user-questionfails at extension load and never starts a session.This is the same class as closed #607 (
todovs@juicesharp/rpiv-todo). #833 asked for a first-party questionnaire so Gentle would not depend on that external tool. #1274 shipped that replacement, but the package-side migration did not.Two docs still tell people to install the colliding companion:
README.mdoptional companions table:@juicesharp/rpiv-ask-user-questionfor "Interactive choice support"docs/readme-reference.mdrecommended install list:pi install npm:@juicesharp/rpiv-ask-user-questionThe extension comment already names juicesharp, states that a duplicate name is a hard load error, and says removal from Pi settings is the migration path. That path is not user-facing: no changelog gate, no startup diagnostic with the exact
pi removecommand.pi update --extensionsongit:github.com/Gentleman-Programming/gentle-pi@maintherefore turns a working stack into a dead session.Steps to reproduce
npm:@juicesharp/rpiv-ask-user-questionandgit:github.com/Gentleman-Programming/gentle-pi@main(or any install that loads both extensions).extensions/ask-user-question.tsfrom feat(ask): native ask_user_question with a scrollable dock-swap dialog #1274 loads.-p).Expected and actual behavior
Expected:
pi remove npm:@juicesharp/rpiv-ask-user-question.docs/readme-reference.mdstop recommending the companion once Gentle ownsask_user_question.Actual:
pi -ne, which disables every extension and is not a usable workaround.gentle-pi version
3.3.0 (
f2d9d073, #1274 onmain)Pi version
0.86.1
Operating system
macOS
Relevant logs or error output (optional)