01 / The arsenal
A layer, not a monolith.
Take what you need.
Start with the problem you want to solve. Each module has a job, a clear license, and its own installation guide. Most extensions run inside Pi; zrag is a standalone Python tool.
Governance
Decide what runs and what changes.
pi-change-reason
ProThe agent has to justify every edit or write before running it.
pi-change-review
ProFile edits wait for approval before they're applied.
pi-edit-guard
ProPost-edit safety net. Suspends on rejection. Forces a re-review before the agent tries again.
pi-gatekeeper
FreeAST-based bash interception. Blocks destructive commands before they run.
pi-sandlock
ProTiered process isolation backed by the Sandlock engine (seccomp + Landlock).
Observability
Keep a record you can inspect.
pi-console-link
TeamConnects your local Pi instance to the self-hosted Bastille-C3 Console. Sends governance events for centralized audit, shared team policy, and team admin.
pi-tracer
ProFull capture of HTTP requests and responses for LLM model calls. A local record you can inspect.
Data Sovereignty
Put your knowledge on your own ground.
Efficiency
Carry context forward without repeating work.
Orchestration
Coordinate agents without losing the thread.
Configurations
Give the agent a method and a clear scope.
No matching modules.
Try a broader search, or clear the filters.
When one machine becomes a team
A Console on your ground.
Bring governance events into a self-hosted Node + PostgreSQL Console. Shared policy, audit history, and a team dashboard belong on your infrastructure.
See the team setup →Know what you're installing
Clear licenses. No hidden tenancy.
Free modules and skills use Apache-2.0. Paid components use FSL-1.1-ALv2. Paid activation checks your entitlement with Polar; your agent workload stays on your machines or with providers you choose.
The public source repository is not available at the configured URL yet. Ask for the source rather than following a broken link.
Request source access ↗