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

@executioncontrolprotocol/browser

v0.12.0

Published

ECP browser runtime and environment extensions

Readme

@executioncontrolprotocol/browser

Browser runtime host for ECP: in-browser executor, registry extensions, session/local config, and helpers to initialize Ecp in a web page.

This is not the browser demo application. UI, provider picker, harness selection, and demo-only persistence belong in the standalone browser demo repo.

What belongs here

| In @executioncontrolprotocol/browser | In the browser demo app (or your app) | | ----------------- | ------------------------------------- | | Browser runtime executor | React/Vite shell, chat layout, panels | | browser-registry, session/local config | First-run modal, provider + harness mode UI | | createEcp(), installBrowserWorkflowShim() | Monaco, Mermaid viewer, CSS | | registerBrowserHost() / slim createBrowserEnvironment() | Binding formats, model providers, harnesses | | Panel encode helper (BrowserAuthoringService) | Which harness + providerCapabilityId to invoke |

Do not add demo-app UI types here (e.g. ProviderMode unions). Those stay in the demo app.

Harness-independent: this package does not depend on @executioncontrolprotocol/harnesses-browser-nano or coding harnesses. Apps register and bind harnesses themselves.

Host registration

import { registerBrowserHost, createBrowserEnvironment, createEcp } from "@executioncontrolprotocol/browser"

await registerBrowserHost()
const env = createBrowserEnvironment("my-app")
// App adds extensions / harnesses / policies as needed:
// env.addExtensionBinding(...); env.withHarnesses([...])
const ecp = await createEcp(env, { exposeGlobal: true })

registerBrowserDefaults / createBrowserDemoEnvironment remain as deprecated aliases of the slim host APIs.

Compile-on-edit

Use @executioncontrolprotocol/core/browser for compileWorkflowSource / compileHarnessArtifactSource (not this package). Call installBrowserWorkflowShim() before compile so Fluent source can use @executioncontrolprotocol/browser imports or the injected shim.

Dependencies

This package depends on @executioncontrolprotocol/core, @executioncontrolprotocol/types, @executioncontrolprotocol/policies, and @executioncontrolprotocol/browser-secrets. Model providers, format extensions, and harnesses are app dependencies.

Tests

npm run test:browser:install   # once
npm run test:browser

See AGENTS.md and the browser demo repo.