Documentation
Installation, configuration, and usage. pi-kit is a desktop interface for pi with model setup, session navigation, code review, and an embedded browser.
Setup
- Install pi-kit and open a project
- Configure a provider or local model
- Create a thread
- Use worktrees and review changes
Getting started
Release assets, first-run setup, project trust, and the first thread.
Read guide →Connect a model↗Provider authentication, LiteLLM, model selection, effort, and usage data.
Read guide →Run a local model↗GGUF files, Hugging Face downloads, engine options, and llama-swap configuration.
Read guide →Workflows
Thread placement, composer context, input requests, session history, and compaction.
Read guide →Worktrees and code review↗Git checkout isolation, diff sources, review comments, sync, and merge operations.
Read guide →Artifacts browser↗Page navigation, agent operations, per-thread sessions, and browser restrictions.
Read guide →Screenshots, inspection, and logs↗Capture scopes, image formats, DOM inspection, and console attachments.
Read guide →Extend pi-kit
Resource types, package installation, scope, skill files, and composer selection.
Read guide →MCP servers and interactive UI↗Server connections, tool exposure, configuration files, A2UI, and MCP Apps.
Read guide →Skill drafting and verification↗Draft generation, outcome replay, approval, and learned-skill records.
Read guide →Self-learning example↗A small Node.js project for drafting, verifying, and reusing a skill.
Read guide →Reference
Project resources, credential resolvers, database recovery, and isolation boundaries.
Read guide →Settings reference↗Settings sections, tabs, configuration scope, and reload behavior.
Read guide →Troubleshooting↗Common errors, configuration checks, and issue-report information.
Read guide →Development and architecture↗Source setup, application layers, build targets, tests, and packaging.
Read guide →Quick links
Start here →Install pi-kit →Get a model →Open your first project →Review changes →Generative UI →Secrets →Threads and controls →Architecture →Documentation follows the development version; released builds may differ. Screenshots use example projects and session data. Source references are listed on each page.