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

@digitalygo/opencode-usage-logger

v0.2.0

Published

A plugin for logging OpenCode AI usage events to an external API.

Readme

@digitalygo/opencode-usage-logger

A plugin for logging OpenCode AI usage events to an external API.

Installation

npm install @digitalygo/opencode-usage-logger
# or
yarn add @digitalygo/opencode-usage-logger
# or
bun add @digitalygo/opencode-usage-logger

Usage

The plugin reads configuration from three sources, in order of precedence:

  1. Plugin options in opencode.json (highest priority)
  2. Dedicated JSON file (.opencode/usage-logging.json by default, or a custom path via configFile)
  3. Environment variables (lowest priority)

Configuration sources

Option 1: Plugin options (recommended for simple setups)

Add configuration directly in opencode.json or opencode.jsonc:

{
  "plugin": [
    ["@digitalygo/opencode-usage-logger", {
      "usageLogApiBase": "https://your-api-endpoint.com",
      "usageLogApiKey": "{env:USAGE_LOG_API_KEY}"
    }]
  ]
}

Option 2: Dedicated JSON file

Create .opencode/usage-logging.json (gitignored by default):

{
  "usageLogApiBase": "https://your-api-endpoint.com",
  "usageLogApiKey": "your-api-key-here"
}

See .opencode/usage-logging.example.json for a template. This file is gitignored and should contain real secrets.

To use a custom file path, set the configFile option:

{
  "plugin": [
    ["@digitalygo/opencode-usage-logger", {
      "configFile": "./config/my-usage-config.json"
    }]
  ]
}

Or use the default .opencode/usage-logging.json:

{
  "plugin": [
    ["@digitalygo/opencode-usage-logger", {
      "configFile": ".opencode/usage-logging.json"
    }]
  ]
}

The configFile contains both usageLogApiBase and usageLogApiKey, so no need to specify them separately.

Option 3: Environment variables

Set these in your shell or .opencode/.env:

# Required: Base URL for the usage logging API
USAGE_LOG_API_BASE=https://your-api-endpoint.com

# Required: API key for authentication
USAGE_LOG_API_KEY=your-api-key-here

Plugin options reference

| Option | Type | Description | |--------|------|-------------| | usageLogApiBase | string | Base URL for the usage logging API. Can be a plain string or {env:VAR_NAME}. | | usageLogApiKey | string | API key for authentication. Can be a plain string or {env:VAR_NAME}. | | configFile | string | Path to a JSON config file containing usageLogApiBase and usageLogApiKey. Default: .opencode/usage-logging.json |

What it logs

This plugin captures usage events for assistant messages including:

  • Event type: message.updated, message.created, usage.updated
  • Model information: provider ID, model ID
  • Token usage: input, output, reasoning tokens
  • Cost information: total usage cost
  • Metadata: project code (from git remote), logged user, timestamp

Local logging

Failed API attempts are logged locally to .opencode/logs/usage-api.log for debugging purposes.

License

MIT