jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

global setup and configuration.

Browse Source
This commit is contained in:
jb
2026-08-24 16:33:11 -04:00
parent 10f64b593b
commit 31c9363dbb
95 changed files with 12641 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -4
View File
@@ -46,14 +46,16 @@ npm run typecheck
Extensions are TypeScript modules loaded directly by Pi; no build step is required.
For live development, the global extension entries can point at this checkout:
Repository-managed global instructions, skills, and extension exposure are declared in [`config/pi-links.json`](config/pi-links.json) and reconciled by one script:
```bash
ln -s /absolute/path/to/harness-tools/extensions/effort-controls ~/.pi/agent/extensions/effort-controls
ln -s /absolute/path/to/harness-tools/extensions/update ~/.pi/agent/extensions/update
./scripts/pi-links.mjs check
./scripts/pi-links.mjs sync --dry-run
./scripts/pi-links.mjs sync
./scripts/pi-links.mjs prune --dry-run
```
This checkout is already linked that way. Run `/reload` after editing an extension.
The repository-local `manage-pi-links` skill applies this workflow. Global instructions are linked to Pi and Codex as `AGENTS.md`; Claude receives a `CLAUDE.md` that imports the shared instructions. The manager preserves unrelated global resources and refuses unmanaged destination collisions. Run `/reload` after changing active Pi instruction, skill, or extension exposure.
## License