Session basics
Set up a session, select a model, inspect profile, usage, or orchestration state, and decide whether a large task needs a fresh session.
Slash commands package policy and workflow directly, with one inspector menu for diffs, commands, safety, and context instead of many one-off commands.
Set up a session, select a model, inspect profile, usage, or orchestration state, and decide whether a large task needs a fresh session.
Apply a profile directly or use a deterministic selector for the profile and tech stack. Output stays compact and does not require model interpretation.
Packages context loading, task contracts, implementation, verification evidence, and final handoff.
There is no /git namespace. Commit and PR flows use workflow guards; pushes and broad staging such as git add -A require confirmation.
Start a clean workflow when the current context is heavy or belongs to a different task.
Inspect and configure tool servers with the core, popular, or design presets.
Inspect runtime health, model routing, background runs, and cost. Daily work remains solo-first; subagents are reserved for independent scouting, planning, or review lanes.
Product visibility
These commands read deterministic state without asking a model to interpret it. They are optional in the daily workflow.
/task-preflight --json Review current repository state
Inspect intent, risk, scope, runtime, solver route, phases, tool and helper recommendations, backend, approvals, and blockers before starting.
/piagent-status
Read the Task Contract, checkpoints, verifier evidence, recovery, helpers, resume state, and terminal receipt. Approval requires the current-tree hard completion gate to pass.
/piagent-inspector
One menu for summary, files, commands, security, context, and toggle. A four-row panel appears automatically just above the native footer: green is healthy, yellow needs attention, and red marks failures, safety warnings, or context at 80% and above. The command reads local state without calling a model.
/usage efficiency
Inspect context and tool utilization, verification, repair, retries, and helper usage. Runtime values that cannot be measured stay null.
/piagent-orchestration
Inspect the solo-first policy, read-only roles, reviewer or Oracle recommendations, owned budgets, and the one-writer invariant.
The footer panel uses observed task files for fast updates; the files view computes the exact snapshot delta and marks mixed-working-tree when a task touches a file that was already dirty. Pi exposes model usage by turn and session, so per-built-in-tool tokens remain unavailable.