Two directories documented one concept (pi npm packages): top-level packages/ (browser-use, permission-system) and pi/packages/ (peon, web-access, subagents). Merged into pi/packages/ — one row per package in a single index, detail pages kept as archive records. The root index's 'OMP packages and skills' section was doubly wrong (packages/ was pi, not OMP); it becomes a Skills tooling section pointing at the consolidated /skills/ tree. Moved the two LIVE omp pages out of the retired-harness banner: pi/statusline.md -> core/statusline.md, pi/subagent-limits.md -> core/subagent-limits.md (both document omp behavior against agent/config.yml + the installed bundle; pi/index.md itself admitted the mis-shelf). Retargeted every inbound link (core/index, system/ dankserver, log x2, pi/index, settings x2, moved files' own xrefs). Refs #29
54 lines
2.2 KiB
Markdown
54 lines
2.2 KiB
Markdown
# Pi Configuration (archive)
|
|
|
|
> **Archive (2026-10-18).** This directory documents the retired **pi** harness
|
|
> (`settings.json` / `models.json`, `frank-default-*` endpoints). The live
|
|
> harness is **omp**: config in `agent/config.yml` + `agent/models.yml` (this
|
|
> repo), fleet endpoints on [System hosts](/system/index.md). Read these pages
|
|
> as historical records, not current state. Knowledge that survived the harness
|
|
> move lives under [Core](/core/index.md):
|
|
> [OMP Status Line](/core/statusline.md) and
|
|
> [OMP Subagent Limits](/core/subagent-limits.md).
|
|
|
|
## Configuration Files (pi-era)
|
|
|
|
- [Pi Settings System (settings.json)](/core/settings.md) — Main `settings.json` record. Providers, models, packages, subagent overrides.
|
|
- [Pi Models Configuration](/pi/models.md) — `models.json` record. Provider definitions, model specs, endpoints.
|
|
|
|
## Extensions (pi-era)
|
|
|
|
- [Pi Packages](/pi/packages/index.md) — installed npm packages: peon, web-access, subagents, browser-use, permission-system.
|
|
|
|
## Skills (pi-era)
|
|
|
|
- [Pi Skills](/pi/skills.md) — installed skills inventory. Current skill toolchain: [Skills](/skills/index.md).
|
|
|
|
## Architecture (pi-era)
|
|
|
|
```mermaid
|
|
graph TD
|
|
A[Pi TUI] --> B[settings.json]
|
|
A --> C[models.json]
|
|
B --> D[Default Provider: llamacpp]
|
|
B --> E[Default Model: frank-default-large]
|
|
B --> F[Packages]
|
|
B --> G[Subagent Overrides: local frank models]
|
|
F --> H[pi-peon]
|
|
F --> I[pi-web-access]
|
|
F --> J[pi-browser-use]
|
|
F --> K[pi-permission-system]
|
|
G --> L[Small: scout, researcher]
|
|
G --> M[Large: planner, worker, reviewer, oracle, context-builder]
|
|
L --> N[dankserver 192.168.0.235:7770]
|
|
M --> O[dankclaw 192.168.0.143:7770]
|
|
```
|
|
|
|
## Note on the Live Default (historical)
|
|
|
|
In the pi era, `models.json` defined the live provider set: the main session
|
|
provider was `llamacpp` with default model `frank-default-large` (Dankclaw);
|
|
subagents defaulted to `frank-default-small` (Dankserver); larger roles mapped
|
|
to `frank-default-large`. Two scopes owned settings: the user
|
|
`~/.pi/settings.json` (main → Dankclaw/large) and the project
|
|
`/home/dank/.pi/agent/settings.json` (main → Dankserver/small); when they
|
|
disagreed, the project-scope file won for the agent's own main session.
|