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

@perstack/runtime

v0.0.111

Published

Perstack Runtime

Readme

@perstack/runtime

The execution engine library for Perstack agents. This is a pure library — it has no CLI. CLI functionality is provided by the perstack package.

Installation

npm install @perstack/runtime

Usage

The primary entry point is the run function:

import { run } from "@perstack/runtime"

const checkpoint = await run(
  {
    setting: {
      model: "claude-sonnet-4-5",
      providerConfig: { providerName: "anthropic", apiKey: "..." },
      jobId: "job-123",
      runId: "run-123",
      expertKey: "researcher",
      input: { text: "Research quantum computing" },
      experts: { /* expert definitions */ },
    },
  },
  {
    eventListener: (event) => console.log(`[${event.type}]`, event),
  },
)

Public API

| Export | Description | | --- | --- | | run(input, options) | Execute an expert run. Returns a Checkpoint. | | runtimeVersion | Current runtime semver string. | | collectToolDefinitionsForExpert() | Collect tool definitions from an expert's skills. | | getLockfileExpertToolDefinitions() | Extract tool definitions from a lockfile expert entry. | | runtimeStateMachine | XState machine definition (for advanced use). |

Events

The eventListener callback receives RunEvent | RuntimeEvent objects with granular execution details:

eventListener: (event) => {
  if (event.type === "callTools") {
    console.log(`Executing ${event.toolCalls.length} tools`)
  }
}

Architecture

Job (jobId)
 ├── Run 1 (Coordinator Expert)
 │    └── Checkpoints...
 ├── Run 2 (Delegated Expert A)
 │    └── Checkpoints...
 └── Run 3 (Delegated Expert B)
      └── Checkpoints...

| Concept | Description | | --- | --- | | Job | Top-level execution unit. Contains all Runs. | | Run | Single Expert execution within a Job. | | Checkpoint | Immutable snapshot at each step boundary. Enables pause/resume. |

The runtime drives the agent loop (Reason → Act → Observe), manages checkpoints for state persistence, provides MCP-based tool execution, and handles expert-to-expert delegation.

Skill Managers

| Type | Manager | Purpose | | --- | --- | --- | | MCP (stdio/SSE) | McpSkillManager | External tools via MCP protocol | | Interactive | InteractiveSkillManager | User input tools (Coordinator only) | | Delegate | DelegateSkillManager | Expert-to-Expert calls |

State Machine

The runtime uses an XState state machine for deterministic execution flow:

Init → PreparingForStep → GeneratingToolCall → CallingMcpTools → ...
  ↓                                              ↓
ResumingFromStop                            CallingDelegates → CallingInteractiveTools
                                                                     ↓
                                               ResolvingToolResult → FinishingStep → (loop)

Terminal states: completed, stoppedByError, stoppedByExceededMaxSteps, stoppedByInteractiveTool, stoppedByDelegate, stoppedByCancellation

Related Documentation