qhkm

Zeptopm — AI skill for Claude Code

AI community

⚡ Process Manager for AI agents — like PM2, but for LLMs.

How to install Zeptopm

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

What Zeptopm does

⚡ Process Manager for AI agents — like PM2, but for LLMs. Erlang-inspired process supervision, real-time agent channels, orchestrated multi-agent runs. Single binary, ~7 MB per agent.

Alternatives in AI

  • AI Engineering Hub — In-depth tutorials on LLMs, RAGs and real-world AI agent applications 37.2k ★
  • Repomix — 📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file 22.7k ★
  • Manifest — Real-time cost observability for OpenClaw agents — track tokens, costs, messages, and model usage 4.1k ★

README

⚡ ZeptoPM

**Process Manager for AI agents — like PM2, but for LLMs.**

[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE) [![Rust](https://img.shields.io/badge/Rust-1.85+-orange.svg)](https://www.rust-lang.org/) [![macOS](https://img.shields.io/badge/macOS-supported-brightgreen.svg)]() [![Linux](https://img.shields.io/badge/Linux-supported-brightgreen.svg)]()

**`~7 MB per agent`** · **`11 MB binary`** · **`near-zero idle CPU`** · **`500+ agents on 4 GB RAM`**

[Quick Start](#-quick-start) · [Features](#-features) · [Channels](#-agent-channels) · [HTTP API](#-http-api) · [Config](#-config-reference)


📖 The Story

We built [ZeptoClaw](https://github.com/qhkm/zeptoclaw) — an AI agent library in Rust with tool use, multi-provider support, and session management. A single ZeptoClaw agent can spawn sub-agents, delegate tasks, even run agents in parallel. It works great — but everything runs in one process. One agent leaks memory, the whole thing goes down. One agent panics, every agent dies with it.

Then OpenAI launched [Symphony](https://github.com/openai/symphony) — built on Elixir and the BEAM VM. Their insight: turn work into **isolated, autonomous runs** where agents operate independently. The BEAM has been doing this for decades in telecom — thousands of isolated processes, each with its own memory, supervised by a parent that restarts them on failure.

That was the spark. We applied the same model to AI agents:

🔸 Each ZeptoClaw agent runs as a **separate OS process** — isolated memory, isolated state, independent crash domains.

🔸 A **daemon supervisor** watches them all. If one crashes, only that agent restarts. Others keep running.

🔸 **Message passing** between agents goes through the daemon over JSON lines — never shared memory — just like the BEAM's actor model.

Symphony manages work at a high level. ZeptoPM manages the agents doing the work — process lifecycle, c