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

acp-client

v0.4.1

Published

Standalone ACP client helpers for launching and talking to Agent Client Protocol agents.

Downloads

1,227

Readme

acp-client

Standalone ACP client helpers for launching and talking to Agent Client Protocol agents.

Package Surfaces

  • acp-client
    • Runtime-neutral ACP stream, connection, session, and registry types.
  • acp-client/node
    • Node stdio process launching, registry cache integration, and binary install helpers.

See docs/api.md for a compact public API map.

import { createNodeAcpClient } from "acp-client/node"

const client = await createNodeAcpClient({
  agent: "codex-acp",
  cwd: process.cwd(),
  clientInfo: {
    name: "example-client",
    version: "1.0.0",
  },
  handler: {
    async requestPermission() {
      return { outcome: { outcome: "cancelled" } }
    },
    async sessionUpdate(params) {
      console.log(params)
    },
  },
})

try {
  const session = await client.newSession({
    cwd: process.cwd(),
    mcpServers: [],
  })
  await session.prompt("Hello from ACP")
} finally {
  await client.close()
}

See examples for runnable Node and inline registry examples.

For supported ACP surfaces, host-owned behavior, and deferred protocol areas, see Protocol Coverage.

Dependency Posture

This package keeps runtime dependencies intentionally small. Archive extraction dependencies are exact-pinned in package.json and chosen to avoid transitive runtime dependencies where practical:

  • modern-tar
  • @ckirby/unbzip2-multistream
  • node-stream-zip

These packages are used for .tar.gz, .tar.bz2, and .zip binary archive installs. Keeping them exact-pinned and zero-transitive reduces supply-chain exposure in the archive installation path. The acp-client maintainers also use two-factor authentication for package maintenance accounts.

Registry Fallback

The Node entrypoint includes a generated fallback copy of the upstream ACP registry so known agents can still resolve when a registry clone is unavailable.

Cache Locations

The Node entrypoint stores package-owned caches under XDG_CACHE_HOME when it is set, otherwise under the user's home cache directory:

  • Registry clone: $XDG_CACHE_HOME/acp-client/registry or ~/.cache/acp-client/registry
  • Downloaded binaries: $XDG_CACHE_HOME/acp-client/binaries or ~/.cache/acp-client/binaries

Hosts can override those paths when they need isolated caches for CI, tests, or sandboxed runtimes:

import { createAcpRegistryService, createNodeAcpClient } from "acp-client/node"

const registryService = createAcpRegistryService({
  cacheDir: "/tmp/acp-client/registry",
})

const client = await createNodeAcpClient({
  agent: "codex-acp",
  cwd: process.cwd(),
  clientInfo: {
    name: "example-client",
    version: "1.0.0",
  },
  registryService,
  binaryCacheDir: "/tmp/acp-client/binaries",
})

License

This project is licensed under the MIT License.