Open source agent runtime

Eva-CLI

A controlled runtime for multi-Agent automation

Eva-CLI uses Rust for reliable runtime boundaries and Lua for hot-reloadable Agent behavior, then connects external Agents, MCP servers, skills, memory, knowledge bases, and hardware through a unified Topic EventBus.

Rust runtime boundary Lua hot reload Topic EventBus

Development progress

From architecture scaffold to release evidence, operator safety, and closure gates

Remaining work
Current stage

V1.17.6 V1.x closure release gate is in place

The repository keeps the V1.11.5-alpha source version while documenting and gating the completed V1.12 to V1.17 runtime evidence line: daemon control and recovery, provider supervision gates, restore mutation and rollback evidence, service-manager abstraction, hardware safety gates, memory retrieval and redaction, observability retention policy, run command split, operator execution fields, high-risk text summaries, public JSON contract diff validation, and the V1.x closure report.

  1. Done
    Architecture, module partitioning, and configuration

    System boundaries, runtime model, adapters, memory, discovery, hardware, recovery, website, docs, configuration, and module partitioning are in place.

  2. Done
    Runnable V1.0 runtime and task diagnostics

    The in-memory basic loop, CLI quickstart, local task status/log/cancel diagnostics, and core CI checks are implemented.

  3. Done
    V1.1 to V1.5.1 controlled capability, release gates, and GHCR delivery

    External capability diagnostics, memory context, hardware plans, backup/lifecycle checks, release hardening commands, the source user manual, and GitHub Packages container delivery are implemented.

  4. Now
    V1.17.6 V1.x closure release gate

    The V1.12 daemon, V1.13 provider, V1.14 restore/service-manager, V1.15 hardware and memory, V1.16 observability, and V1.17 CLI/operator contract evidence lines are summarized by the closure gate and synchronized across website, docs, release notes, and i18n manifest.

  5. Later
    Signed installers, provenance, and real apply paths

    Future releases add provider process execution, durable stores, destructive apply gates, signed installers, OS packages, and provenance bundles.

Next implementation work
  • Resolve production signing, attestation, OS package publication, and release upload blockers when credentials and repository permissions exist.
  • Attach platform service-manager test environments, real hardware fixtures, and production database sink evidence before claiming production readiness.
  • Keep high-risk restore, upgrade, hardware, and lifecycle paths behind explicit evidence, confirmation gates, and stable JSON contracts.

Architecture

From runtime boundary to controlled capabilities

Eva-CLI architecture diagram

Docs

Read by usage and architecture topic

Discussion

Discuss Eva-CLI

Ask questions, share implementation ideas, or leave design feedback through GitHub Discussions.