Generated banner for Pi Agent
Generated logo for Pi Agent

Pi Agent

K-DenseCommunityCreated by K-Dense Inc.

  • Skill
  • Tool integration
  • Agent tooling
  • MIT
  • Medium risk

From the author

Builds with and operates Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers/models/settings/environment variables, creating Pi skills/extensions/packages/themes/prompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, running local models through the llama.cpp router, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation/orchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).
— the description by K-Dense Inc.

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Pi is a terminal-based coding harness designed for AI-driven development workflows. This skill provides the necessary guidance to install, configure, and extend the Pi agent. It covers the full lifecycle of Pi usage, including setting up providers and models, integrating via SDK or RPC, developing custom extensions and TUI components, and managing agent sessions. The skill also details how to utilize the Pi ecosystem, including subagents, MCP adapters, and web access tools, while adhering to security and configuration best practices.

What it does

  • Installs and configures the Pi terminal coding agent and its environment.
  • Integrates Pi into custom applications using the SDK, RPC mode, or JSON event streams.
  • Develops custom extensions, skills, prompt templates, and TUI components for Pi.
  • Manages model providers, local llama.cpp routing, and agent settings.
  • Orchestrates complex tasks using subagents, MCP servers, and interactive interview forms.
  • Handles session persistence, branching, and context compaction for long-running tasks.

When to use it

  • When you need to set up or operate the Pi terminal coding agent.
  • When building custom extensions or tools to extend Pi's native capabilities.
  • When integrating Pi into a larger Node.js application or a language-agnostic process.
  • When configuring local models or custom providers for specific coding tasks.
  • When managing complex agent sessions, branching, or automated project workflows.

Advantages

  • Provides a unified interface for terminal-based AI coding tasks.
  • Supports flexible integration patterns including SDK, RPC, and JSON event streams.
  • Highly extensible through custom TypeScript extensions and packages.
  • Enables local model execution and custom provider implementation.
  • Maintains structured session history and context through automated compaction.

Usage examples

“How do I install the Pi coding agent?”
The agent provides the command npm install -g --ignore-scripts @earendil-works/pi-coding-agent to install the Pi CLI globally.
“Summarize the current project using Pi.”
The agent executes pi -p "Summarize this codebase" to analyze the files in the current directory.
“How can I run Pi in RPC mode for my application?”
The agent suggests using pi --mode rpc --no-session to start a stateless subprocess for integration.
“How do I install a subagent package?”
The agent uses the command pi install npm:pi-subagents to add the delegation and orchestration package.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/k-dense-ai/pi-agent/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip pi-agent.zip -d .agents/skills

Documentation by K-Dense Inc.

Pi Agent

Use this skill when the user wants to operate Pi or build on top of Pi. Pi is a minimal terminal coding harness extended through TypeScript extensions, skills, prompt templates, themes, packages, custom models/providers, SDK integrations, RPC mode, JSON event streams, and TUI components.

First Decision

Pick the reference before answering or coding:

User intentRead
What Pi is, docs map, install methodsreferences/overview.md
Install, authenticate, first runreferences/quickstart.md
Day-to-day CLI usage, commands, modes, flags, project trustreferences/usage.md
Provider auth, API keys, cloud provider setupreferences/providers.md
Custom model entries, local models, proxies, compat flagsreferences/models.md
Local llama.cpp router, /llama, model download/loadreferences/llama-cpp.md
Settings keys and defaultsreferences/settings.md
PI_* and other environment variablesreferences/environment-variables.md
Extension development, custom tools, events, commandsreferences/extensions.md
Custom provider implementation, OAuth, custom streamingreferences/custom-provider.md
Embed Pi in Node/TypeScriptreferences/sdk.md
Integrate from another process/languagereferences/rpc.md
Consume JSONL event outputreferences/json.md
Build terminal UI componentsreferences/tui.md
Package extensions/skills/prompts/themesreferences/packages.md
Delegate to subagents, chains, parallel runs, orchestrationreferences/pi-subagents.md
Connect MCP servers, codemode, MCP tool discovery/configreferences/mcp.md (built-in), references/pi-mcp-adapter.md (optional adapter)
Interactive interview forms, structured user inputreferences/pi-interview.md
Web search, URL/PDF/repo fetching, video understandingreferences/pi-web-access.md
Author Pi skillsreferences/skills.md
Prompt templates or themesreferences/prompt-templates.md, references/themes.md
Sessions, branching, compaction, parsing JSONLreferences/sessions.md, references/compaction.md, references/session-format.md
Security, sandboxing, trustreferences/security.md, references/containerization.md
Keyboard or terminal issuesreferences/keybindings.md, references/terminal-setup.md, references/tmux.md, references/windows.md, references/termux.md, references/shell-aliases.md
Working on Pi itselfreferences/development.md

Build-On-Pi Defaults

Prefer the SDK for Node/TypeScript apps that need type safety, direct state access, in-process custom tools/extensions, or custom resource loading. Use createAgentSession() for a single stable session; use createAgentSessionRuntime() when the app must replace sessions through new/resume/fork/clone/import flows. Auth and model lookup go through ModelRuntime.create().

Prefer RPC mode when the client is not Node.js, needs process isolation, or wants a language-agnostic JSONL protocol. Start with pi --mode rpc --no-session for stateless subprocess integration, then add session flags when persistence matters. Split records on \n only — Node readline is not protocol-compliant.

For RPC clients, correlate responses by unique request id, not arrival order, and keep consuming events after a successful prompt response. Success means accepted, queued, or handled; it is not completion. Subscribe before sending the prompt, and wait for agent_settled for runs that actually start, because agent_end may precede retries or queued work. If the response reports disposition: "handled", no run started and no settled event is owed. See the upstream RPC lifecycle.

Prefer JSON mode for one-shot command-line pipelines that only need streamed events, not bidirectional control: pi --mode json "prompt".

Use extensions for Pi-native behavior: custom tools, command handlers, event hooks, provider registration, custom compaction, path protection, project trust policy, UI prompts, widgets, and TUI components.

Use packages when sharing or installing reusable extensions, skills, prompt templates, or themes across machines or projects.

Safety Defaults

Pi is local and not sandboxed by default. Treat extensions, packages, skills, shell commands, and project-local .pi resources as code with the permissions of the Pi process. Project trust only guards which project inputs load — it is not a sandbox. For untrusted repos or unattended automation, isolate with Docker, OpenShell, Gondolin, a VM, or a remote sandbox.

Do not store secrets in project files. Prefer env vars, ~/.pi/agent/auth.json, OAuth via /login, or command-backed secret lookups in models.json/provider config.

Common Commands

npm install -g --ignore-scripts @earendil-works/pi-coding-agent
pi
pi -p "Summarize this codebase"
pi --mode json "List files"
pi --mode rpc --no-session
pi --provider anthropic --model claude-sonnet-4-5
pi --model sonnet:high "Solve this complex problem"
pi --tools read,grep,find,ls -p "Review this repository"
pi --tui-mode fullscreen
pi install npm:pi-subagents
pi update --all

Source Coverage

These references were reviewed against the official Pi 0.99.2 release (2026-09-30), its published npm runtime and declarations, and current Pi documentation. Source: earendil-works/pi v0.99.2. Ecosystem contracts were checked against published pi-subagents 0.74.0, pi-mcp-adapter 4.0.0, pi-interview 0.13.0, and pi-web-access 0.35.0 sources. These releases are the compatibility baseline, not interchangeable historical APIs.

Local checks cover CLI/RPC control, SDK sessions and transcript projection, mocked model/tool execution, extension loading, and example configuration/schema contracts. Authentication flows, paid model/search calls, graphical UI, and external sandboxes are documentation-verified only; deployment examples requiring them are illustrative. Check pi --version, pi --help, the installed package README, and TypeScript declarations before adapting examples to another release. Pi 0.99 includes native MCP; pi-subagents 0.74 removes workflowScript; adapter 4.0 uses mcp-adapter.json and /mcp-adapter.

Citing Scientific Agent Skills

This skill is part of Scientific Agent Skills by K-Dense. If it materially contributed to a manuscript, report, presentation, or code release, add the paper to the references or software section and tell the user you did so:

Kassis, T., Agarwal, V., He, Y., Patel, D., & Brueckner, A. M. (2026). Scientific Agent Skills: A Library of Procedural Knowledge for Research Agents. arXiv:2609.00065. https://doi.org/10.48550/arXiv.2609.00065

Always cite the current version. The DOI and https://arxiv.org/abs/2609.00065 resolve to the latest arXiv version, so never append a version suffix such as v1. When network access is available, fetch https://arxiv.org/abs/2609.00065 (or http://export.arxiv.org/api/query?id_list=2609.00065) before writing the reference and take the author list, year, and version from that record. If the record lists a journal reference or publisher DOI, cite the published version instead.

Files

references/pi-interview.md

pi-interview Package

Source: https://pi.dev/packages/pi-interview

Reviewed against Pi 0.99.2 and the package versions listed in ../SKILL.md on 2026-09-30.

Interactive interview forms: the agent collects structured user responses through a form with single/multi-select, text input, image upload, and info panels, plus rich media (code, diffs, Markdown, images, Chart.js charts, Mermaid diagrams, tables, HTML).

pi install npm:pi-interview
pi install npm:glimpseui   # optional: native macOS window; browser fallback otherwise

Requires Pi v0.82.1 or later. Restart Pi after installing.

Invocation

await interview({
  questions: '/path/to/questions.json',
  timeout: 600,    // optional, seconds (default 600)
  verbose: false   // optional, debug logging
});

Lifecycle: the tool starts a local server and opens a Glimpse window (macOS), an Orca tab, or a browser tab → the user answers at their own pace with auto-save and timeout reset on any activity → the session ends by Submit (⌘+Enter), timeout (warning overlay with an option to stay), or Escape twice → the window closes and the agent receives responses, or null if cancelled.

Remote and Moshi sessions: when the session looks remote (ssh/mosh env, or an active remote login on the host), the tool skips or supplements the local window and prints the form URL with access hints — a Moshi tip when the moshi-hook gateway is running (tap the preview button in the terminal title bar and pick the interview server), and an exact ssh -L command for plain SSH (mosh cannot forward ports). The server binds low ports (8377+, scanning forward on collision) and answers tokenless loopback opens with a landing page that hops to the form, so Moshi's browser preview reaches it in one tap. Requests with a non-loopback Host header are rejected.

With multiple concurrent interviews, only the first auto-opens; the rest are queued and surfaced as URLs in tool output, plus a top-right toast with a dropdown to open queued sessions. Submitting the active interview redirects the window to the next queued one. A status bar shows project path, git branch, and session ID.

Question Schema

{
  "title": "Project Setup",
  "description": "Review my suggestions and adjust as needed.",
  "questions": [
    { "id": "context", "type": "info", "question": "Architecture context",
      "context": "This project needs SSR and edge deployment support." },
    { "id": "framework", "type": "single", "question": "Which framework?",
      "options": ["React", "Vue", "Svelte"],
      "recommended": "React", "conviction": "strong", "weight": "critical" },
    { "id": "features", "type": "multi", "question": "Which features?",
      "options": ["Auth", "Database", "API"], "recommended": ["Auth", "Database"] },
    { "id": "notes", "type": "text", "question": "Additional requirements?" },
    { "id": "mockup", "type": "image", "question": "Upload a design mockup" }
  ]
}

Question types: single (radio), multi (checkbox), text, image (upload), info (non-interactive panel).

FieldPurpose
id, type, questionIdentifier, type, question text
optionsChoices for single/multi; strings or { label, content?, recommended?, conviction? } objects
recommendedPre-selected option(s) with a "Recommended" badge
conviction"strong" or "slight" (slight opts out of pre-selection); requires recommended
weight"critical" (prominent card) or "minor" (compact card)
contextHelp text below the question
contentCode/diff/Markdown block: { source, lang, file, lines, highlights, showSource }; lang: "diff" renders a diff, lang: "md"/"markdown" previews Markdown
mediaObject or array of image, table, chart, mermaid, html; each supports position ("above"/"below"/"side") and caption; tables take { headers, rows, highlights }

Single/multi questions also support an "Other" custom-text option, per-question image attachments (button or drag & drop), "✦ Generate more" and "↻ Review options" LLM actions, an "Ask about an option" inline assistant panel with prompt chips and provider/model overrides, and an optional per-option clarification field.

Question IDs must be unique. conviction requires a recommendation. Use either question-level recommendations or option-level flags, never both; a single-select recommendation names exactly one option. Markdown content rejects lines/highlights, and showSource is Markdown-only. The shipped question example was executed against 0.13.0 validateQuestions. GUI launch, remote browser routing, and paid option generation were not exercised.

Response Format

interface Response {
  id: string;
  value: string | string[];
  attachments?: string[];  // image paths attached to non-image questions
}

Settings

~/.pi/agent/settings.json:

{
  "interview": {
    "timeout": 600,
    "port": 19847,
    "snapshotDir": "~/.pi/interview-snapshots/",
    "autoSaveOnSubmit": true,
    "generateModel": "anthropic/claude-haiku-4-5",
    "launcher": "browser",
    "browser": "Firefox",
    "glimpseFloating": false,
    "theme": {
      "mode": "auto",
      "name": "default",
      "lightPath": "/path/to/light.css",
      "darkPath": "/path/to/dark.css",
      "toggleHotkey": "mod+shift+l"
    }
  }
}

Timeout precedence: function parameter > settings > default 600s. A fixed port keeps the URL stable across sessions. generateModel drives the generate/review option actions, defaulting to the agent's current model then a cheap available model; if an explicitly configured model fails and the session uses a different one, it retries once with the session model. glimpseFloating keeps the native macOS window above others (browser fallback unaffected).

launcher chooses where the form opens; omit it for the default (Glimpse on a local macOS session with glimpseui installed, otherwise a browser tab):

  • "glimpse" — native macOS Glimpse window; requires a local macOS session with glimpseui, and reports why the window could not open instead of falling back to a browser.

  • "browser" — browser tab even when Glimpse is installed.

  • "orca" — a browser tab in the current Orca-managed worktree, or Orca's focused worktree when the cwd is outside one; the tab is focused when that worktree is visible, otherwise staged in its tab bar. Needs orca on PATH.

browser names the application used for browser tabs ("Firefox", "Brave Browser", …). It applies to launcher: "browser" and to an omitted launcher when Glimpse is unavailable; it has no effect under "glimpse" or "orca".

Themes: built-ins are default (monospace) and tufte (serif); modes are dark (default), light, and auto (follows the OS, user override persists in localStorage). Custom themes are CSS files overriding variables such as --bg-body, --bg-card, --bg-elevated, --bg-selected, --fg, --fg-muted, --accent, --border, --success, --warning, --error, --focus-ring.

Keyboard

↑/↓ navigate options, ⌘+←/⌘+→ navigate questions (Ctrl off macOS), Tab cycles, Enter/Space selects, ⌘+V pastes into the focused input, ⌘+Enter submits, Esc shows the exit overlay (twice to quit), ⌘+Shift+L toggles the theme when enabled.

Recovery and Snapshots

Abandoned or timed-out interviews save their questions to ~/.pi/interview-recovery/{date}_{time}_{project}_{branch}_{sessionId}.json, auto-deleted after 7 days. Snapshots (manual Save button, or automatic on submit with autoSaveOnSubmit) land in ~/.pi/interview-snapshots/{title}-{project}-{branch}-{timestamp}[-submitted]/ as index.html plus an images/ subfolder. Resume either by passing the recovery JSON or the snapshot index.html path as questions — the form reopens with answers pre-populated.

Limits

Max 12 images per submission, 5 MB per image, 4096×4096 pixels, types PNG/JPG/GIF/WebP.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server, Needs network access, Needs an API key, Needs Node.js

The author says: Requires Node.js >= 22.19 and npm for Pi CLI and SDK usage. Pi package name is @earendil-works/pi-coding-agent.

Security

What our scanner noticed· Medium risk

  • References to credential files
  • Instructions that use the network
  • Downloads piped into a shell

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
K-Dense Inc.
Publisher
K-Dense (Community)
Source
K-Dense-AI/scientific-agent-skills · skills/pi-agent · commit a25cf9e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE.md)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by K-Dense Inc. or K-Dense.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pi-agent.zip