Developer ✓ Verified

Deterministic multi-agent dev pipeline with Lobster workflows

By Ggondim

Published 2026-03-11

A developer built a deterministic multi-agent dev pipeline inside OpenClaw using Lobster workflows. Three isolated agents work with YAML-driven orchestration, not LLM-decided flow.

What the Pipeline Does

Programmer: writes code from specs
Reviewer: checks quality (max 3 iterations)
Tester: validates output
Parallel: 4 projects x 3 roles = 12 concurrent sessions
Validation: LLM output checked against JSON schemas before next step

How He Built It

Each agent gets own tools, memory, identity, workspace. Communication via Telegram. YAML controls state machine. After evaluating Copilot sessions, Protoagent, and Ralph, chose Lobster but needed loops. Contributed Sub-lobsters nested workflow feature (PR #20). Published on dev.to.

Results: Up to 12 concurrent sessions. Contributed Sub-lobsters (PR #20) to OpenClaw/Lobster.

View Original Source → ← All Developer Use Cases

Frequently Asked Questions

Yes. Using Lobster workflows, three isolated agents (programmer, reviewer, tester) run with YAML-driven orchestration instead of letting an LLM decide the flow.

The programmer writes code, the reviewer checks it (max 3 iterations), and the tester validates. LLM output is validated against JSON schemas before triggering the next step.

Yes. The setup supports 4 projects x 3 roles = up to 12 concurrent agent sessions, each with their own tools, memory, and workspace.

What the Pipeline Does

How He Built It

More Developer Use Cases

Frequently Asked Questions

Start automating your developer workflows today

OpenClaw Communityfor Founders.

OpenClaw Community
for Founders.