Pi Local Repo is Just Better
To make your Pi works faster, you must try checkpointing your plugins.
Listing your dependencies
A lot of people used the barebone Pi harness because of its speed. However, certain plugins may hinder this performance benefit due to internet connection or just regular npm bottleneck.
If you want to look at your package/plugin usage. Use pi list and notes everything that has either a git
repository or a downloadable code.
Here's mine:
hanz@debian:~/Documents/Projects/REDACTED$ pi list
User packages:
npm:pi-web-access
/home/hanz/.pi/agent/npm/node_modules/pi-web-access
git:https://github.com/hanzceo/pi-docparser/
/home/hanz/.pi/agent/git/github.com/hanzceo/pi-docparser
git:github.com/HanzCEO/pi-codebase-reader
/home/hanz/.pi/agent/git/github.com/HanzCEO/pi-codebase-reader
../../Documents/OpenSource/pi-params
https://github.com/sting8k/pi-vcc
/home/hanz/.pi/agent/git/github.com/sting8k/pi-vcc
npm:@wienerberliner/pi-arxiv
/home/hanz/.pi/agent/npm/node_modules/@wienerberliner/pi-arxiv
npm:pi-mcp-adapter
/home/hanz/.pi/agent/npm/node_modules/pi-mcp-adapter
npm:pi-autoresearch
/home/hanz/.pi/agent/npm/node_modules/pi-autoresearch
npm:@narumitw/pi-chrome-devtools
/home/hanz/.pi/agent/npm/node_modules/@narumitw/pi-chrome-devtools
git:github.com/mrexodia/kilo-pi-provider
/home/hanz/.pi/agent/git/github.com/mrexodia/kilo-pi-provider
npm:pi-cheap-tool-error-recovery
/home/hanz/.pi/agent/npm/node_modules/pi-cheap-tool-error-recovery
../../Documents/OpenSource/pi-goal
/home/hanz/Documents/OpenSource/pi-goal
How to optimize it
Every time you open up Pi, it uses your internet connection to check for updates. Primarily Pi updates or extensions updates.
This will took too long sometimes, about 10-20+ seconds depending on your configuration.
To speed things up, you need to look into packages that you:
- Do not need anymore
- Installed via npm
- Installed via git
When you have them listed, you can then explore each of those packages for their downloadable code or git repository.
git clone https://github.com/sting8k/pi-vcc
Clone them to your local directory, like so.
cd pi-vcc
pnpm i
pnpm approve-builds --all
pi install pi-vcc
And install it.
When you're done, the list should look a little bit similar to this:
hanz@debian:~/Documents/OpenSource$ pi list
User packages:
npm:pi-web-access
/home/hanz/.pi/agent/npm/node_modules/pi-web-access
../../Documents/OpenSource/pi-params
../../Documents/OpenSource/pi-goal
/home/hanz/Documents/OpenSource/pi-goal
../../Documents/OpenSource/pi-docparser
/home/hanz/Documents/OpenSource/pi-docparser
../../Documents/OpenSource/pi-codebase-reader
/home/hanz/Documents/OpenSource/pi-codebase-reader
../../Documents/OpenSource/pi-cheap-tool-error-recovery
/home/hanz/Documents/OpenSource/pi-cheap-tool-error-recovery
../../Documents/OpenSource/pi-vcc
/home/hanz/Documents/OpenSource/pi-vcc
../../Documents/OpenSource/pi-arxiv
/home/hanz/Documents/OpenSource/pi-arxiv
Now it should load much better!