---
id: "claim-queues-over-loops"
type: "claim"
source_timestamps: ["00:32:59", "00:36:29"]
tags: ["system-architecture", "reliability"]
related: ["concept-agentic-queues", "contrarian-queues-not-loops", "entity-ralph", "action-implement-agent-queues"]
confidence: "high"
testable: true
speakers: ["Matt Pocock"]
---
# Queues are Superior to Agent Loops

## Claim

Building autonomous agents using infinite while loops is a flawed architecture that leads to non-deterministic failures. Structuring agent work as a queue of discrete, scoped tasks — like a human Kanban board — is vastly superior for reliability, parallelization, and debugging.

See [[concept-agentic-queues]] and [[contrarian-queues-not-loops]]. The loop-based example Pocock critiques is [[entity-ralph]].

## Confidence

**High** for software engineering workflows. The position is reinforced by decades of distributed systems practice: message queues, worker pools, idempotent jobs, CI/CD pipelines, Kubernetes Jobs, Argo, Airflow.

## Testability

**Testable.** Compare a loop-based agent (Auto-GPT-style) against a queue-based agent on the same backlog of engineering tasks. Measure: task completion rate, cost per task, mean time to debug a failure, ability to parallelize.

## Where loops still matter

Research settings and long-horizon agents (monitoring, trading, game-playing) where work isn't decomposable into isolated tasks. The claim is *scoped to software engineering workflows*, not all agentic AI.

## Operational form

[[action-implement-agent-queues]].