Pi CLI Hokage Edition

The intelligence layer that ships your code.

One CLI. Every stack. From a single pi "…" sentence to deterministic validation, autofix, routines, and IDE handoff.

Terminal

$ pi "add Stripe checkout + Supabase webhook, then validate"|

→ detected Next.js (app router), TypeScript, Supabase

→ omni-router → plan: routine → execute → validate

✓ routine.stripe-checkout-flow.v1.md generated

✓ 4 files written, 1 env var added

✓ validate passed (0 violations, 3 rules skipped via cache)

ready → pi watch · pi trace · pi prompt

Three beats

Think. Ship. Govern.

Most AI tools stop at the suggestion. Pi CLI runs the loop — planning, writing, and proving the work.

pi resonate runs a Staff-Engineer session with repo DNA from pi learn, then emits a .pi-plan.md you can execute step by step.

// packages/pi-cli/src/commands/resonate.ts

The omni-router turns pi "…" into real chained subprocesses via cli-orchestrator— multilingual, session-aware, polyglot-ready.

// packages/pi-cli/src/lib/omni-router.ts

Sharingan AST + Rasengan cache + cloud rules. pi validate, pi fix, pre-commit hooks, CI, daemonized pi watch.

// packages/pi-cli/src/commands/validate.ts

Identity · 位

Pi is the governance and context layer under your AI. Keep your Cursor, Claude Code, Codex CLI — Pi makes them sharper.

Pi governs. Your existing AI writes. Different job, different layer.

Coexistence

Cursor, Claude Code, Codex CLI, Cline, Windsurf — Pi injects your team's DNA into all of them.

Safety net

Deterministic rules, watch daemon, team constitution — before CI, before review.