Join waitlistJoin
How it worksResearchDocsAdoptersPricingContactJoin waitlist
Back to agent research
Installer proof / May 19, 2026

A fresh install wrapped four agent runtimes with one CLI path.

Runtime parity proves the boundary can hold across frameworks. This follow-up proves the integration path is usable from a clean workspace: install the CLI, initialize OpenClaw, Hermes, MCP, or a custom HTTP agent, connect to the runtime, and run a local proof without special repository state.

Agent boundary research sequence

Eight chapters. One continuous agent-control story.

The path moves from the first OpenClaw payment block, to adversarial replay, late-stage drift, native tool-body proof, second-runtime model turns through Hermes, Hermes parity, a four-runtime parity proof, and finally a clean-install CLI path for those adapters.

01Baseline proof before bodyA model-selected payment.transfer call was stopped before the tool function ran.May 902Adversarial replay under loadSeven attack patterns replayed as 700 concurrent attempts with zero body calls.May 1303Late-drift deep dive at turn eightThe bad action appeared after safe-looking context and was still blocked at execution.May 1404Native tool proof three bodies blockedDeploy, export, and payment tools were invoked natively and blocked before body entry.May 1405Hermes proof second runtimeHermes model turns through OpenAI, Gemini, and DeepSeek were blocked before body entry.May 1606Hermes native tools parity proofHermes native tools, replay, mutation, action matrix, and model-turn checks now match the OpenClaw evidence depth.May 1607Joint runtime proof one policyOpenClaw, Hermes, MCP, and Generic HTTP shared one constitution across 100-way mixed concurrency, delegation, halt, and fail-closed preflight.May 1908Clean install path four init commandsA fresh npm workspace installed the CLI, initialized four adapters, and re-ran the shared proof with zero prohibited body calls.May 19
Why this matters

A runtime adapter is only useful if a customer can reproduce it outside the lab. This run starts from a clean npm workspace and exercises the exact operator path we want: initialize the runtime, write the config, connect to the agent, and run a local proof. The same command shape now covers OpenClaw, Hermes, MCP tool hosts, and custom HTTP agents.

Clean install run

The install path generated adapters and ran proof from a fresh folder.

The verifier used the packed CLI artifact instead of the repository source tree. It then created local bridge processes for all four runtime families and ran installed imladri agent init plus imladri agent verify.

StepResult
PackagePacked the local Imladri CLI and installed it into a fresh npm workspace.
OpenClawGenerated config, connected to the local bridge, and detected 37 actions through the adapter contract.
HermesGenerated config, connected to the local bridge, and detected native Hermes actions.
MCPGenerated config for an MCP tool host and verified JSON-RPC-style tool discovery through the adapter.
Generic HTTPGenerated config for a custom HTTP agent endpoint and verified the same adapter shape.
ProofRan installed imladri agent verify with 100 samples and 100-way concurrency.
Operator path

Four runtimes, one command shape.

The runtime name changes, but the product path stays the same: initialize the adapter, provide an endpoint, verify the response, publish policy, wrap actions, and export evidence.

RuntimeInit command
OpenClawimladri agent init --runtime openclaw
Hermesimladri agent init --runtime hermes
MCPimladri agent init --runtime mcp
Customimladri agent init --runtime custom
Proof checks

The installed CLI re-ran the shared runtime proof.

The installed package ran the embedded parity verifier, not a static screenshot. The important checks are the same ones a customer would care about before trusting a wrapper path.

CheckOutcome
Allowed bodiesOpenClaw, Hermes, MCP, and Generic HTTP each ran safe actions.
Denied bodiesAll four runtimes denied prohibited actions before body entry.
Mixed concurrency100/100 mixed-runtime prohibited attempts blocked.
DelegationDelegated dangerous actions blocked at the receiving runtime boundary.
Shared haltOne halted preflight boundary stopped every runtime before body entry.
Fail closedStrict preflight transport failure denied every runtime.
EvidenceAll runtime events shared the required normalized proof schema.
Artifact

The public artifact is sanitized for publication.

The JSON includes pass/fail steps, detected action counts, runtime list, verifier output, and the high-level result. Local machine paths and temporary workspace paths are intentionally omitted.

Clean-install artifact: agent-runtime-clean-install-20260519.json

Scope

This proves installability and adapter consistency.

This is not a claim that every unwrapped plugin is protected automatically. The claim is narrower and more useful: the same Imladri adapter contract can be generated, connected, tested, and verified from a fresh install across four runtime families.