Day-to-day work

No workflow launchers: say what you need in plain language. Inspection commands only observe and never start a model turn.

Edit this page

Workflow impact

No new command is mandatory in the daily flow

Since 1.9.0 work is assigned with a plain-language request and nothing else. /workflow, /task, /fresh and /onboard were retired together with the task contract: a session no longer records a contract, work plan, completion gate or receipt. The guard still checks every tool call.

Short answer

Say what you want, including whether the agent may edit ("read-only, do not edit", "plan first", "implement and run the tests"). The inspection commands below are optional and never start a model turn.

Moment	What the user does	What the runtime does	Optional inspection command
Before the work	Send the request in plain language.	Loads the profile and project context.	/task-preflight [--json] <intent>
During the work	Follow along or answer a confirmation.	Checks each tool call: protected and read-only paths, permission profile, context budget for large files, edits against a stale read, and confirmation for destructive or external actions. The inspector updates below the footer.	/piagent-inspector or /piagent-status
Verify and review	Ask for the project's checks, or for a review of the current diff.	Runs the commands like any other tool call.	/piagent-inspector commands
After the work	No required step.	Keeps sourced telemetry without inferring quality.	/usage efficiency

Command semantics

How far the inspection commands affect a workflow

Command	Reads or displays	Does not perform
/task-preflight	Context and the deterministic shadow route for an intent.	Does not create anything, call a model, or grant implementation authority.
/piagent-status	Profile, guard, runtime and authenticated model state.	Does not edit files, rerun verification or retry work.
/piagent-inspector	Changed files in the four-row footer panel, current tool, command failures and blocks, safety warnings, and context budget. No argument opens the menu.	Does not edit files, execute commands, or estimate tokens for each built-in tool.
/usage efficiency	Sourced context telemetry; unavailable facts remain null or unavailable.	Does not grade a person or model.
/piagent-orchestration	Current mode, helper mode, helper limit, review lenses, Field Guide, and writer policy.	Does not change mode, spawn a helper, or enable parallel writers.

Only explicit opt-in changes behavior.

These five commands are read-only. Behavior changes only when an operator deliberately enables a setting such as helper mode; parent routing, automatic workers, and multiple writers do not turn on automatically.

Daily example

A complete flow can look like this

Inspect → implement → review

/task-preflight --json Fix the failing checkout test
Fix the failing checkout test and run the project tests.
/piagent-inspector
Review the current diff: correctness, missing tests, scope drift. Read-only.
/usage efficiency

Only the plain-language lines start model work. Preflight, inspector and efficiency are optional views.

Git in Pi Agent

There is no /git namespace and no workflow command. Ask for a commit or a pull request in plain language. git push, GitHub writes and broad staging such as git add -A still require operator confirmation.

Parent-direct orchestration

Use /piagent-orchestration to inspect the helper ceiling, dispatch/skip reason, review lenses, Field Guide, and writer policy. Helpers default to off. With explicit opt-in the parent may use up to two fresh read-only helpers; token-saving estimates are telemetry, not a gate. Workers and retries stay disabled.

Implementation

Fix the failing checkout test and run the project tests.

Read-only scout

Map the auth flow and risk areas. Read-only, do not edit.

Plan before coding

Plan multi-tenant billing support. Do not edit code yet.

Review a diff

Review the current diff: correctness, missing tests, scope drift. Read-only.

Local commit

Commit the two docs files with message "docs: update onboarding notes". Do not push.

Pull request

Open a draft pull request for this branch titled "Harden command docs".

Backend spec to frontend

/profile be-readonly-fe
Implement frontend support for the new user status endpoint. Backend is read-only.

Onboard a project

Inspect this project read-only and record its project context.

Many sessions

See every session without opening each space

piagent sessions lists every open session: processing is running, paused is waiting for you, failed hit an error, done has finished. Add --watch to keep it refreshed. With Herdr, run piagent sessions --setup-herdr once to see the state on each space.