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

@postqode/agent-tui

v0.9.0

Published

Lean terminal UI for a PostQode coding agent — a readline + ANSI REPL on top of @postqode/agent's event stream. Streams text, renders tool calls, shows usage, and ships slash commands. Zero heavy UI deps.

Readme

@postqode/agent-tui

A terminal UI for a PostQode coding agent on top of @postqode/agent's event stream. Two frontends, same agent core and config:

  • postqode-tui — rich UI built on OpenTUI (React + a native renderer). Requires Bun (OpenTUI's renderer is exposed via bun:ffi).
  • postqode-tui-node — dependency-free readline + ANSI REPL on plain Node (no Bun, no native deps). The portable fallback.

Both reuse @postqode/headless-agent's config loading, so the same env vars / flags / agent.config.json apply and every provider is available — including postqode.

Run

OpenTUI (Bun):

bun run tui                                   # from this package
postqode-tui --provider anthropic --model claude-sonnet-4.5
postqode-tui --provider openai --base-url <azure-resource> \
  --azure-api-version 2025-04-01-preview --model gpt-5.5

Readline fallback (Node):

postqode-tui-node
postqode-tui-node --provider postqode --base-url https://gateway --model anthropic/claude-sonnet-4.5

The OpenTUI app lives in src/opentui/ (run from source under Bun; typecheck with npm run typecheck:opentui). The readline app is the compiled dist/cli.js.

Each prompt extends the same conversation (the agent is stateful). A spinner covers the wait for the first token; text streams as it arrives; tool calls render inline.

Flags

| Flag | Meaning | |---|---| | --provider <name> | anthropic, openai, openrouter, gemini, postqode, … | | --model <id> | model id (default: provider default) | | --base-url <url> | OpenAI-compatible / postqode gateway URL | | --azure-api-version <v> | Azure OpenAI api-version | | --max-turns <n> / --max-cost <usd> | per-prompt budgets | | --tools emoji\|minimal\|hidden | tool-call display (default emoji) | | --reasoning | show the model's reasoning, dimmed |

Slash commands

/help · /model · /cost · /new (fresh conversation) · /clear · /exit (or Ctrl-D). Ctrl-C aborts an in-flight turn; again while idle exits.

Programmatic

import { runTui } from "@postqode/agent-tui"
import { loadConfig } from "@postqode/headless-agent"

await runTui({ config: loadConfig({ provider: "anthropic" }), toolDisplay: "emoji" })

The rendering and command layers (formatEvent, handleCommand, Renderer) are exported and pure, so they're unit-testable without a TTY.