Hardwire 0.5.0: make software understandable to AI agents

Hardwire 0.5.0: make software understandable to AI agents

Hardwire is an open source toolkit that helps developers describe application
actions and check their inputs, declared effects and approval requirements
before connecting those actions to an AI agent.

Why

An agent integration needs more than a button label. Developers need a clear
description of what an action expects, what it changes and which approvals
apply. Hardwire makes those declarations explicit and provides tools to check
them before connecting them to application code.

What

This first public release includes a Node.js library, command line tools and a
local MCP server. Its five tools infer draft action descriptions from supplied
HTML, inspect contracts, validate arguments, generate MCP tool descriptions and
check trace consistency.

It is for developers and experimenters building agent integrations. You do not
need an app, hosted service or API key to try Hardwire. The code is MIT licensed.

How

Supply saved HTML or a JSON action description, review the draft and its declared
rules, then validate example arguments. You get a contract you can inspect and
test. Connecting it to a real service still requires a trusted application handler
with authorization and approval enforcement.

Use Node 22+ (24 recommended). To try this exact release:

git clone --branch v0.5.0 --depth 1 https://github.com/Automatron-workflows/hardwire.git
cd hardwire
npm ci --ignore-scripts
npm run test:mcp
npm run --silent mcp:config

Merge the generated entry into your local MCP client's configuration. Follow
the setup guide
for a first prompt and troubleshooting. No application ownership is needed.

Alternatively, download hardwire-0.5.0.tgz and SHA256SUMS from this release.
Verify with shasum -a 256 -c SHA256SUMS (macOS) or
sha256sum --check SHA256SUMS (Linux), then install it in a separate project:

npm install /absolute/path/to/hardwire-0.5.0.tgz --ignore-scripts
node node_modules/hardwire/scripts/client-config.mjs

The tarball is distributed through GitHub; no npm package or MCP Registry listing
is published. Do not use npm install hardwire to obtain this project.

Checks exercise an official MCP client, all handlers, rejected inputs, a tampered
trace, and the command from a clean package install. Existing unit/CLI and real
HTTP integration suites also run in CI on Node 22 and 24. The release workflow
downloads the uploaded artifact, verifies its checksum and repeats the installed
MCP check before the draft is published.

This is experimental inspection tooling. It does not browse sites, authenticate,
execute submitted ports or certify inferred effects. Trace digests are consistency
checks, not signatures or proof of execution. Existing 0.4.x panel/trace formats
are unchanged.