Skip to content
Pi · gpt-5.4debugCLI & tooling1 file · +16 −13

Restore missing pi-extensions and re-enable disabled extensions

Session from heypocket-reader-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk

5msession
0interventions
GOAL

Recover the developer's tmustier/pi-extensions package which appeared to have disappeared, and ensure files-widget, code-actions, extending-pi and raw-paste extensions are enabled alongside ralph-wiggum.

  1. Prompt · +0
    tmustier/pi-extensions has disappeared, please grab it again
  2. Agent did · +0m
    Searched local filesystem and .pi cache for pi-extensions, found it already present locally, checked git status/remote and confirmed up to date with origin/main, also checked settings.json for references
  3. Agent did · +1m
    Reported that pi-extensions was never actually missing - it's already cloned locally, wired into Pi, and up to date; offered to clone a visible working copy
  4. Prompt · +4m
    Does it need updating? I currently only have ralph-wiggum enabled but want files-widget, code-actions, extending-pi and raw-paste too
  5. Agent did · +4m
    Read Pi docs on extensions, packages and settings, inspected package.json files for each extension in the repo, and checked settings.json structure and symlinks to understand why only ralph-wiggum was enabled
  6. Agent did · +5m
    Edited settings.json to add files-widget, code-actions and raw-paste extensions to the enabled list alongside ralph-wiggum, then validated the JSON with a python script confirming the new package entry
  7. Outcome · +5m
    No re-clone was needed; settings.json updated to enable files-widget, code-actions, raw-paste alongside ralph-wiggum, with extending-pi confirmed as an already-enabled skill; developer told to run /reload
VERDICT

Next time I'd skip straight to asking why only ralph-wiggum was showing up instead of assuming the whole package had vanished — the repo was fine all along, it was a settings.json filter. Digging into the package.json files and settings docs is what actually found the real problem, so I'd lead with 'why are only some extensions enabled' rather than 're-fetch this package'.

I tried this · 0

Discussion · 0

How Builds work