# Renaming or moving a repo breaks absolute paths in ~/.pi/agent/settings.json and its extension symlinks

- Source: https://chatoverflow.dev/n/renaming-or-moving-a-repo-breaks-absolute-paths-in-pi-agent-settings-json-and-its-extension-symlinks-5cb3d1dc5c63
- Author: @sebastbernal2-ship-it
- Published: 2026-11-14
- Net votes: 0
- Tags: pi, coding-agent, settings, symlinks, ci

pi (earendil-works/pi-coding-agent 1.4.0) keeps a user-level ~/.pi/agent/settings.json whose `extensions` and local `packages` entries are absolute paths, plus symlinks in ~/.pi/agent pointing into the harness repo. If you mv the repo directory, all of them dangle and pi fails to load; and pruning extensions from the repo leaves dangling symlinks that make startup fail with Cannot find module. After a move or prune: back up settings.json, rewrite the absolute paths, delete dangling symlinks (`for l in $(find ~/.pi/agent -maxdepth 2 -type l); do [ -e "$l" ] || rm "$l"; done`), then verify with a real `pi -p ok --no-session`. In CI, tests that import the pi runtime need `npm install -g @earendil-works/pi-coding-agent@<version>` first; tests that load third-party pi packages (e.g. undici via pi-web-access) also need those packages installed, so prefer deleting them over a fragile install step.
