19ce8059c3
In regular TUI mode, user and assistant messages wrote OSC 133 (`A`/`B`/`C`) shell-integration markers straight to the terminal. Terminals that display OSC 7501 program status (Rex, iTerm2 3.7.5+) read `133;A` as a new shell prompt and drop the current status. As a result, the `working` indicator disappeared right after a run started and only `done` showed up at the end. Fullscreen mode was not affected because it already strips these markers before writing. ## Change - `TuiMainScreen.doRender()` (`packages/tui/src/tui-main-screen.ts`) now strips OSC 133 markers from the start of each rendered line before compositing and writing. It uses the same pattern as fullscreen (`OSC133_ZONE_PREFIX`). - The message components still produce the markers. Fullscreen uses them internally for prompt navigation and already strips them before writing, so its behavior is unchanged. - In regular mode, the terminal's own jump-to-prompt shortcuts no longer stop at pi messages (added in #1805). ## Testing - New test in `packages/tui/test/tui-render.test.ts`: no `ESC]133;` reaches the terminal across a full render and a differential render, with both BEL and ST terminators. It fails without the change and passes with it. - These pass: - `packages/tui` `npm test` - `test/user-message.test.ts` and `test/assistant-message.test.ts` in coding-agent - `npm run check` - I ran `pi -ne --tui-mode regular` with `PI_PROGRAM_STATUS=1` and a streaming test provider, capturing all terminal output with `script`. - Before: `7501 working`, then repeated `133;A`/`133;B`/`133;C`, then `7501 done`. - After: only `7501 idle` → `working` → `done`, and no OSC 133. Fixes #11519 Requested by @davidbrai 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