---
slug: "neuralpartners-pi-yo"
source_type: "readme"
source_url: "https://cdn.jsdelivr.net/gh/Neural-Partners/np-pi@main/README.md"
repo: "https://github.com/Neural-Partners/np-pi"
source_file: "README.md"
branch: "main"
---
# np-pi

Neural Partners' public home for Pi packages, extensions, skills, prompts, themes, and related tooling.

## What lives here

- `packages/*` — public npm packages that can be installed by Pi.
- `local/` — local experiments and personal packages; contents are gitignored except the README.
- `private/` — Neural Partners internal or customer-specific packages; contents are gitignored except the README.
- `docs/` — repo conventions, publishing notes, and implementation specs/plans.

## Current public packages

| Package                 | Purpose                                                                                         | Install                                |
| ----------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------- |
| `@neuralpartners/pi-yo` | Trusted-local inter-session messaging, retained inbox/state, and local chatrooms for Pi agents. | `pi install npm:@neuralpartners/pi-yo` |

See each package's README for package-specific usage, license, local smoke tests, and verification details. For unpublished package changes, test from a fresh `origin/main` worktree or install the package by local path; the primary checkout in this repo may be intentionally behind while other worktrees carry release candidates.

## Development

Use Node.js 22+ and npm workspaces.

```bash
npm install
npm run verify
```

Root verification runs workspace checks where packages define them, then checks Markdown/JSON/YAML formatting with Prettier.

## Pi package conventions

See [`docs/pi-packages.md`](https://github.com/Neural-Partners/np-pi/blob/HEAD/docs/pi-packages.md).

Short version:

- publishable packages live under `packages/<name>/`
- package manifests include the `pi-package` keyword for discoverability
- package manifests declare Pi resources under the `pi` key when conventional directories are not enough
- runtime dependencies live in the package that uses them
- Pi-provided APIs such as `@mariozechner/pi-coding-agent` and `typebox` should usually be peer dependencies

## Publishing

See [`docs/publishing.md`](https://github.com/Neural-Partners/np-pi/blob/HEAD/docs/publishing.md).

Tokens must come from AWS SSM Parameter Store or local environment variables. Never commit tokens, `.npmrc`, or generated auth files.

## License

This repo is a container for multiple packages. Package-level `package.json` and `LICENSE` files govern package code. See [`LICENSE`](https://github.com/Neural-Partners/np-pi/tree/HEAD/LICENSE) for the repo-level licensing note.
