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

@open-harness/core

v1.0.0-alpha.3

Published

**TypeScript-native agent framework. Signals. Recording. Evals.**

Readme

@open-harness/core

TypeScript-native agent framework. Signals. Recording. Evals.

const analyst = agent({
  prompt: "Analyze {{ state.symbol }}",
  activateOn: ["workflow:start"],
  when: (ctx) => ctx.state.ready,
  emits: ["analysis:complete"],
});

const trader = agent({
  prompt: "Trade based on {{ signal.payload.output }}",
  activateOn: ["analysis:complete"],
  when: (ctx) => ctx.state.analysis?.confidence > 0.8,
});

await runReactive({
  agents: { analyst, trader },
  state: { symbol: "AAPL", analysis: null },
  harness: new ClaudeHarness(),
});

Two agents. Signal-based coordination. Typed guards. 15 lines.


Install

bun add @open-harness/core
# or
npm install @open-harness/core

What You Get

Test the execution, not just the output

import { expect } from "vitest";
import "@open-harness/vitest";

expect(result.signals).toHaveSignalsInOrder([
  "workflow:start",
  "analysis:complete",
  "trade:proposed",
]);

expect(result.signals).toHaveSignalCount("agent:activated", 2);
expect(result).toCostUnder(0.05);
expect(result).toHaveLatencyUnder(5000);

Built on Vitest. Assert on signal flow, cost, and latency.

Record once, replay forever

// Record live execution
await runReactive({
  agents,
  state,
  fixture: "my-workflow",
  mode: "record",
  store,
});

// Replay in CI (zero API calls)
await runReactive({
  agents,
  state,
  fixture: "my-workflow",
  mode: "replay",
  store,
});

Your agent tests run in milliseconds.

Swap providers without rewriting

// Claude
const result = await runReactive({
  agents,
  state,
  harness: new ClaudeHarness(),
});

// OpenAI - one line change
const result = await runReactive({
  agents,
  state,
  harness: new CodexHarness(),
});

Same agents. Different model.


Quick Start

import { createWorkflow, ClaudeHarness } from "@open-harness/core";

// Define your state
interface MyState {
  name: string;
  greeting: string | null;
}

// Create typed workflow
const { agent, runReactive } = createWorkflow<MyState>();

// Define an agent
const greeter = agent({
  prompt: "Create a greeting for {{ state.name }}",
  activateOn: ["workflow:start"],
  updates: "greeting",
});

// Run it
const result = await runReactive({
  agents: { greeter },
  state: { name: "World", greeting: null },
  harness: new ClaudeHarness(),
  endWhen: (state) => state.greeting !== null,
});

console.log(result.state.greeting);

Core Concepts

Signals, not spaghetti

Agents subscribe to signal patterns. No imperative chains.

const myAgent = agent({
  prompt: "Your prompt with {{ state.field }} templates",
  activateOn: ["workflow:start"],  // When to activate
  emits: ["my:complete"],          // What to emit on success
  updates: "field",                // State field to update
  when: (ctx) => ctx.state.ready,  // Guard condition
});

Signal flow

workflow:start → agent activates → emits signal → next agent → workflow:end

Every step is observable. Every step is testable.


Packages

| Package | Purpose | |---------|---------| | @open-harness/core | Workflow API, harnesses, signals | | @open-harness/vitest | Vitest matchers for testing | | @open-harness/testing | Test utilities | | @open-harness/stores | Persistence (SQLite, file) | | @open-harness/server | Server-side streaming | | @open-harness/client | Client transports | | @open-harness/react | React hooks |


Why This Exists

We got tired of:

  • Testing agents by eyeballing output
  • Hitting APIs on every test run
  • Rewriting when providers change
  • Multi-agent code nobody can follow

So we built the framework we wanted to use.


GitHub · Docs · Discord