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

@baton-tools/workbench

v1.3.1

Published

Local-first web workbench for Kanban-driven Claude Code terminal sessions.

Vulnerabilities

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

Links

Git

Maintainers

sdg9sdg9

Keywords

agentkanbanterminalopenspecclaude

Readme

@baton-tools/workbench

Local-first Kanban board for launching and monitoring Claude Code terminal sessions against your local projects.

Part of the Baton monorepo. Pairs naturally with @baton-tools/harness — projects with a harness.config.ts get harness-driven actions on the board (approve, status, holdout-check, verify), but the workbench works against any project with OpenSpec changes (and is adapter-shaped to support other source-of-truth backends in the future).

What it is

  • Browser UI that shows project cards in Kanban columns (active / attention / ready-to-merge / done).
  • Card source adapters — the first is OpenSpec (reads openspec list --json). Future adapters can read GitHub issues, Linear, plain markdown.
  • Per-card sessions — moving a card to an active column can create or attach a terminal session.
  • Durable terminals — sessions run locally through a PTY, attached to tmux for survival across browser/tab restarts.
  • Local-first — the server binds to 127.0.0.1 by default; nothing leaves the host unless you put it behind your own Cloudflare Tunnel + Access.

Intended Runtime

Browser UI
  <-> local HTTP/WebSocket server on 127.0.0.1
  <-> PTY/tmux session manager
  <-> claude / shell
  <-> allowlisted project workspaces

Cloudflare Tunnel can expose the local server with Cloudflare Access restricted to a single email if you want remote access.

Getting started

# In the monorepo
pnpm install
pnpm --filter @baton-tools/workbench dev      # vite dev server (browser UI)
pnpm --filter @baton-tools/workbench server   # backend (PTY/tmux/HTTP)
pnpm --filter @baton-tools/workbench test

Configuration lives in config/:

  • config/agents.example.json — copy to config/agents.json and edit to set bind host, allowed agent commands, tmux session prefix, idle-notification timeout.
  • config/projects.example.json — copy to config/projects.json and edit to allowlist your project paths, set per-project default agent, and choose the adapter.

Local Auth and Remote Access

The server binds to 127.0.0.1 (configurable in config/agents.json). Terminal/session APIs require either:

  • Authorization: Bearer local-dev-token for local development, OR
  • Cf-Access-Authenticated-User-Email when the app is placed behind Cloudflare Tunnel + Cloudflare Access.

Do not bind the server to 0.0.0.0 for normal use. Browser terminal control is local shell access and must remain behind loopback plus an authenticated tunnel.

License

MIT