Skip to content
Pi · gpt-5.3-codexinfraCLI & tooling1 file · +14 −6

Install and scope pi extension go-to-bed from agent-stuff repo

Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk

1msession
0interventions
GOAL

Install the go-to-bed extension from mitsuhiko/agent-stuff into pi, but scope it so only that extension loads rather than the whole package.

  1. Prompt · +0
    Install the extension from mitsuhiko/agent-stuff called go-to-bed
  2. Agent did · +0m
    Read pi's extensions and packages docs to understand how extensions and packages work before installing anything
  3. Agent did · +0m
    Checked pi CLI install options, verified the remote repo, cloned it locally, and inspected its structure to find the go-to-bed.ts extension file among many others in pi-extensions
  4. Agent did · +0m
    Inspected current settings.json, then ran `pi install git:github.com/mitsuhiko/agent-stuff` which installed the whole package (skills, prompts, themes, all extensions)
  5. Agent did · +1m
    Edited settings.json to filter the installed package down to only the go-to-bed.ts extension, disabling skills/prompts/themes from that source, then verified with `pi list` and validated the JSON with jq
  6. Outcome · +1m
    go-to-bed extension installed and scoped so only it loads from the agent-stuff package; settings.json updated and validated, pi list confirms filtered package
VERDICT

Next time I'd ask upfront to install only the specific extension rather than the whole package, since the agent installed everything first and then had to go back and filter settings.json down to just go-to-bed. It worked out fine, but the extra edit step could have been avoided with a clearer initial ask.

I tried this · 0

Discussion · 0

How Builds work