Reproducible Pi.dev agent configuration: settings, MCP servers, custom skills, subagents, and bootstrap install script.

⚡ ← Back to LocalPibox — project overview, architecture, and the full stack.

config/
├── AGENTS.md                        # Global agent instructions
├── README.md / CONTRIBUTING.md / VALIDATION.md
├── settings.json.template           # Pi settings template (rendered at first boot → settings.json, gitignored)
├── mcp.json.template                # MCP server template (rendered at first boot → mcp.json, gitignored)
├── lpb-memory-config.json.template  # Memory extension template (→ lpb-memory-config.json, gitignored)
├── pi-defaults.json                 # Local-first defaults (subagent model, extension overrides)
├── .env.example                     # Environment variables template (EXA_API_KEY, …)
├── install.sh                       # One-command bootstrap script
├── skills/                          # Custom skills (installed to ~/.pi/agent/skills/)
│   ├── agent-browser-mcp-integration/
│   ├── browser-validation/
│   └── mcp-vision-analysis/
└── agents/                          # Custom subagents (installed to ~/.pi/agent/agents/)
    ├── README.md
    ├── _template.md
    ├── browser-automation.md
    ├── exa-search.md
    ├── researcher.md
    └── vision-analysis.md

Rendered runtime files (settings.json, mcp.json, lpb-memory-config.json) are gitignored and regenerated by lpb-config render — never edit them by hand.

# Install with defaults (to ~/.pi/agent/)
bash install.sh

# Install to custom location
bash install.sh /path/to/custom/pi/agent

Shipped in the devstack image at /opt/pi-support/lpb-config (symlinked to lpb-config in PATH). Manage the config repo from inside any container.

lpb-config status               # Show config repo state
lpb-config update               # Fetch + fast-forward config repo
lpb-config reset [--force]      # Re-clone (destructive)
lpb-config merge                # Interactive merge
lpb-config render [--force]     # Regenerate runtime config from templates
lpb-config align                # Update extension pins to latest tags
lpb-config sync-pins            # Sync extension pins to the pipeline's stack version
lpb-config setup                # First-run setup wizard (provider, model, memory)
lpb-config check                # Validate the installation (read-only checklist)

lpb-config memory show          # Show lpb-memory config
lpb-config memory setup         # Interactive config wizard
lpb-config memory setup --non-interactive  # Generate from template

sync-pins is pipeline-sensitive: lpb-config --tag main sync-pins syncs pins to the stable stack version. Workspace/validate operations live in lpb-devstack (dev-time tool):

lpb-devstack validate                          # Full stack alignment check
lpb-devstack workspace status | sync           # Workspace repo management

This repo ships templates (settings.json.template, lpb-memory-config.json.template, mcp.json.template); the rendered runtime files are gitignored. start.sh generates them on first boot only, so lpb-config also renders: reset re-renders (force), update/merge re-render (non-forcing), and lpb-config render [--force] regenerates on demand. Non-forcing render never overwrites — it creates missing files and warns on stale version pins; --force merges (user keys and user-added packages preserved; template pins win in settings.json, local keys win in the memory config).

• Provider: lemonade (external LLM server)
• Model / endpoint: runtime config — lpb-config show (change with lpb-config set model|base-url|api-key or the lpb setup wizard)
• Thinking: medium (default); adjustable via /settings in Pi TUI or lpb-config set thinking
• Packages: extensions installed at runtime (from settings.json#packages, version-pinned via the __LPB_VERSION__ placeholder — synced with lpb-config sync-pins):
  • git:github.com/lpb-stack/lemonade-pi-plugin@<stack-version>
  • git:github.com/lpb-stack/lpb-memory@<stack-version>
  • npm:pi-mcp-adapter
  • npm:@tintinweb/pi-subagents (upstream npm, no version pin — pi updates it via pi update --extensions)
  • npm:pi-powerline-footer
  • @upstash/context7-mcp

Configuration for the lpb-memory extension. Generated at first boot from lpb-memory-config.json.template — the template is tracked, the config is not.

# Review current config
lpb-config memory show

# Interactive setup wizard
lpb-config memory setup

# Non-interactive (from template)
lpb-config memory setup --non-interactive

Default settings (from template):

• reviewTransport: subprocess (offload to NPU)
• memoryMode: legacy-inject (visible to AI every turn)
• memoryCharLimit: 3000 (context optimized)
• failureInjectionMaxEntries: 3
• No llmModelOverride — uses main model (user configures after /login)

MCP server configuration — runtime file, rendered from mcp.json.template at first boot (gitignored; the setup wizard's MCP step, step 6, offers an enable/disable toggle per server — "enabled": false turns a server off):

• exa — Web search and content fetch (requires EXA_API_KEY)
• agent-browser — Browser automation
• chrome-devtools — Diagnostics (disabled by default)
• context7-mcp — Up-to-date library docs (optional CONTEXT7_API_KEY)

Copy .env.example to .env in your project directory and fill in:

• EXA_API_KEY — Exa MCP server API key
• CONNECTION_TOKEN — OpenVSCode auth token
• EDITOR_HOST — Editor host for VSCodium
• ED_PORT — Editor port

This repo is the configuration preset for the LocalPibox stack. On first container boot, these files are seeded into ~/.pi/agent/.

Pi itself is not a stack repo — the image installs mainstream pi from the npm registry at LPB_PI_VERSION (the former fork is retired).

See the devstack repo for container setup and lpb-stack.github.io/devstack/ for the project site.

See the stack CONTRIBUTING guide.