INSTALL

The canonical path is the hero command: pi install git:github.com/686f6c61/Alfred-Pi. Then, in a pi session, /reload. Then a test prompt: «audit the security of this repo». If there are no providers, the assistant offers itself.

No pi yet? pi.dev, 0.84 or later. Want to try without leaving the extension installed? pi -e git:github.com/686f6c61/Alfred-Pi.

If you want the tree on disk (to patch or read packs):

git clone https://github.com/686f6c61/Alfred-Pi
cd Alfred-Pi
ln -sfn "$PWD" ~/.pi/agent/extensions/alfred-pi

Permissions and doctor live in docs/instalacion (Spanish original).

If you come from 0.2.x, update with pi update --all and start a session. The state directory is no longer ~/.pi/agent/pi-harness-moe/; it is~/.pi/agent/alfred-pi/. The first start after updating does not leave you without profiles. If the new directory exists, it is used. If it does not and the old one does, it is copied (not moved) and migrated-from.json is left with the date. The origin is not deleted in 0.3.0. If the origin is a file instead of a directory, it is not copied: the doctor already diagnoses that.

Memory policy is read first from.alfred-pi/memory-policy.json and, if missing, from.pi-harness-moe/. Writes go only to the new one. Yourmodels.json, auth.json andsettings.json are not touched by this move: they belong to pi.

The --harness-moe flag still answers in 0.3.0. The doctor warns that the canonical flag is --alfred-pi. In 0.4.0 the alias is removed. Values (doctor, usage,stack, autopilot, domains and the :json variants) do not change.

pi remove git:github.com/686f6c61/Alfred-Pi
rm -rf ~/.pi/agent/alfred-pi

Removing the symlink does not delete your keys. Keys live in pi's native files. The alfred-pi/ directory is harness state (profiles, health, backups, sonar.env). Delete it only if you want to throw away that house, not pi's.