EnvarLive

An operator-hosted Live interface for an existing Agent: text, voice, avatars, explicitly supplied images, native task progress, tool approvals and protected files. Envar opens the interface only for the Agent owner. Model, avatar and wallet secrets stay in the operator's environment.

Requires Python 3.11+ and Node.js 24+ on Linux/macOS. Select an existing reviewed Hermes installation or an authenticated OpenClaw Gateway; no model/provider fallback or automatic package installer is embedded in the SDK.

uv tool install 'envarlive==0.1.0a11'
envarlive init --runtime hermes --directory ./agent-live
envarlive doctor --config ./agent-live/live.toml
envarlive serve --config ./agent-live/live.toml

The published Python wheel includes viewer assets; no npm or build step is needed after installation. doctor checks Node/SQLite without inference. This is an alpha release. CI candidates, production-site checks and physical microphone/avatar acceptance have separate evidence; installing the package does not establish a production SLA for the operator's runtime or HTTPS origin.

Review the profile and use a dedicated HTTPS origin. On your Envar Agent, add its private Live /mcp entry, apply the exact ownership challenge with envarlive connect, restart and verify. The stdio host plugin forwards to that same service and does not start another Agent.

Stable request IDs and private journals prevent restart from creating another task. Uncertain operations retain their native identity and block replacement work until inspected. Image bytes and provider/service tokens are excluded from SDK journals. Avatar starts have a persistent rolling limit; normal close/timeout share one stop.

The executor must have a separate OS/container identity from an EnvarPay signer and must never receive wallet key mounts. The OpenClaw HTTP connector reports final text/run states. Opt-in native Gateway mode adds tool events, confirmed cancellation and bounded task-owned file delivery when an operator-configured shared output directory exists. Remote Gateways can expose only their managed transcript artifacts. OpenClaw execution approvals stay in its native operator surface by default; the optional scoped Gateway plugin supports Allow once and Deny for the paired EnvarLive device's own Run. See the native OpenClaw guide. Task escrow belongs to EnvarPay and remains a separate testnet-only feature.

For payments, install EnvarPay as a separate Python wallet/MCP service. JavaScript and TypeScript Agents use @envarai/envarpay to call that service; the client holds no signing key. Native hosts connect through MCP, and other languages can use the documented MCP HTTP interface. EnvarLive supplies the interactive interface; it never signs payments.

Source and full setup · Operator deployment and recovery