β‘ Local-First AI | π Privacy-First | π No Cloud Dependencies | πΎ Self-Contained | π Multi-Host Ready
PIP extends the Pi Agent system with enhanced orchestration, damage control, and production-ready capabilities. Think of PIP as the professional harness that makes the Pi agent system even more powerful and production-ready.
PIP (Pi-Integration Platform) is a modular agent-based system that sits on top of the core Pi Agent infrastructure, providing:
- Enhanced Orchestration β Multi-agent coordination with intelligent task distribution
- Damage Control β 60+ safety rules preventing catastrophic errors
- Theme System β 11 pre-configured themes with hot reload
- Memory Management β Multi-scope memory with export capabilities
- Extension Architecture β Three-layer module system for custom functionality
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β PIP System β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π― PIP Layer (Extension Harness) β
β ββ> Damage Control (Safety & Auditing) β
β ββ> Memory System (Multi-scope memory) β
β ββ> Theme System (11 themes, hot reload) β
β ββ> Extension Loader (Dynamic module loading) β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π€ Pi Agent Core β
β ββ> 30+ Specialized Agents β
β ββ> 13 Team Configurations β
β ββ> 14 Pipeline Chains β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π οΈ Tool Layer (Built-in Tools) β
β ββ> read/write/edit/bash/grep/find/ls β
β ββ> web_search/fetch_content (External) β
β ββ> dispatch_agent (Agent coordination) β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β PIP System β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β ββββββββββββββββββ ββββββββββββββββββ ββββββββββββββββββ β
β β Entry Layer ββββ>β Middle Layer ββββ>β Agent Layer β β
β β β β β β β β
β β justfile β β Extensions β β 30+ Agents β β
β β (Build & Launch)β β & Utils β β + YAML Configs β β
β ββββββββββββββββββ β & Loading β ββββββββββββββββββ β
β β β β β
β βΌ βΌ βΌ β
β ββββββββββββββββββ ββββββββββββββββββ ββββββββββββββββββ β
β β PI_STACK β β pi-loader.ts β β agents.yaml β β
β β Environment β β Dynamic Loader β β Teams.yaml β β
β ββββββββββββββββββ ββββββββββββββββββ ββββββββββββββββββ β
β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β Tools Layer β β
β β ββββββββββββ ββββββββββββ ββββββββββββ ββββββββββββ β β
β β β read β β write β β bash β β web_searchβ β β
β β ββββββββββββ ββββββββββββ ββββββββββββ ββββββββββββ β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
| Component | Purpose | Implementation |
|---|---|---|
| justfile | Build automation & launcher | POSIX-compatible shell script |
| PI_STACK | Environment variable | Set on first run, persists |
| pi-loader.ts | Dynamic extension loader | TypeScript runtime loader |
| Damage Control | Safety auditing | 60+ pattern rules |
| Memory System | Multi-scope memory | JSON/Markdovn export |
| Theme System | UI theming | 51 color tokens |
graph TD
A[PIP System] --> B[Core Dev Agents]
A --> C[Domain Specialists]
A --> D[Platform Experts]
A --> E[Homepage Team]
A --> F[Meta Experts Pi-Pi]
A --> G[Special Agents 40+]
B --> B1[Scout - Reconnaissance]
B --> B2[Planner - Architecture]
B --> B3[Developer - Code]
B --> B4[Reviewer - QC]
B --> B5[Documenter - Docs]
B --> B6[Red-Team - Security]
B --> B7[Session-Manager - Coordination]
C --> C1[FrontendCoder - UI/UX]
C --> C2[Bowser - Browser Automation]
C --> C3[Ext-Builder - Extensions]
C --> C4[Plan-Reviewer - Critique]
D --> D1[Netlify-Troubleshooter]
D --> D2[Pi-Dev-Expert]
E --> E1[Dev-Agent]
E --> E2[Content-Agent]
E --> E3[Marketing-Agent]
E --> E4[Research-Agent]
E --> E5[Design-Agent]
E --> E6[SEO-Agent]
E --> E7[Accessibility-Agent]
E --> E8[Image-Agent]
F --> F1[Pi-Orchestrator]
F --> F2[Skill-Expert]
F --> F3[Agent-Expert]
F --> F4[Ext-Expert]
F --> F5[TUI-Expert]
F --> F6[CLI-Expert]
F --> F7[Config-Expert]
G --> G1[Research & Analysis 8]
G --> G2[Web Tools 8]
G --> G3[Content Creation 12]
G --> G4[Creative AI 6]
G --> G5[Finance 5]
G --> G6[Developer Tools 4]
| Agent | Specialization | Tools | Primary Use Case |
|---|---|---|---|
| scout | Fast Reconnaissance | read, grep, find, ls | Codebase exploration, discovery |
| planner | Architecture & Planning | read, grep, find, ls, write | Architecture design, resource allocation |
| developer | Code Implementation | read, write, edit, bash, grep, find, ls | Code generation, feature implementation |
| reviewer | Code Review & QC | read, bash, grep, find, ls, write | Quality checks, security audits, validation |
| documenter | Documentation | read, write, edit, grep, find, ls | README generation, doc updates, changelog |
| red-team | Security Testing | read, bash, grep, find, ls | Adversarial testing, vulnerability scanning |
| session-manager | Session Coordination | read, write, grep, find, ls | Chat sessions, metadata, history coordination |
| Agent | Specialization | Tools | Primary Use Case |
|---|---|---|---|
| frontendcoder | UI/UX Implementation | read, write, edit, bash, grep, find, ls | Components, styling, responsive design |
| bowser | Browser Automation | read, write, ls | Playwright CLI, headless browser control |
| ext-builder | Extensions Development | read, write, edit, bash, grep, find, ls | Pi extensions, tools, events, rendering |
| plan-reviewer | Plan Critique | read, grep, find, ls | Challenges, validates implementation plans |
| Agent | Specialization | Tools | Primary Use Case |
|---|---|---|---|
| netlify-troubleshooter | CI/CD & Netlify | read, write, edit, bash, grep, find, ls | Build pipelines, dependency resolution |
| pi-dev-expert | Pi Ecosystem | read, write, edit, bash, grep, find, ls | Core primitives, extensions, skills, terminal |
graph LR
A[Full Dev Team] --> A1[Scout - Fast Recon]
A --> A2[Planner - Architecture]
A --> A3[Developer - Code]
A --> A4[Reviewer - QC]
A --> A5[Documenter - Docs]
B[Planning Review Team] --> B1[Scout]
B --> B2[Planner]
B --> B3[Plan-Reviewer]
B --> B4[Reviewer]
C[Security Research Team] --> C1[Scout]
C --> C2[Developer]
C --> C3[Netlify-Troubleshooter]
C --> C4[Ext-Builder]
C --> C5[Pi-Dev-Expert]
D[Browser Automation Team] --> D1[Scout]
D --> D2[Developer]
D --> D3[Bowser]
D --> D4[Documenter]
E[Session Team] --> E1[Session-Manager]
E --> E2[Developer]
E --> E3[Documenter]
F[Build Deploy Team] --> F1[Developer]
F --> F2[Netlify-Troubleshooter]
F --> F3[Planner]
F --> F4[Reviewer]
G[Architecture Team] --> G1[Planner]
G --> G2[Plan-Reviewer]
G --> G3[Reviewer]
G --> G4[Ext-Builder]
G --> G5[Pi-Dev-Expert]
H[Extensions Team] --> H1[Ext-Builder]
H --> H2[Developer]
H --> H3[Documenter]
H --> H4[Pi-Dev-Expert]
I[Fast Exec Team] --> I1[Planner]
I --> I2[Developer]
I --> I3[Scout]
J[Maintenance Team] --> J1[Documenter]
J --> J2[Session-Manager]
J --> J3[Developer]
J --> J4[Reviewer]
# Example team configuration
- team: full-dev-team
members:
- scout
- planner
- developer
- reviewer
- documenter
default: true
purpose: Complete development lifecycle implementation
- team: security-research-team
members:
- scout
- developer
- netlify-troubleshooter
- ext-builder
- pi-dev-expert
default: false
purpose: Deep exploration and security analysis
- team: browser-automation-team
members:
- bowlser
- developer
- documenter
default: false
purpose: Web scraping and browser automation# Use agent-team extension to switch teams
pi -e agent-team
just run-pi "agent-team, full-dev-team"
# View available teams
pi --teamsflowchart TD
START[User Request] --> PIPELINE
subgraph Pipelines
direction TB
P1[SCOUT β SCOUT β SCOUT]
P2[PLANNER β DEVELOPER β REVIEWER]
P3[PLANNER β DEVELOPER]
P4[SCOUT β PLANNER β DEVELOPER β REVIEWER]
P5[SCOUD β EXT-BUILDER β PI-DEV-EXPERT β DEVELOPER β REVIEWER]
P6[SCOUD β NETLIFY-TROUBLESHOOTER β DEVELOPER β DOCUMENTER]
P7[PI-DEV-EXPERT β EXT-BUILDER β DEVELOPER β DOCUMENTER β REVIEWER]
P8[SESSION-MANAGER β DEVELOPER β DOCUMENTER]
P9[PLANNER β PLAN-REVIEWER β PLANNER]
P10[ARCHITECTURE REVIEW: PLANNER β PLAN-REVIEWER β PI-DEV-EXPERT β REVIEWER]
end
PIPELINE --> P1
PIPELINE --> P2
PIPELINE --> P3
PIPELINE --> P4
PIPELINE --> P5
PIPELINE --> P6
PIPELINE --> P7
PIPELINE --> P8
PIPELINE --> P9
PIPELINE --> P10
P1 --> END[Completion]
P2 --> END
P3 --> END
P4 --> END
P5 --> END
P6 --> END
P7 --> END
P8 --> END
P9 --> END
P10 --> END
| Chain | Steps | Purpose |
|---|---|---|
| plan-build-review | planner β developer β reviewer | Standard development cycle with review |
| plan-build | planner β developer | Fast two-step without review |
| scout-flow | scout β scout β scout | Triple-scout deep reconnaissance |
| plan-review-plan | planner β plan-reviewer β planner | Iterative planning with critique |
| full-review | scout β planner β developer β reviewer | Complete end-to-end pipeline |
| browser-flow | scout β developer β bowser β documenter | Browser automation workflow |
| session-workflow | session-manager β developer β documenter | Session management operations |
| security-research-flow | scout β ext-builder β pi-dev-expert β developer β reviewer | Security research |
| deploy-workflow | scout β netlify-troubleshooter β developer β documenter | CI/CD deployment |
| extensions-workflow | pi-dev-expert β ext-builder β developer β documenter β reviewer | Extension development |
| fast-exec-team | planner β developer | Quick cycles |
| docs-workflow | scout β documenter β developer | Documentation workflow |
| architecture-review | planner β plan-reviewer β pi-dev-expert β reviewer | Architecture review |
| session-analysis-flow | session-manager | Session deep-dive analysis |
βββββββββββββββββββββββββββββββββββββββββββ
β Damage Control System β
β β
β β
60+ Dangerous Command Patterns β
β β
Read-Only/No-Delete Path Protection β
β β
Per-Path Override Mechanisms β
β β
Interactive Settings Modal β
β β
Real-time Safety Auditing β
βββββββββββββββββββββββββββββββββββββββββββ
# Dangerous command patterns blocked
β rm -rf /
β curl | bash
β wget | bash
β dd if=/dev/zero of=/dev/sdX
# Protected directories
π ~/.pi/user_data (read-only)
π ~/.pi/project (read-only)
π /etc/* (no writes)
# Customizable via settings
$ {EDITOR} {settings} --damage-controlMulti-scope memory for context retention:
flowchart LR
A[User Scope] --> B[Memory System]
C[Project Scope] --> B
D[Local Scope] --> B
B --> E[Export Formats]
E --> E1[JSON]
E --> E2[Text]
E --> E3[Markdown]
E --> E4[Stats]
# Memory operations
pi memory --list
pi memory --export json
pi memory --export markdown
pi memory --statsflowchart LR
A[Theme Picker Widget] --> B[Theme System]
B --> C[11 Pre-configured Themes]
B --> D[51 Color Tokens]
B --> E[Hot Reload Capability]
B --> F[Vars System]
| Theme | Description | Status |
|---|---|---|
| catppuccin | Modern pastel colors | β Dark/Light |
| nord | Arctic blue palette | β Dark |
| dracula | Classic dev theme | β Dark |
| tokyonight | Tokyo-inspired | β Dark |
| monokai | Classic IDE colors | β Dark |
| gruvbox | Warm earth tones | β Dark |
| papermoon | Soft pink palette | β Dark |
| solarized | Gray-green balance | β Light/Dark |
| one-dark | VS Code default | β Dark |
| material | Material design | β Dark/Light |
| gruvbox-material | Gruvbox variant | β Dark |
git clone https://github.com/zerwiz/pip.git
cd pip
just install
# Or direct run
just run-pi "agent-team, damage-control"# Standard usage
just run-pi "agent-team"
# With specific extensions
just run-pi "agent-team, damage-control, theme-cycler"
# Multi-host (optional)
just run-pi "agent-team,damage-control" --hosts local,remote1,remote2# Common commands
pi <request> # Send request to agent team
pi memory --list # List memory scopes
pi memory --export # Export memory files
pi --teams # View available teams
pi --pipelines # View available pipelines
pi --settings # View current settings
pi --themes # List available themes
pi --help # Full help menu# Switch teams
pi -e agent-team
just run-pi "agent-team, new-team"
# List all teams
pi --teams --list- Start with Scout β Always run
scoutfirst for reconnaissance - Use Teams β Let teams handle task distribution
- Enable Damage Control β Default: enabled, prevents errors
- Export Memory β Regular memory exports for backup
- Use Pipelines β Leverage built-in pipeline chains
- Check Settings β Review
$settingsbefore task
- Don't Skip Scout β Always recon before execution
- Avoid Direct File Deletion β Use edit/write, not bash rm
- Don't Overload β One team at a time per session
- Review Code β Always review after developer step
- Backup Memory β Export memory regularly
# Enable parallel execution
just run-pi "agent-team" --parallel
# Use fast-team for simple tasks
just run-pi "fast-exec-team"
# Multi-host for heavy workloads
just run-pi "agent-team" --hosts local,host1,host2# Homepage team creates complete website
just run-pi "homepage-team" \
--request "Create a landing page for my product"
# Behind the scenes:
# - design-agent creates UI
# - content-agent writes copy
# - dev-agent implements code
# - image-agent selects visuals# Security research workflow
just run-pi "security-research-team" \
--request "Analyze this codebase for vulnerabilities"
# Flow: scout β ext-builder β pi-dev-expert β developer β reviewer# Build a custom extension
just run-pi "extensions-team" \
--request "Create a memory export extension"
# Flow: pi-dev-expert β ext-builder β developer β documenter β reviewer# Web scraping workflow
just run-pi "browser-automation-team" \
--request "Extract product data from this website"
# Flow: scout β developer β bowser β documenterpip/
βββ justfile # Entry point & launcher
βββ .pi/
β βββ agents/ # Agent definitions
β βββ extensions/ # Pi extensions
β βββ py/ # Python components
βββ .pi/build_logs/ # Build artifacts
βββ .pi/reference/ # File backups
βββ README.md # This file
| File | Purpose |
|---|---|
| justfile | Entry point, sets PI_STACK, launches extensions |
| .pi/agents/ | 30+ agent definitions |
| .pi/extensions/ | 24+ extension modules |
| .pi/build_logs/ | Build artifacts and logs |
| .pi/reference/ | Full-file backups |
- Pi Agent System Documentation
- Agent YAML Configuration Guide
- Extensions Documentation
- Migration Guide
- Justfile Startup Mechanism
# 1. Fork the repository
git clone https://github.com/zerwiz/pip.git
# 2. Create a new branch
git checkout -b feature/my-feature
# 3. Make changes
pi [your-request]
# 4. Test locally
just install
just run-pi "agent-team"
# 5. Submit a pull request
git push origin feature/my-featureMIT License β See LICENSE file for details
System Compatibility: Branch 12 is compatible with Pi v0.72.1+.
Minimum Requirements: Pi v0.72.1 or later.
Recommended: Pi v0.72.2+ for enhanced performance.
Version: PIP 0.72.1+
- Issues: Create on GitHub
- Features: Submit via issue tracker
- FAQ: Check README frequently
Built with β€οΈ by the PIP team. Thanks to Pi agent system for the amazing foundation.
π Ready to get started?
just run-pi "agent-team, damage-control"System Version: 0.72.1+
Last Updated: 2026
License: MIT
Developer: @zerwiz