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

@taico/worker

v0.3.3

Published

Runtime for the current Taico worker.

Readme

@taico/worker

Runtime for the current Taico worker.

The worker connects to an existing Taico server, claims eligible work, starts executions, prepares workspaces, and launches the configured agent runtime.

Start

npx @taico/worker --serverurl http://localhost:1234

The helper script helpers/start-worker.sh wraps this for the common local setup.

Recommended Usage

The recommended way to run the worker is locally via npx.

That lets it use:

  • your existing provider logins
  • your local developer tools
  • your local shell environment
  • any CLIs already configured on the machine

That is convenient, but it also means the worker inherits real host capabilities. Run it only on a machine you trust for that level of access.

Authentication

On first startup, the worker performs browser-based authorization against the Taico server and stores credentials locally. After that it refreshes and reuses those credentials automatically.

Default credentials path:

  • ~/.taico/worker-credentials.json

Default workspace root:

  • ~/.taico/workspaces

Options

  • --serverurl: required Taico server base URL
  • --credentials-path: override the stored worker credentials path
  • --working-directory: override the workspace root used for task workspaces

Supported Agent Runtimes

  • GitHub Copilot
  • OpenCode
  • Google ADK
  • Claude

For OpenCode, GitHub Copilot, and Claude, the worker uses whatever local installation and authentication state already exists on the host.

Google ADK

If you want to use Google models via ADK, set:

export GOOGLE_CLOUD_PROJECT="your-project-id"
export GOOGLE_CLOUD_LOCATION="your-location"
export GOOGLE_GENAI_USE_VERTEXAI="True"

The helper script includes placeholders for those variables.

Runtime Model

This worker is execution-centric.

  • the backend decides which tasks are eligible
  • the worker claims work
  • the worker starts an execution
  • the worker requests short-lived agent execution tokens as needed
  • execution activity is reported back to Taico

If you see old docs referring to an orchestrator or agent runs, that is legacy terminology.