npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pi-llama-server

v1.2.0

Published

Pi extension for llama-server router - model discovery, auto-load, per-project config

Readme

Note: This is how I use pi.dev + llama.cpp on my local machine. I created a plugin so that I can update my setup quickly.

pi-llama-server

Pi extension that integrates a running llama-server instance with the Pi Coding Agent. Discovers llama-server models and automatically loads the selected model when you switch models in Pi.

Demo

Demo

Prerequisites

  • A running llama-server instance (from llama.cpp) in router-mode (the default if you don't mention -m)
  • Pi Coding Agent installed (@earendil-works/pi-coding-agent)

Install

pi install npm:pi-llama-server

Or from git:

pi install git:github.com/user/pi-llama-server

Pi auto-discovers the extension via pi.extensions in package.json. No additional setup needed.

Configuration

The llama-server URL is resolved in this order:

  1. Per-project config — create .pi/llama-server.json in your project root:
    { "url": "http://10.0.0.5:9090" }
  2. Environment variable — set globally:
    export LLAMA_SERVER_URL=http://10.0.0.5:9090
  3. Default — falls back to http://127.0.0.1:9931

API Key (optional)

If your llama-server endpoint requires authentication, set an API key:

  1. Per-project config — add apiKey to .pi/llama-server.json:
    { "url": "http://10.0.0.5:9090", "apiKey": "your-api-key" }
  2. Environment variable:
    export LLAMA_SERVER_API_KEY=your-api-key

The API key is sent as a Bearer token on all requests to the server.

Usage

Use Ctrl+P (or /model) in Pi to select any llama-server model for inference. Pi switches to that model, and the extension automatically tells llama-server to load it. While llama-server reports loading progress, Pi shows a progress bar in the footer status.

After each llama-server response, the footer also shows the speed of that request:

PP 965.1 t/s (465 tok) · TG 134.0 t/s (89 tok)
  • PP (prefill / prompt processing): uncached prompt tokens divided by the time from sending the request to the first streamed token. Prompt tokens served from llama-server's cache are not counted.
  • TG (token generation): output tokens after the first, divided by the time from the first to the last streamed token.

Both are measured on the client as the response streams in. TG closely matches llama-server's own predicted_per_second. PP also includes per-request overhead (chat templating, tokenization, HTTP), so on short prompts it reads well below llama-server's prompt_per_second; the gap shrinks as prompts grow.

How it works

When Pi starts, the extension:

  1. Resolves the llama-server URL from config/env/default
  2. Queries GET /models to discover available GGUF models
  3. Registers each model as an OpenAI-compatible provider under {url}/v1
  4. Listens for model switch events and calls POST /models/load on the server
  5. Listens to GET /models/sse while a selected model is loading to show footer progress

llama-server endpoints used

| Endpoint | Method | Purpose | |----------|--------|---------| | /models | GET | List all models | | /models/load | POST | Load a model | | /models/sse | GET | Stream model status/progress events | | /v1/... | POST | OpenAI-compatible completions (via Pi provider) |