Files
openclaw/docs/pi-dev.md
Vincent Koc ca9a04b271 docs: full-page readability pass on 5 worst-offender pages
- automation/standing-orders: sentence-case all H2/H3 headings (Why Standing Orders, Anatomy, Execute-Verify-Report Pattern, Multi-Program Architecture, Best Practices, etc.) and clean up Related link styling
- platforms/raspberry-pi: sentence-case 10 headings (Hardware Requirements, Performance Optimizations, Cost Comparison, etc.)
- install/fly: sentence-case troubleshooting and Private Deployment headings
- pi-dev: drop 'this guide summarizes' filler, sentence-case 4 H2 headings, restore brand-cased Pi
- concepts/model-providers: sentence-case Kimi Coding (other brand-named providers preserved as-is: Google Gemini, Google Vertex, Kilo Gateway, Volcano Engine)
2026-04-26 23:57:10 -07:00

83 lines
2.5 KiB
Markdown

---
summary: "Developer workflow for Pi integration: build, test, and live validation"
title: "Pi development workflow"
read_when:
- Working on Pi integration code or tests
- Running Pi-specific lint, typecheck, and live test flows
---
A sane workflow for working on the Pi integration in OpenClaw.
## Type checking and linting
- Default local gate: `pnpm check`
- Build gate: `pnpm build` when the change can affect build output, packaging, or lazy-loading/module boundaries
- Full landing gate for Pi-heavy changes: `pnpm check && pnpm test`
## Running Pi tests
Run the Pi-focused test set directly with Vitest:
```bash
pnpm test \
"src/agents/pi-*.test.ts" \
"src/agents/pi-embedded-*.test.ts" \
"src/agents/pi-tools*.test.ts" \
"src/agents/pi-settings.test.ts" \
"src/agents/pi-tool-definition-adapter*.test.ts" \
"src/agents/pi-hooks/**/*.test.ts"
```
To include the live provider exercise:
```bash
OPENCLAW_LIVE_TEST=1 pnpm test src/agents/pi-embedded-runner-extraparams.live.test.ts
```
This covers the main Pi unit suites:
- `src/agents/pi-*.test.ts`
- `src/agents/pi-embedded-*.test.ts`
- `src/agents/pi-tools*.test.ts`
- `src/agents/pi-settings.test.ts`
- `src/agents/pi-tool-definition-adapter.test.ts`
- `src/agents/pi-hooks/*.test.ts`
## Manual testing
Recommended flow:
- Run the gateway in dev mode:
- `pnpm gateway:dev`
- Trigger the agent directly:
- `pnpm openclaw agent --message "Hello" --thinking low`
- Use the TUI for interactive debugging:
- `pnpm tui`
For tool call behavior, prompt for a `read` or `exec` action so you can see tool streaming and payload handling.
## Clean slate reset
State lives under the OpenClaw state directory. Default is `~/.openclaw`. If `OPENCLAW_STATE_DIR` is set, use that directory instead.
To reset everything:
- `openclaw.json` for config
- `agents/<agentId>/agent/auth-profiles.json` for model auth profiles (API keys + OAuth)
- `credentials/` for provider/channel state that still lives outside the auth profile store
- `agents/<agentId>/sessions/` for agent session history
- `agents/<agentId>/sessions/sessions.json` for the session index
- `sessions/` if legacy paths exist
- `workspace/` if you want a blank workspace
If you only want to reset sessions, delete `agents/<agentId>/sessions/` for that agent. If you want to keep auth, leave `agents/<agentId>/agent/auth-profiles.json` and any provider state under `credentials/` in place.
## References
- [Testing](/help/testing)
- [Getting Started](/start/getting-started)
## Related
- [Pi integration architecture](/pi)