Pi Agent Platform
Existing workflow launchers stay unchanged. The runtime lifecycle and live inspector update automatically, while commands expose preflight, diffs, progress, receipts, efficiency, and orchestration policy.
Workflow impact
Users still assign work with a natural-language request or /workflow task. The main change is inside the runtime: task state, trajectories, verifier evidence, recovery, and completion gates are recorded more strictly. The new commands only expose that data when needed.
The interaction flow is not longer. The control flow behind it is safer and fails closed when evidence is missing. A valid task does not require all four new commands.
| Moment | User action stays the same | New automatic runtime behavior | Optional inspection command |
|---|---|---|---|
| Before a task | Send a request or /workflow task <request>. | Loads profile and context, classifies intent and risk, captures runtime truth, and computes a solver recommendation. | /task-preflight [--json] <intent> |
| During work | Continue the task normally. | Records the work plan, phase, changed files, tool and command results, checkpoints, helpers, and recovery events. The inspector updates below the footer. | /piagent-inspector or /piagent-status |
| Verify and review | Use project verification; call /workflow review when a separate review is useful. | Accepts only successful exact verifiers bound to the current working-tree identity. | /piagent-status |
| Completion or handoff | Receive the outcome and remaining risks as before. | Approves a receipt only when trace, work plan, acceptance, changed-file integrity, and the hard gate all pass. | /piagent-status |
| After a task | No new required step. | Keeps sourced telemetry without inferring quality. | /usage efficiency |
Command semantics
| Command | Reads or displays | Does not perform |
|---|---|---|
| /task-preflight | Intent, risk, scope, runtime, route, phase/tool/helper policy, backend, approval, and blockers. | Does not create a task, advance a phase, call a model, or grant implementation authority. |
| /piagent-status | Task Contract, trajectory, checkpoint, verifier, recovery, helper, resume, and terminal receipt from persisted evidence. | Does not edit files, rerun verification, retry work, or turn missing evidence into success. |
| /piagent-inspector | Observed task files in the four-row footer panel, exact baseline delta in the files view, current tool, command failures and blocks, safety warnings, and context budget. No argument opens the menu. | Does not edit files, execute commands, change completion state, or estimate tokens for each built-in tool. |
| /usage efficiency | Sourced context telemetry and task metrics; unavailable facts remain null or unavailable. | Does not grade a person or model and does not decide the completion gate. |
| /piagent-orchestration | Current mode, helper mode, subagent limit, review lenses, Field Guide, and writer policy. | Does not change mode, spawn a helper, or enable parallel writers. |
These five commands are read-only. Behavior changes only when an operator deliberately enables a rollout setting such as phase tools or helper mode; parent routing, automatic workers, and multiple writers do not turn on automatically.
Daily example
/task-preflight --json Fix the failing checkout test
/workflow task Fix the failing checkout test and verify.
/piagent-inspector
/workflow review current diff
/piagent-status
/usage efficiencyOnly /workflow task starts implementation. The inspector opens a menu for files, commands, safety, and context; preflight, inspector, status, and efficiency are optional. Use a separate review when the scope or handoff policy calls for one.
There is no separate /git namespace. Use /workflow commit for a reviewed local commit and /workflow pr to prepare a pull request. Actions such as git push or broad staging with git add -A still require operator confirmation.
Use /piagent-orchestration to inspect the one-helper ceiling, dispatch/skip reason, projected token saving, review lenses, Field Guide, and writer policy. Helpers default to off. Explicit opt-in still permits only one fresh read-only helper when two independent lanes and at least 30% projected net saving are proven; workers and retries stay disabled.
/workflow task Fix the failing checkout test and verify./workflow scout Map the auth flow and risk areas./workflow plan Add multi-tenant billing support./workflow review current diff/workflow commit "feat: add guarded git workflow"/workflow pr "Prepare PR for guarded git workflow"/profile be-readonly-fe
/workflow be-to-fe Implement frontend support for the new user status endpoint./workflow platform-improve Harden command docs and run verification.