New issues and PRs from new contributors are auto-closed by default. Maintainers review auto-closed issues daily. See CONTRIBUTING.md.
Pi eXperience Improved.
Pixi is Pi with extra UX and provider work merged in. Nothing is taken away: providers, config, extensions, skills, prompt templates, themes, packages, RPC, and the SDK behave exactly as Pi documents them.
This README covers what Pixi adds and how to install it. Pi itself is documented elsewhere, and those docs apply here as-is:
- Pi README — project overview, Nix builds, monorepo packages, release binaries, supply-chain rules
- pi.dev/docs — setup and usage
packages/coding-agent/docs— sessions, CLI, RPC, SDK, extensions, skills, prompt templates, themes, containerization
curl -fsSL https://raw.githubusercontent.com/Panoplos/Pixi/main/scripts/install.sh | shThe installer downloads the latest release binary for your platform from the releases page and installs it as pixi.
Until the first release is published, run Pixi from source:
git clone https://github.com/Panoplos/Pixi && cd Pixi
npm install --ignore-scripts
npm run build
mkdir -p ~/.local/bin && ln -s "$PWD/packages/coding-agent/dist/bundle/cli.js" ~/.local/bin/pixiPixi needs Node.js 22.19 or newer. Start it in the directory you want to work in, connect a provider with /login, and give it a task:
cd /path/to/project
pixi- Extra providers — Bitdeer, DeepInfra, and Inco are wired in as first-class providers, with model catalogs seeded from live API data and refreshed by the model generator.
- Next-message suggestions — after each assistant reply, a small model drafts the suggested next prompt, shown as ghost text that fills in word by word; Tab accepts the whole line, or the right arrow accepts it a word at a time. The suggestion model is picked separately from your main model — choose it in
/settings→ Suggestion model, or setsuggestions.model(a"provider/model"string) in~/.pi/agent/settings.json— so a fast, cheap model can draft suggestions while your main model does the heavy lifting.
- Model picker grouped by lab —
/modelgroups models by the company that makes them, and/thinkingand/contextlet you tune reasoning effort and context display without digging through settings. - Editor UX — click to position the cursor, drag to select with delete/replace, and pasted images become atomic
[Image N]markers that move and delete as one unit. Selections copy straight to the system clipboard.
- Queued messages — type follow-ups while Pixi is still working; they send in order, images intact.
- Write/edit previews — tool previews render proper diffs for file writes and edits, so you can review changes before they land.
- Collapsible activity — batches of tool calls collapse into one-line summaries ("ran 1 shell command, read 1 file") that expand in place with ctrl+o, and a thinking spinner shows what Pixi is doing between actions.
- Configurable prompt prefix — the input editor prefix is a
promptPrefixsetting with a matching optional theme color (falls back toaccent).
- RPC on a running session — an interactive session serves the RPC protocol on
~/.pi/agent/rpc/<session id>.sock, so a script or editor can prompt or inspect a session you are using in the terminal; the footer showsrpc <session id>while it is on, and--no-rpcturns it off. See RPC mode and CLI Integration forRpcClientandconnectRpcClient().
- Secret masking —
key-guard.tsmasks API keys, tokens, and PEM blocks before they enter model context. It shells out topixi-mask, a 1.5 MB Rust CLI that runs the betterleaks rule set over a tool result in a few milliseconds, and falls back to in-process patterns when the binary is not onPATH.
Like Pi, Pixi has no built-in permission system: it runs with the permissions of the user and process that launched it. For stronger boundaries, containerize it — see containerization for a host-plus-micro-VM extension, plain Docker, and policy-controlled sandboxes.
npm install --ignore-scripts # Install all dependencies without running lifecycle scripts
npm run build # Refresh model data, then build all packages
npm run build:offline # Rebuild using existing model data without network access
npm run check # Lint, format, and type check
./test.sh # Run tests (skips LLM-dependent tests without API keys)
./pi-test.sh # Run pixi from sources (can be run from any directory)Pixi follows Pi's monorepo layout and build scripts. For Nix builds, local package artifacts, standalone binaries, and the supply-chain rules (pinned dependencies, the lockfile gate), use the matching sections of Pi's README.
See CONTRIBUTING.md for contribution guidelines and AGENTS.md for project-specific rules (for both humans and agents). Longer term plans for Pi live in the RFCs.
MIT







