What problem does it solve?
It enables a fast, reliable edit–reload–test loop for the tracked foxctl Pi extension while you interact with Pi inside a live Maestri shell.
Core Features & Use Cases
- Maestri-driven iterative testing: Reloads extension code in the active Maestri shell and exercises foxctl tools via maestri ask without repeatedly restarting the whole environment.
- Workspace-scoped extension workflow: Keeps a Pi project symlink pointed at the tracked foxctl TypeScript source so changes are reflected immediately in the Pi session.
- Tool-call verification loops: Provides prompts that constrain Pi to specific foxctl tool calls (read-only smoke checks, repoindex checks, and tool-run evidence loading) to validate behavior and tool availability.
- Operational safety notes for tool allowlists and tool choice: Clarifies how /reload affects keybindings and prompts but not the original tool allowlist, and warns when to restart Pi to expand tool access.
- Use Case: When you modify integrations/pi/foxctl.ts, you can typecheck, reload in Maestri, then run a structured prompt that forces Pi to call gather_context and summarize workspace/room/inbox results.
Quick Start
Use maestri list to find the active shell name, then run maestri ask "Shell #6" "/reload" after editing the extension.