7391dbb0f8
In fullscreen mode, the startup `Model scope: …` notice was still in the shell after pi exited. With `fullscreenExitOutput: "resume-hint"`, the shell showed it above the resume command. Cause: `InteractiveMode.init()` printed the notice with `console.log` before the renderer started. In fullscreen mode that output goes to the terminal's normal screen. Pi then draws on the alternate screen, and when it exits the terminal switches back to the normal screen, where the notice is still visible. The change: - Building the notice text moves into `getModelScopeNotice()`. - Regular mode prints it with `console.log` before the TUI starts, as before. - Fullscreen mode adds it to the header container below the built-in header. It uses a `ThemedText`, so the text is built after the terminal reports its colors and follows theme changes. Since fullscreen is the default `tuiMode`, this applies to every user who has `enabledModels` set and quiet startup off. Testing: - Added `packages/coding-agent/test/interactive-mode-model-scope.test.ts`. It checks two things for fullscreen: the notice renders in the header and `console.log` is not called, and nothing is added when startup details are hidden. - `npm run check` passes. - Manual check in tmux with `enabledModels` set: - fullscreen + `resume-hint`: before the change, `Model scope: claude-sonnet-4-5, claude-opus-4-5 (Ctrl+P to cycle)` was left in the shell after `/quit`. Now the line shows inside pi's header and the shell is clean after exit. - `tuiMode: "regular"`: unchanged, the line is still printed above the header. Fixes #11508 Requested by @badlogic Co-authored-by: triagent <triagent@localhost> |
||
|---|---|---|
| .. | ||
| docs | ||
| examples | ||
| install-lock | ||
| schemas | ||
| scripts | ||
| src | ||
| test | ||
| .gitignore | ||
| CHANGELOG.md | ||
| package.json | ||
| README.md | ||
| tsconfig.build.json | ||
| tsconfig.examples.json | ||
| vitest.config.ts | ||
New issues and PRs from new contributors are closed automatically. Maintainers review closed submissions daily. See CONTRIBUTING.md.
Pi
Pi is a minimal, extensible agent harness that you can make your own.
Adapt Pi to your workflows, not the other way around. Customize Pi with extensions, skills, prompt templates, and themes. Bundle them as Pi packages and share via npm or git.
Pi ships with powerful defaults but skips features like sub-agents and plan mode. Ask Pi to build what you want, or install a package that does it your way.
Use Pi interactively, automate it in print or JSON mode, control it over RPC, or build apps with the Pi TypeScript SDK. See OpenClaw for a real-world integration.
Getting started
Install the command-line interface:
curl -fsSL https://pi.dev/install.sh | sh
On Windows:
powershell -c "irm https://pi.dev/install.ps1 | iex"
The installer pins all dependencies and updates Pi with pi update. Alternatively, install directly with npm, which does not pin transitive dependencies:
npm install -g --ignore-scripts @earendil-works/pi-coding-agent
Pi requires Node.js 22.19 or newer. The macOS, Linux, and Windows installers can install it if needed. Pi does not require dependency lifecycle scripts for a normal npm installation.
On macOS and Linux, Nix users can install the latest release with nix profile add github:earendil-works/pi/stable. See the quickstart for updating and pinning releases.
Start Pi in the directory where you want it to work:
cd /path/to/project
pi
For a built-in AI provider, run /login inside Pi to connect a subscription or API key. Then give Pi a task.
See the documentation for full setup and usage instructions.
Share your OSS coding agent sessions
If you use Pi for open source work, please share your coding agent sessions.
Public OSS session data helps improve models, prompts, tools, and evaluations using real development workflows.
For the full explanation, see this post on X.
To publish sessions, use badlogic/pi-share-hf using a Hugging Face account and the Hugging Face CLI.
- Demo video on how to publish Pi sessions
- Published Pi development sessions:
badlogicgames/pi-monoon Hugging Face.
Development
Clone the repository, install its dependencies, and run Pi from source:
git clone https://github.com/earendil-works/pi
cd pi
npm install --ignore-scripts
./pi-test.sh
pi-test.sh can be called from any directory and preserves the caller's working directory.
Before submitting changes, run:
npm run check
./test.sh
Read CONTRIBUTING.md before opening an issue or pull request. It defines the contribution gate, issue quality bar, and required checks. Read AGENTS.md for repository-specific implementation, testing, dependency, and release rules.
License
MIT