Person flying with jetpack - representing accelerated development
Decentralized Swarm Orchestration

As promised.

Jetpack is a decentralized multi-agent swarm that coordinates AI agents to build software together—autonomously, safely, at scale. Agents coordinate through data, not control flows.

Made for modern product teams

What is Jetpack?

Jetpack is a decentralized multi-agent swarm orchestration system that coordinates AI agents to work together on large-scale software development.

Built as an 8-package monorepo with a durable Turso cloud database, Jetpack uses advisory file reservations, graph-based task prioritization, and 3-layer semantic memory—creating a crash-resilient environment where agents autonomously claim tasks, share knowledge, and build software at scale.

Model-Agnostic
Any LLM
Concurrent
Unlimited Agents
Advisory
Smart Reservations
Architecture

Monorepo Architecture

Jetpack is built as an 8-package monorepo with a durable DataLayer, decentralized SwarmCoordinator, and model-agnostic agent execution.

Component Overview

ComponentPurposeStorage
DataLayerDurable persistence interface (Turso/SQLite)Turso cloud / .jetpack/jetpack.db
Task QueueHierarchical task queue with dependency trackingDataLayer
Agent MailAdvisory reservations, threading & intent broadcastingDataLayer
Memory System3-layer semantic memory (Episodic, Working, Procedural)DataLayer
SwarmCoordinatorAgent lifecycle, work distribution & claim strategiesIn-memory
AgentHarnessModel-agnostic agent execution wrapperIn-memory
Features

Key Features

Everything you need to orchestrate a swarm of AI agents for software development at scale.

Swarm Intelligence

5 claim strategies including graph-prioritized with critical path analysis

  • Skill-based task assignment with best-fit (default), round-robin, and load-balanced strategies
  • TaskGraph analysis: critical path, fan-out (dependent count), and depth scoring
  • Intent broadcasting — agents announce files they'll touch before starting

Durable State

Turso cloud database as the single source of truth

  • 3-layer memory system: Episodic (permanent), Working (TTL), Procedural (learned patterns)
  • Agents coordinate through data, not control flows — crash-resilient by design
  • Embedded replicas with offline sync and vector search

Safe Coordination

Advisory file reservations — conflicts are data, not errors

  • Multiple agents can reserve the same file; conflicts surface as information
  • Task dependency DAG ensures correct execution order
  • Pre-commit Git hook enforcement via jetpack hook install

Visual Oversight

Real-time dashboard with task graph and agent monitoring

  • Kanban board with drag-and-drop task management
  • Agent health monitoring with heartbeat tracking
  • Quality metrics and regression detection

Model-Agnostic Agents

AgentHarness wraps any LLM — Claude Code, Codex, or custom models

  • Skill-based registration and matching (typescript, react, testing, etc.)
  • Session isolation via session_id for clean agent lifecycle
  • Automatic recovery of stuck tasks from stale agents

Interactive Demos

See It In Action

Explore how Jetpack's core systems work together — from task orchestration to agent coordination and semantic memory.

Layered orchestration
for autonomous coding agents.

A unified architecture coordinating multiple AI agents through task queues, messaging, and semantic memory—enabling long-horizon tasks without losing context.

Task Queue

Persistent structured tasks.

Hierarchical task queue with dependency tracking. TaskGraph provides critical path, fan-out, and depth analysis for smart prioritization.

Agent Mail — Coordination

Coordination layer.

Advisory file reservations, message threading, and intent broadcasting. Agents coordinate through data — conflicts are information, not errors.

Memory System

Vector-backed semantic memory.

Vector embeddings for semantic search. Agents retrieve relevant context from past work without losing institutional knowledge.

SwarmCoordinator — Workers

Parallel execution.

1-N worker agents via model-agnostic AgentHarness. Each claims tasks atomically, executes independently, and reports back through Agent Mail.

[TASK QUEUE]

Persistent Task Queue

_

tasks.list()
3/11 complete
bd-a3f8Auth System
in-progress
bd-a3f8.1JWT Setup
completed
bd-a3f8.1.1Token Generation
completed
bd-a3f8.1.2Validation Logic
completed
bd-a3f8.2OAuth Flow
in-progress
bd-a3f8.2.1Google Auth
claimed
bd-a3f8.2.1.1Callback Handler
ready
bd-a3f8.2.1.2Profile Sync
pending
bd-a3f8.3Session Management
pending
bd-a3f8.3.1Redis Store
pending
bd-a3f8.3.2Expiry Logic
pending
$ready
HIERARCHICAL ID STRUCTURE
bd-a3f8Epic
bd-a3f8.1Task
bd-a3f8.1.1Sub-task
bd-a3f8.1.1.1Leaf
01 / STRUCTURE

Hierarchical task trees with parent-child relationships and dependency tracking.

02 / ATOMIC

Race-free task claiming ensures no duplicate work across parallel agents.

03 / PERSISTENT

Tasks survive restarts—agents resume exactly where they left off.

[AGENT MAIL]LIVE

Coordination Layer for Coding Agents

_

AA
Agent Alpha
agent-alpha
AB
Agent Beta
TypeScript migration blocked
2m ago
To: Agent Alpha (agent-alpha)
Advisory Reservations
src/utils/parser.jsRESERVED
src/config/index.jsRESERVED
I've hit a blocker on the TypeScript migration. Files src/utils/parser.js and src/config/index.js need coordination. I'm announcing intent on both files to surface conflicts. Can you review the types I've defined before I proceed? Estimated completion: 2 hours
Reply to Agent Beta...
ACTIVE AGENTS
4
MESSAGES TODAY
47
ACTIVE RESERVATIONS
8
AVG RESPONSE
12m
[MEMORY]

Memory System

_

<episodic:preferences/>
<working:project_ctx/>
<procedural:patterns/>
<episodic:decisions/>
<working:semantic/>
<episodic:task_history/>
<procedural:styles/>
<working:domain_knowledge/>
dimensions: 1536embeddings: 8similarity: cosine
01 / EPISODIC

Past decisions and task history stored as high-dimensional vectors in the memories table.

02 / WORKING

Active project context and semantic knowledge clustered for fast retrieval.

03 / PROCEDURAL

Learned code patterns and styles—agents query by meaning, not keywords.

[SWARM COORDINATOR]

Autonomous Task Worker (AgentHarness)

_

AGENT STATUS
heartbeat #0
1. idle
2. looking
3. claiming
4. retrieving
5. executing
6. storing
7. publishing
8. complete
SKILLS
typescriptreactdatabasetestingdevopspython
TASK QUEUE
<refactor_auth_module/>
typescript
<add_user_dashboard/>
react
<optimize_db_queries/>
database
<write_api_tests/>
testing
<setup_ci_pipeline/>
devops
AGENT HARNESS (ANY LLM)
status:awaiting work
01 / START

SwarmCoordinator subscribes to Agent Mail, starts heartbeat every 30s, begins work loop.

02 / CLAIM

Get ready tasks, filter by skills, sort by priority, claim highest match.

03 / EXECUTE

Retrieve memory context, spawn AgentHarness with any LLM, capture output.

04 / COMPLETE

Store learnings in Memory System, publish completion via Agent Mail.

Getting Started

Quick Start

Get up and running in under 5 minutes.

1
Clone & Install
git clone https://github.com/agent-jetpack/jetpack-cloud.git && cd jetpack-cloud && pnpm install && pnpm build
2
Initialize
cd /your/project && jetpack init
3
Start
jetpack start

What happens next:

1SwarmCoordinator starts
2AI Agents spawn
3Web UI opens at :3000
4Load plans via jetpack load
View Full Documentation

CLI reference, code examples, use cases, and API documentation

Roadmap

What's Next

The future accelerates. Here's what we're building.

Completed

Phase 0: Foundation

14 critical bug fixes — session isolation, leaf-only claiming, recovery, PID tracking

Phase 1: Agent Mail Core

Advisory file reservations, message threading, intent broadcasting, stale cleanup

Phase 2: Smart Coordination

TaskGraph with critical path, fan-out (dependent count), depth scoring, graph-prioritized strategy

Upcoming

In Progress

Procedural Learning

Pattern extraction from completed tasks — learned approaches for recurring problems

In Progress

Conflict Injection

Inject file reservation conflicts into agent prompts for smarter coordination

Planned

Plan-Level File Annotations

Parse Files: section in markdown plans for pre-computed file reservations

Planned

Batch Scheduling

Atomic batch execution for related tasks from the Agent Flywheel (UBS)

Planned

WebSocket Dashboard

Real-time push updates to the web dashboard via WebSocket connections

Future

Cloud Agent Farm

Cloud-hosted agent infrastructure for scalable distributed workloads

Future

Issue Tracking Integration

GitHub Issues and Linear integration for seamless workflow

Future

Agent Leaderboards

Performance metrics and competitive agent rankings

Have a feature request?

Open an issue on GitHub

Acknowledgments

Built on Giants

This project integrates and builds upon amazing open-source work.

Jeffrey Emanuel

Creator of the Agentic Coding Tooling Flywheel ecosystem—a comprehensive suite of tools for multi-agent software development.

Flywheel Components:

Claude Code Agent FarmUltimate MCP ClientAgent MailMemory SystemTask Queue ViewerNamed Tmux ManagerSimultaneous Launch ButtonUltimate Bug ScannerCoding Agent Session Search

Steve Yegge

Creator of Beads—a git-backed task management system with dependency tracking and hash-based IDs for conflict-free merging. The foundation of Jetpack's task system.

Key Features:

Git-backed StorageTask DependenciesHash-based IDsConflict-free Merging

Turso

Cloud-native libSQL database powering Jetpack's durable DataLayer. Enables embedded replicas, offline sync, and vector search for crash-resilient agent coordination.

Key Features:

Embedded ReplicasVector SearchOffline SyncCloud-Native