Back to corpus
research noteexperiment writeup candidatescore 40

Agent Swarm

> Autonomous multi-agent task orchestration daemon — ingest work from GitHub, Linear, or internal queues and dispatch to Claude, Codex, or Gemini agents with workspace isolation, state machine tracking, and full audit trails.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> Autonomous multi-agent task orchestration daemon — ingest work from GitHub, Linear, or internal queues and dispatch to Claude, Codex, or Gemini agents with workspace isolation, state machine tracking, and full audit trails. - [Overview](#overview) - [Architecture](#architecture) - [Packages](#packages) - [Data Flow](#data-flow) - [Setup](#setup) - [Configuration](#configuration) - [Usage](#usage) - [API Reference](#api-reference) - [Workflows](#workflows) - [Database Schema](#database-schema) - [Development](#development) Agent Swarm sits between your work item sources (GitHub Issues, Linear tickets, internal queues) and AI agents (Claude Code, Codex, Gemini CLI). It fully automates the loop: 1. **Ingest** — Poll or receive webhooks from GitHub / Linear / machine queue 2. **Dispatch** — Select the best available agent (by label hints, load, or metadata) 3. **Execute** — Isolate each task in its own workspace (git clone), render a Liquid prompt, run the agent subprocess 4. **Track** — Persist every state transition to Supabase for full audit trails 5. **Notify** — Post Discord messages + update source status (GitHub labels, Linear status) on completion **Tech stack:** Bun + TypeScript monorepo (10 workspace packages), Supabase for state, Prometheus for metrics, NUMU Bus for cross-system events.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.