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

@tryopenbot/computer-service

v0.2.0

Published

The API-key-protected ConnectRPC server that runs inside an OpenBot Computer image. It executes lifecycle bundles, agent-scoped commands and file operations, Cua Driver GUI automation, port discovery, and VNC tunneling.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

danielblignautdanielblignaut

Keywords

Readme

@tryopenbot/computer-service

The API-key-protected ConnectRPC server that runs inside an OpenBot Computer image. It executes lifecycle bundles, agent-scoped commands and file operations, Cua Driver GUI automation, port discovery, and VNC tunneling.

Public API

This package is a service executable and declares no importable package exports. Its network contract is @tryopenbot/computer-service-proto, mounted under /rpc; the listening port is COMPUTER_SERVICE_PORT or 4101.

Model-facing requests include an agent ID. The service validates it and defaults relative command and file operations to /workspace/<agent-id>. Agents otherwise share the computer's process identity and filesystem, so this directory is not a security boundary. Agent tools call this service through the generated typed client. The web and desktop applications do not call it directly.

Every RPC requires Authorization: Bearer <COMPUTER_SERVICE_API_KEY>. Init creates this static key only inside configuration/secrets.enc.yaml; deployment installs the same secret into the computer, agent service, and control service without returning it in provider outputs.

Model-controlled processes start with an allowlisted environment, so the service key and other computer-service environment variables are not inherited. HOME is the agent directory, allowing its seeded .profile to initialize Bash login shells.

Background shell commands detach from the service process and keep private job metadata, bounded output, and an exit-status file under /workspace/.openbot/jobs. AwaitExec validates the originating agent ID and can recover a running or completed job after computer-service restarts; jobs still belong to the lifetime of the Computer itself.

ListCuaTools and CallCuaTool expose the exact runtime Cua catalog and result envelope. One lazy private worker receives each agent's display, isolated home/XDG state (including Cua's browser data), and accessibility environment. Legacy screenshot and input RPCs are compatibility translations through Cua. noVNC remains a separate owner preview and takeover transport.