Pi Agent Policy 🔧
User-level Pi tool policies and bounded recovery
Project goal
Install once in the Pi user directory to apply declarative tool policies across projects. Policy repairs and eligible terminal recovery share one allowance per original user input; the extension returns real native-tool alternatives and waits for agent_settled before recovery. The repository is currently private, and there is no independent website.
Tech stack
- Pi 0.85.1+ — Public extension events, native tool schemas and user-directory installation
- TypeScript / Node.js 22.19+ — Declarative rules, shared repair budget and versioned installer
- mvdan-sh 0.10.1 — Pinned shell parser; unknown syntax defaults to known commands only
Brand & assets

For agents
Read the integration guide
# Pi Agent Policy — project and identity Page: https://hexly.ai/projects/pi-agent-policy User-level Pi tool policies and bounded recovery Project ID: pi-agent-policy. Catalogue state: active. This is not a product release or health assertion. Repository: https://github.com/nocoo/pi-agent-policy Website: not listed Original project identity: https://h.no.mt/projects/pi-agent-policy/identity/v1.0.0/pi-agent-policy-family-2026-09-14-03-01-c090785742f2.png Original SHA-256: c090785742f29fbaed227af799e5555a49b20449c5f37cdea5fb826fae1d3611 Source: https://github.com/nocoo/pi-agent-policy/blob/ba73409bd7326fa1a425e5faa918a285cde42de5/logo.png Reuse the approved downloadable files. Preserve the original Logo geometry, proportions, colors and bytes. Hexly campaign styling belongs to this archive and Hexly promotional material; the product's own palette and UI remain independent. Family artwork: https://h.no.mt/logos/family/pi-agent-policy/2026-09-14-03/01/transparent.png Family SHA-256: c090785742f29fbaed227af799e5555a49b20449c5f37cdea5fb826fae1d3611 Recorded adoption state: adopted. Do not treat a review candidate as an adopted product identity. The exact generation prompt is a historical source record. Read it for context; adopting the existing assets does not require running it again. Brand kit: v1.0.3. Read its manifest roles and license records before choosing official identity versus Hexly campaign artwork. Verify the selected files against that manifest. The decorative surface was generated with gpt-image-2.5-flare. Reuse its approved PNG/WebP; it is separate from the original Logo. Display one complete canvas without repetition or cropping. Exact light/dark prompts and generation receipts are in the brand archive. ## Sources - [Exact generation prompt](https://h.no.mt/logos/family/pi-agent-policy/2026-09-14-03/01/prompt.txt) - [Brand asset manifest](https://h.no.mt/brands/pi-agent-policy/v1.0.3/manifest.json) - [Exact light surface prompt](https://h.no.mt/brands/pi-agent-policy/v1.0.3/texture-light-prompt.txt) - [Exact dark surface prompt](https://h.no.mt/brands/pi-agent-policy/v1.0.3/texture-dark-prompt.txt) - [Project catalogue JSON](https://hexly.ai/data/projects.json) - [Agent index](https://hexly.ai/llms.txt) - [Published site version and revision](https://hexly.ai/api/live)