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

openwork-server

v0.11.200

Published

Filesystem-backed API for OpenWork remote clients

Readme

OpenWork Server

Filesystem-backed API for OpenWork remote clients. This package provides the OpenWork server layer described in apps/app/pr/openwork-server.md and is intentionally independent from the desktop app.

Quick start

npm install -g openwork-server
openwork-server --workspace /path/to/workspace --approval auto

openwork-server ships as a compiled binary, so Bun is not required at runtime.

Or from source:

pnpm --filter openwork-server dev -- \
  --workspace /path/to/workspace \
  --approval auto

The server logs the client token and host token on boot when they are auto-generated.

Add --verbose to print resolved config details on startup. Use --version to print the server version and exit.

Config file

Defaults to ~/.config/openwork/server.json (override with OPENWORK_SERVER_CONFIG or --config).

{
  "host": "127.0.0.1",
  "port": 8787,
  "approval": { "mode": "manual", "timeoutMs": 30000 },
  "workspaces": [
    {
      "path": "/Users/susan/Finance",
      "name": "Finance",
      "workspaceType": "local",
      "baseUrl": "http://127.0.0.1:4096",
      "directory": "/Users/susan/Finance"
    }
  ],
  "corsOrigins": ["http://localhost:5173"]
}

Environment variables

  • OPENWORK_SERVER_CONFIG path to config JSON
  • OPENWORK_HOST / OPENWORK_PORT
  • OPENWORK_TOKEN client bearer token
  • OPENWORK_HOST_TOKEN host approval token
  • OPENWORK_APPROVAL_MODE (manual | auto)
  • OPENWORK_APPROVAL_TIMEOUT_MS
  • OPENWORK_WORKSPACES (JSON array or comma-separated list of paths)
  • OPENWORK_CORS_ORIGINS (comma-separated list or *)
  • OPENWORK_OPENCODE_BASE_URL
  • OPENWORK_OPENCODE_DIRECTORY
  • OPENWORK_OPENCODE_USERNAME
  • OPENWORK_OPENCODE_PASSWORD

Token management (scoped tokens):

  • OPENWORK_TOKEN_STORE path to token store JSON (default: alongside server.json)

File injection / artifacts:

  • OPENWORK_INBOX_ENABLED (1 | 0)
  • OPENWORK_INBOX_MAX_BYTES (default: 50MB, capped)
  • OPENWORK_OUTBOX_ENABLED (1 | 0)

Sandbox advertisement (for capability discovery):

  • OPENWORK_SANDBOX_ENABLED (1 | 0)
  • OPENWORK_SANDBOX_BACKEND (docker | container | none)

Endpoints

  • GET /health
  • GET /status
  • GET /capabilities
  • GET /whoami
  • GET /workspaces
  • GET /workspace/:id/config
  • PATCH /workspace/:id/config
  • GET /workspace/:id/events
  • POST /workspace/:id/engine/reload
  • GET /workspace/:id/plugins
  • POST /workspace/:id/plugins
  • DELETE /workspace/:id/plugins/:name
  • GET /workspace/:id/skills
  • POST /workspace/:id/skills
  • GET /workspace/:id/mcp
  • POST /workspace/:id/mcp
  • DELETE /workspace/:id/mcp/:name
  • GET /workspace/:id/commands
  • POST /workspace/:id/commands
  • DELETE /workspace/:id/commands/:name
  • GET /workspace/:id/audit
  • GET /workspace/:id/export
  • POST /workspace/:id/import

Token management (host/owner auth):

  • GET /tokens
  • POST /tokens (body: { "scope": "owner"|"collaborator"|"viewer", "label"?: string })
  • DELETE /tokens/:id

Inbox/outbox:

  • POST /workspace/:id/inbox (multipart upload into .opencode/openwork/inbox/)
  • GET /workspace/:id/artifacts
  • GET /workspace/:id/artifacts/:artifactId
  • POST /workspace/:id/files/sessions
  • POST /files/sessions/:sessionId/renew
  • DELETE /files/sessions/:sessionId
  • GET /files/sessions/:sessionId/catalog/snapshot
  • GET /files/sessions/:sessionId/catalog/events
  • POST /files/sessions/:sessionId/read-batch
  • POST /files/sessions/:sessionId/write-batch
  • POST /files/sessions/:sessionId/ops

Toy UI (static assets served by the server):

  • GET /ui
  • GET /w/:id/ui
  • GET /ui/assets/*

OpenCode proxy:

  • GET|POST|... /opencode/*
  • GET|POST|... /w/:id/opencode/*

OpenCode Router proxy:

  • GET|POST|... /opencode-router/*
  • GET|POST|... /w/:id/opencode-router/*

Auth policy:

  • GET /opencode-router/health requires client auth.
  • All other /opencode-router/* endpoints require host/owner auth.

Approvals

All writes are gated by host approval.

Host APIs accept either:

  • X-OpenWork-Host-Token: <token> (legacy host token), or
  • Authorization: Bearer <token> where the token scope is owner.

Approvals endpoints:

  • GET /approvals
  • POST /approvals/:id with { "reply": "allow" | "deny" }

Set OPENWORK_APPROVAL_MODE=auto to auto-approve during local development.