pi-grok-build

Pi package for bringing xAI Grok Build into Pi as a source-inspectable extension, tool, and skill.

pi-grok-build gives Pi a native grok_build tool surface and package docs for operating Grok Build with explicit consent, retained evidence, and bounded output.

Status

pi-grok-build is in the 0.0.x bootstrap line.

Published 0.0.1 reserved the package name and shipped the first source-inspectable doctor. Current source is the 0.0.3 foundational bootstrap candidate: current default install posture, still doctor-only and pre-operational.

Current scope:

• Pi package manifest with pi.extensions and pi.skills
• read-only grok_build tool with action: "doctor"
• pi-grok-build skill
• package-shape tests and npm pack dry-run gate
• public docs for capability, evidence, consent, security, release, and authority boundaries

The doctor is the first-success path. Operational delegation is the next design phase.

Product direction

Grok Build is a terminal coding agent with interactive, headless, and agent-protocol modes. Pi Grok Build will provide a Pi-owned supervision layer around that product:

• one model-facing Pi tool: grok_build
• curated lifecycle actions for launch, status, results, cancellation, and cleanup
• operator-owned launch profiles and executable identity policy
• explicit consent before prompt-carrying provider/subscription use
• bounded previews with artifact paths for full evidence
• source/package/Pi-loader/live-proof separation

Install

From npm after reviewing the published source:

pi install npm:pi-grok-build

From a trusted local checkout:

pi install /absolute/path/to/pi-grok-build

For one-session testing without writing package settings:

pi -e /absolute/path/to/pi-grok-build

First success today

Ask Pi to use the grok_build tool with the only implemented action:

{ "action": "doctor" }

The doctor reports whether grok-build or grok is discoverable on PATH. Treat the result as executable-candidate evidence for that invocation. Operational readiness requires the stronger proof ladder in Evidence ledger.

Control-plane docs

• Architecture
• Vision
• Security
• Privacy
• Terms
• Release
• Control plane
• Capabilities
• Evidence ledger
• Authority matrix
• Configuration
• Consent and provider use
• Artifacts and retention
• Release provenance
• ADR 0001: name and boundary
• ADR 0002: Pi tool contract

Local AGENTS.md, PLAN.md, and HANDOFF.md files are ignored checkout/session notes. Durable package policy belongs in the tracked docs above.

Development checks

npm test
npm run check:pack
git diff --check

npm run check:pack uses npm pack --dry-run --json without leaving a tarball behind.

Security posture

Pi packages run with the user's full local permissions. Review source before installing any Pi package, including this one.

The bootstrap runtime scope is read-only candidate discovery with zero runtime dependencies, shell execution, network calls, credential reads, provider use, or filesystem mutation.