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

opencode-top

v3.5.11

Published

Monitor OpenCode AI coding sessions - Token usage, costs, and agent analytics

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

nielk74nielk74

Keywords

opencodeaimonitoringtuicli

Readme

opencode-top

Monitor your OpenCode AI coding sessions in real-time — token usage, costs, agent chains, tool calls, and more.

opencode-top TUI

Install

npm install -g opencode-top

Usage

opencode-top live      # Live monitoring dashboard (default)
opencode-top sessions  # Print session table and exit

Requires OpenCode to have been run at least once (reads from ~/.local/share/opencode/opencode.db).

Screens

| Key | Screen | Description | |-----|--------|-------------| | 1 | Sessions | Browse sessions and agent trees, view stats and messages | | 2 | Tools | Tool usage analytics — call counts, error rates, avg duration | | 3 | Overview | Aggregate stats, 7-day trends, hourly activity heatmap |

Keyboard shortcuts

Sessions screen

| Key | Action | |-----|--------| | j / k | Navigate session list | | g / G | Jump to top / bottom | | Tab | Switch between Stats and Messages view |

Messages view

| Key | Action | |-----|--------| | j / k | Move cursor line by line | | d / u | Scroll half page down / up | | g / G | Jump to top / bottom | | Enter | Expand / collapse tool call (shows input params + output) | | [ / ] | Previous / next session |

Global

| Key | Action | |-----|--------| | 1 2 3 | Switch screens | | r | Force refresh | | q | Quit |

What you see

  • Session list — title, date, token count, cost per session and sub-agent
  • Stats panel — tokens, cost, duration, output rate, context usage, top tools, agent chain graph
  • Messages panel — chronological tool calls with ✓/✗ status, duration, expand for full input/output; interaction headers show ↓in ↑out token counts and cumulative token progress
  • Tools screen — ranked tool list sortable by calls / failures / avg time
  • Overview screen — cross-session totals, model breakdown, 7-day spark charts, hourly heatmap

Requirements

  • Node.js >= 20
  • OpenCode installed and used at least once

Development

git clone https://github.com/Nielk74/opencode-top
cd opencode-top
npm install
npm start live   # run from source with tsx

Maintenance

Publishing a new version

  1. Make and commit your changes
  2. Bump the version in package.json
  3. Build and publish:
npm publish --access public

The prepublishOnly script runs the build automatically before publishing. The bin entry must point to bin/octop.js (not bin/octop.mjs) — octop.js loads the pre-built dist/cli.mjs and has no runtime dependencies.