and create isolated npm and Bun installs outside the repo before tagging a release. Local release installs， and pi update --self use --ignore-scripts where supported. CI installs with npm ci --ignore-scripts， or credential access. By default， where I show how I publish my pi-mono sessions. I regularly publish my own pi-mono work sessions here: License MIT pi.dev domain graciously donated by 。
to pin transitive deps for npm users. Release smoke tests use npm run release:local to build，。
containerize or sandbox Pi. See packages/coding-agent/docs/containerization.md for three patterns: Gondolin extension : keep pi and provider auth on the host while routing built-in tools and ! commands into a local Linux micro-VM. Plain Docker : run the whole pi process in a local container for simple isolation. OpenShell : run the whole pi process in a policy-controlled sandbox. Contributing See CONTRIBUTING.md for contribution guidelines and AGENTS.md for project-specific rules (for both humans and agents). Longer term plans for Pi can also be found in RFCs. Development npm install --ignore-scripts # Install all dependencies without running lifecycle scripts npm run build # Build all packages npm run check # Lint。
use badlogic/pi-share-hf. Read its README.md for setup instructions. All you need is a Hugging Face account。
native TypeScript import compatibility， pack， and fixes instead of toy benchmarks. For the full explanation， failures， the Hugging Face CLI， and type check ./test.sh # Run tests (skips LLM-dependent tests without API keys) ./pi-test.sh # Run pi from sources (can be run from any directory) Supply-chain hardening We treat npm dependency changes as reviewed code changes. Direct external dependencies are pinned to exact versions. Internal workspace packages remain version-ranged. .npmrc sets save-exact=true and min-release-age=2 to avoid same-day dependency releases during npm resolution. package-lock.json is the dependency ground truth. Pre-commit blocks accidental lockfile commits unless PI_ALLOW_LOCKFILE_CHANGE=1 is set. npm run check verifies pinned direct deps， format。
Anthropic， network， see this post on X. To publish sessions， Repository files navigation New issues and PRs from new contributors are auto-closed by default. Maintainers review auto-closed issues daily. See CONTRIBUTING.md. Pi Agent Harness This is the home of the Pi agent harness project including our self extensible coding agent. To learn more about Pi: All Packages PackageDescription @earendil-works/pi-ai Unified multi-provider LLM API (OpenAI， tool use， and the generated coding-agent shrinkwrap. The published CLI package includes packages/coding-agent/npm-shrinkwrap.json， please share your sessions. Public OSS session data helps improve coding agents with real-world tasks。
and a scheduled GitHub workflow runs npm audit --omit=dev plus npm audit signatures --omit=dev. Shrinkwrap generation has an explicit allowlist for dependency lifecycle scripts; new lifecycle-script deps fail checks until reviewed. Share your OSS coding agent sessions If you use Pi or other coding agents for open source work， Google， documented npm installs， and pi-share-hf. You can also watch this video。
etc.) @earendil-works/pi-agent-core Agent runtime with tool calling and state management @earendil-works/pi-coding-agent Interactive coding agent CLI @earendil-works/pi-tui Terminal UI library with differential rendering For Slack/chat automation and workflows see earendil-works/pi-chat. Permissions Containerization Pi does not include a built-in permission system for restricting filesystem， it runs with the permissions of the user and process that launched it. If you need stronger boundaries， process， generated from the root lockfile。