docs: simplify README — separate user and dev install sections
6b351accda4c6ccfaa6e95732fc2a67424a77928
Oliver Jan Krylow <oliver@bugabinga.net> · 2026-06-05 20:01 UTC
unsigned 1 parent
repositories / pi-ext
pi-ext
bugabingas pi extensions
owned by admin
Changed files (1)
README.md
ready@@ -9,31 +9,21 @@
Never `pi ext install`.
That corpse stays buried.
-All extensions via git, pinned:
+Pinned version:
```bash
pi install git:github.com/bugabinga/pi-ext@v0.0.3
```
-Default branch install:
+Default branch:
```bash
pi install git:github.com/bugabinga/pi-ext
```
-Local checkout, absolute path:
+### Filtering
-```bash
-pi install /home/me/Workspace/pi-ext
-```
-
-Local checkout, `~` path:
-
-```bash
-pi install ~/Workspace/pi-ext
-```
-
-Single-extension package filter in `~/.pi/agent/settings.json`:
+Load only a subset via `~/.pi/agent/settings.json`:
```json
{
@@ -130,6 +120,31 @@
Less accounting.
Fewer tiny coffins.
+## Development
+
+Clone locally, install dependencies, then point Pi at the path:
+
+```bash
+git clone https://github.com/bugabinga/pi-ext.git
+cd pi-ext
+bun install
+pi install /absolute/path/to/pi-ext
+```
+
+Or add to `~/.pi/agent/settings.json`:
+
+```json
+{
+ "packages": [
+ {
+ "source": "/absolute/path/to/pi-ext"
+ }
+ ]
+}
+```
+
+> **Note:** Local paths and git sources both require manual dependency installation. Pi runs `npm install --omit=dev` for git sources, but ignores `bun.lock`. In practice npm 7+ resolves the workspace correctly. For local development, run `bun install` inside the repo first.
+
---
Fat prompts rot in bins.\