Stable ยท October 24, 2026

Agent 0.1.26

One Agent for local IPC and cloud MCP on Windows x64, macOS Apple Silicon, Linux x64 and Linux ARM64.

Install

Run this on the device you want to register, then follow browser verification:

npx --yes @browzwork/agent@0.1.26

The npm package installs the matching Native Agent and Supervisor. The standalone Native downloads below are intended for managed deployments.

What changed

Upgrade an existing device

In Portal โ†’ Devices, compare the reported Agent version and use the approved signed upgrade when a newer version is available. Upgrades are manual; automatic upgrades remain off.

Devices that only trust the earlier Release key need their Owner to approve the additional signing public key locally before accepting this signer. Publishing a release does not silently replace a device trust root.

Downloads and SHA-256

These are the same four Native files pinned by the signed stable manifest. Verify the signature with the public keys pinned by your trusted installation; this page is not a substitute for signature verification.

PlatformDownloadSHA-256
win32-x64Download Native Agentc6e16c1dea1c4459193ab52f2876f64055cfd478c9c4dde157dcdd5fdce4f94c
darwin-arm64Download Native Agent8a35fe2a4a51fa69a4a88f420a4abea6da77e4ee141b6ae49a09481b36f80400
linux-x64Download Native Agente6e828d10cbfdd2c010211fbe2c1996f3b9c90ffd37f203beb02b9dc56fde67b
linux-arm64Download Native Agentc8d418284bfc83003cc1ba8eac33891accaed2421ab76a5453ecd78908bbc4ba

Validation

All four target platforms passed Native library regression and actual TLS/WSS tests with 7,000-byte UTF-8 output and a single side effect when the same request is retried. Windows also passed ten actual IPC technical scenarios. Signing, Supervisor and rollback regression passed; this release has not yet been installed on all production devices. Forty coding and technical scenario runs covered local IPC, an isolated authenticated Gateway/Native TLS-WSS channel, RDC local and RDC hosted remote with shared fixtures and verified file effects.

These scenarios do not establish full feature equivalence with RDC or identical fault-injection coverage. Client-specific integrations and separately marked preview plugins retain their own validation status.