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

✍️ OpenClawRadar📅 Published: April 17, 2026🔗 Source
Void-Box Update Adds Sandboxed OpenClaw-Telegram Integration via KVM Micro-VMs
Ad

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.

Ad

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

📖 Read the full source: r/LocalLLaMA

Ad

👀 See Also

ScreenMind: Local-First AI Memory That Indexes Your Entire Computer Activity
Tools

ScreenMind: Local-First AI Memory That Indexes Your Entire Computer Activity

ScreenMind captures your screen, meetings, and voice notes using Gemma 4 E2B locally via llama.cpp. Runs on 4GB+ VRAM with Q4 quantization. Search past activity, chat with history, and connect to Claude/Cursor via MCP.

OpenClawRadar
Local MCP Memory System with Consolidation for AI Conversations
Tools

Local MCP Memory System with Consolidation for AI Conversations

A developer built an MCP server that provides persistent local memory for AI clients, using Qwen 2.5-7B to consolidate conversations into structured knowledge documents every 6 hours. The system runs entirely on your hardware with semantic dedup, adaptive scoring, and FAISS vector search.

OpenClawRadar
Open-source MCP server adds built-in session memory for Claude Desktop
Tools

Open-source MCP server adds built-in session memory for Claude Desktop

A developer built a TypeScript MCP server with integrated session memory to preserve context between Claude Desktop coding sessions, eliminating the need for separate memory infrastructure. The server includes session save/load functions and additional tools like Brave Search and Google Gemini integration.

OpenClawRadar
Replacing complex retrieval pipelines with simple git shell commands for LLM agents
Tools

Replacing complex retrieval pipelines with simple git shell commands for LLM agents

A developer replaced their entire AI agent retrieval pipeline (sentence-transformers, rank-bm25, two-pass LLM pipeline) with a single tool that lets the agent execute read-only shell commands against a git repository, reducing Docker image size by ~3GB and eliminating timeout issues.

OpenClawRadar