Skip to content

Hardwire 0.6.0: try the toolkit in your browser

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Nov 09:20
086cdb3

Hardwire 0.6.0: try the toolkit in your browser

Hardwire helps developers describe application actions and check their inputs,
declared effects and approval requirements before connecting them to an AI agent.

Open the playground.
No app, account, installation or API key is needed.

Try it

  1. Search for a lamp in the sample shop.
  2. Let Hardwire turn the form into an action contract.
  3. Call the fixed demo search directly. Try the wrong input to see it rejected.
  4. Download the inferred contract.

The demo uses the same inference and validation code as the CLI and MCP server.
Inputs remain in the tab. The only executable handler searches fixed fake data;
it cannot call arbitrary endpoints or perform writes.

What changed

Version 0.6.0 adds the public playground, a portable hardwire/browser entry point,
async Web Crypto hashing, a reproducible static build and GitHub Pages deployment.
The synchronous Node API, panel format and trace format remain compatible.
The local demo also serves the playground at /playground/.

Read the architecture
for module responsibilities, runtime boundaries and deployment details.

Install the versioned source

Use Node 22 or newer:

git clone --branch v0.6.0 --depth 1 https://github.com/Automatron-workflows/hardwire.git
cd hardwire
npm ci --ignore-scripts
npm run demo

Open http://127.0.0.1:8787/playground/. To connect an MCP client, run
npm run --silent mcp:config and follow the setup guide.

The release also includes hardwire-0.6.0.tgz and SHA256SUMS. Download both,
check the checksum and install the local tarball:

shasum -a 256 -c SHA256SUMS
npm install ./hardwire-0.6.0.tgz

MIT licensed. Hardwire is not published on npm and its package identity has not
been reserved. Do not use npm install hardwire to obtain this project.

Scope

This remains an experimental toolkit. It validates descriptions and arguments;
it does not log in, execute submitted ports or prove that an endpoint behaves
safely. The benchmark still contains three synthetic fixtures. General execution
and real website inference accuracy remain open work.