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

@mono-agent/operator-console

v0.3.0

Published

Local browser operator console for core agent settings and recorded runs.

Readme

@mono-agent/operator-console

Category

Category: operator-surface

Responsibility

Local loopback operator surface for agent hosts. It serves a React settings UI, validates registered field-group patches, writes a JSON settings file atomically, and reads local trace registry plus recorded-run artifacts for a Traceability view.

Install / Usage

pnpm --filter @mono-agent/operator-console run build
import { startOperatorConsole } from "@mono-agent/operator-console";
import { CORE_AGENT_FIELD_GROUPS } from "@mono-agent/config";
import { telegramFieldGroup } from "@mono-agent/telegram-adapter";

const consoleServer = await startOperatorConsole({
  configPath: "./mono-agent.config.json",
  fieldGroups: [...CORE_AGENT_FIELD_GROUPS, telegramFieldGroup],
  observability: { artifactDir: "./.mono-agent/artifacts" },
  traceability: { registryDir: "~/.mono-agent/trace-sources" },
});

console.log(`${consoleServer.url}/?t=${consoleServer.token}`);

Public API

  • startOperatorConsole
  • OperatorConsoleOptions, OperatorConsoleStartResult, OperatorConsoleEvent
  • OperatorConsoleObservabilityOptions, OperatorConsoleTraceabilityOptions
  • OPERATOR_CONSOLE_STATIC_DIR from @mono-agent/operator-console/static
  • Field-group types re-exported from @mono-agent/settings

Traceability

The console keeps the existing bearer-protected /api/observability/* endpoints for single-artifact-dir hosts. New /api/traceability/* endpoints read a file-backed source registry and aggregate recent runs across all registered sources:

  • GET /api/traceability/sources
  • GET /api/traceability/runs
  • GET /api/traceability/runs/:sourceId/:runId

When no registry is configured but an observability.artifactDir is present, the traceability API exposes a single fallback local source instead of demo data. Malformed manifests, missing artifact directories, corrupt summaries/events, and stale heartbeats are returned as warnings.

Dependency Boundary

The package depends on @mono-agent/settings and @mono-agent/observability. It must not depend on core config, communication adapters, or the agent harness; hosts compose field groups, trace source lifecycle, and runtime behavior outside the console.

What This Package Does Not Own

It is not a runtime host, credential manager, communication adapter, database, or observability backend. It only reads/writes the configured JSON file and reads local registry/artifact files when explicitly pointed at them.

Verification

pnpm --filter @mono-agent/operator-console run build
pnpm --filter @mono-agent/operator-console run typecheck
pnpm --filter @mono-agent/operator-console run test