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

@obversa/engine-opencode-cli

v0.1.7

Published

Run one engine attempt through a fresh OpenCode CLI process, with your own OpenCode login.

Downloads

1,167

Readme

@obversa/engine-opencode-cli

@obversa/engine-opencode-cli runs one Obversa engine attempt through a fresh OpenCode CLI process.

The plugin runs OpenCode clean by default: with your own home folder and your OpenCode login, but with an empty config folder in place of yours, so your OpenCode settings stay out. Set clean: false to run it the way you run it, with your own config folder too. It adds only what the step needs, through OpenCode's own config: the tools and permission rules the step declares, no autoupdate and no sharing. Every other tool is set to ask, so OpenCode turns down each call to it and the tool doesn't run.

Requirements

  • Node.js 22.12 or later
  • OpenCode CLI 1.18.23, the version the plugin is tested with
  • OpenCode signed in to your model's provider, or login data passed as auth
  • Any model OpenCode runs, free models such as opencode/big-pickle included. Free models says what they cost.

Free models

OpenCode's free models refuse any run whose config turns a tool off or denies a permission. So the plugin does neither. It sets each tool the step doesn't declare to ask. A declared tool the step limits to a pattern, such as Bash(git status), is set to ask for everything else.

A free model gives up nothing for this. opencode run turns down every ask, because nobody is there to answer it, and the plugin never passes the flags that would approve them, such as --auto. So a tool the step doesn't declare never runs, and a step's limits hold the same way on a free model as on a paid one.

What it costs: the model sees all of OpenCode's tools, not only the ones the step declares. When it calls one the step doesn't declare, OpenCode turns the call down and tells the model, and the model carries on with the step.

Install

pnpm add @obversa/engine-opencode-cli

Use

import { OpenCodeCliEngine } from '@obversa/engine-opencode-cli';

const engine = new OpenCodeCliEngine({
  executable: '/absolute/path/to/opencode',
  version: '1.18.23',
  identity: { provider: 'anthropic', modelFamily: 'claude' },
});