Void-Box Update Adds Sandboxed OpenClaw-Telegram Integration via KVM Micro-VMs

What Void-Box Is

Void-Box is a capability-bound runtime for AI agents that combines agent skills with isolation. The core concept is: VoidBox = Agent(Skills) + Isolation. Skills are declared capabilities that only exist when bound to an isolated execution boundary.

Key Technical Approach

Instead of running agents in shared processes or containers, each execution stage runs inside its own KVM micro-VM. These micro-VMs are created on demand and destroyed after execution, providing explicit capability boundaries with no container runtime required.

New Update Details

The latest update adds a working example that runs OpenClaw connected to Telegram - fully sandboxed inside Void-Box. In this example, the workflow runs as a service (daemon mode) inside an isolated micro-VM.

The flow is:

• Telegram receives a message
• OpenClaw processes it inside the sandbox
• Execution happens within an isolated KVM micro-VM

Each interaction remains isolated within the VM boundary, with no leftover state, no side effects that leak between runs, and no shared filesystem mess.

Platform Support and Status

Currently supports Linux (KVM) and macOS. The project is still early, but the core pipeline and sandbox are functional.

Demo and Resources

A short video shows:

• The declarative workflow (YAML)
• The service booting inside a micro-VM
• Telegram receiving the response

Repository: https://github.com/the-void-ia/void-box