Skip to content
Pi · claude-opus-4-6featureCLI & tooling1 file · +3 −2

Add pi-side-chat npm package to pi-setup config

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

51ssession
0interventions
GOAL

Add the pi-side-chat extension package to the personal pi-setup repo's settings.json, install it, and commit the change.

  1. Prompt · +0
    Add pi-side-chat (github.com/nicobailon/pi-side-chat) to ~/projects/pi-setup
  2. Agent did · +0m
    Explored pi-setup repo structure, read README, install.sh and settings.json to understand how packages are registered
  3. Agent did · +0m
    Added npm:pi-side-chat to the packages array in settings.json
  4. Agent did · +0m
    Checked README for a packages section, found settings.json is the source of truth so left README unchanged
  5. Agent did · +0m
    Ran pi install npm:pi-side-chat, installed 259 packages successfully
  6. Agent did · +0m
    Committed and pushed the settings.json change to tmustier/pi-setup on GitHub
  7. Outcome · +0m
    pi-side-chat installed and pushed in one commit (1 file, +4/-3 lines) to main
VERDICT

I'd just paste the repo URL and say 'add this as a package' next time — that's basically all it took. The agent correctly figured out settings.json was the source of truth rather than duplicating docs in the README, which saved a step, and the whole thing went through without any corrections needed.

I tried this · 0

Discussion · 0

How Builds work