Skip to content

Agent Workbench 0.3.0

Choose a tag to compare

@bcherrington bcherrington released this 30 Jun 20:29
1916d2b

Spec 033 (cross-platform packaging). Agent Workbench ships as a normal npm package distributed through GitHub Releases (not the npm registry). Plugins register clone-free from the installed package — no repo clone, no --plugin-dir.

Install (Windows / macOS / Linux)

Prerequisites

  • Node.js 22 recommended (Node 24 needs a C++20 toolchain for the native build).
  • Python 3 + a C/C++ toolchain to compile native modules (Windows: VS Build Tools "Desktop development with C++"; macOS: xcode-select --install; Linux: build-essential).

1. Install the runtime (builds native modules + records the runtime pointer):

npm install -g https://github.com/Auriora/agent-workbench/releases/download/v0.3.0/auriora-agent-workbench-0.3.0.tgz

2a. Register the Claude Code plugin:

PKG="$(npm root -g)/@auriora/agent-workbench"          # PowerShell: $pkg = "$(npm root -g)\@auriora\agent-workbench"
claude plugin marketplace add "$PKG/plugins/agent-workbench"
claude plugin install agent-workbench@agent-workbench-local --scope user
claude plugin list   # -> agent-workbench@agent-workbench-local  v0.3.0  enabled

2b. Register the Codex plugin:

codex plugin marketplace add "$PKG/plugins/agent-workbench"
codex plugin add agent-workbench@agent-workbench-local

Restart the editor so the skill, hooks, and MCP server are discovered. Full guide: docs/runbooks/install-agent-workbench.md.

What's new in 0.3.0

  • Normal npm package model. Removed the copy-to-prefix installer and archive install.sh/install.ps1; npm install builds natives in place and a postinstall pointer drives the in-place node shim launch.
  • Clone-free plugin registration, verified end-to-end from the packed tarball for Claude and Codex (package-scoped agent-workbench-local marketplaces).
  • CI green on ubuntu, macOS, and windows-2022 — native build + MCP initialize launch + hook smokes on all three.
  • Distributed via GitHub Releases; not published to the npm registry.

Known gaps

  • Kiro launcher not yet wired to the shim (docs/backlog/033-kiro-shell-free-launcher.md).
  • windows-latest (VS 18) not yet supported by node-gyp; CI pins windows-2022.