Zeptobeam banner
qhkm qhkm

Zeptobeam

Development community

Description

Orchestration layer for ZeptoClaw. Fault-tolerant multi-agent runtime inspired by OpenAI Symphony and Erlang/BEAM.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

**This repo is an experiment.** We forked [ErlangRT](https://github.com/kvakvs/ErlangRT) and extended it toward AI agent orchestration — sync scheduler, reduction counting, supervision trees, ETS/DETS, hot code upgrades. It got to 343 tests and then hit a wall: the sync scheduler can't `await`, so every LLM call required two thread hops and correlation IDs. Reduction counting models the wrong resource — AI agents don't consume CPU, they consume tokens and dollars. The learnings shaped [ZeptoRT](https://github.com/qhkm/zeptort), which fixes both problems. Active development is there.


ZeptoBeam

**BEAM-inspired multi-agent runtime in Rust. Fault-tolerant, message-driven, production-ready.**

[![Rust](https://img.shields.io/badge/rust-nightly-orange.svg)](https://rust-lang.github.io/rustup/concepts/channels.html) [![Tests](https://img.shields.io/badge/tests-343%20passing-brightgreen.svg)](#) [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)


What

ZeptoBeam is the orchestration runtime for [ZeptoClaw](https://github.com/qhkm/zeptoclaw) — a multi-agent AI system where autonomous agents collaborate on complex tasks.

Built on Erlang/BEAM principles, it handles the hard parts of running many agents at once:

  • Process isolation — Each agent has its own mailbox, state, and lifecycle
  • Fault tolerance — Crashed agents restart automatically via supervision trees
  • Message passing — Agents communicate via async messages, no shared state
  • Preemptive scheduling — Reduction-based preemption with 3-tier priority queues
  • Durable state — Checkpoints to SQLite, WAL-backed durable mailboxes
  • Hot code upgrades — Swap agent behaviors at runtime without restart
  • MCP integration — Expose runtime as MCP server, consume external MCP tools
  • Advanced orchestration — DAG dependencies, retry policies, resource budgets, approval gates

The Problem

AI agents fail. They hallucinate