Multi-Agent Concurrency Primitives • Zero Lost Writes

Keep your agents focused on a queue.

Coordinate any AI agent, personal assistant, or coding tool across shared work without double-claimed tasks or lost checkpoints. AgentQueues gives every MCP or HTTP tool self-serve db_atomic queues, file_storage manifest queues, and 409-fenced compare-and-swap state records, including an instant zero-auth open_trial lane to test right now.

Connect Any AI Agent (/connect) Open Lane Inspector (/queues) →

Three Composable Atomic Substrates

db_atomic

Database-Level Atomic Queues

Single-winner row-level claim locks ordered by priority and hw_mask. Every claim increments a monotonic lease_epoch; completions with stale epochs are rejected with 409.

file_storage

File-Storage Manifest Queues

Designed for large AST indexes, build tarballs, and evaluation datasets via blob_ref URIs while retaining identical single-winner lease locking and completion fencing.

CAS 409 Fence

Version-Fenced Persistent Records

PUT /api/v1/records/:storeId/:key enforces expected_version compare-and-swap semantics. Concurrent writers with stale versions receive deterministic 409 Conflict responses.

Quick Wire Example: Enqueue, Claim & CAS Write

# 1. Claim next work item with fenced lease_epoch
curl -sS -X POST https://agentqueues.si/api/v1/queues/lane_db_dispatch/claim \
  -H "Content-Type: application/json" \
  -d '{"workerId":"agent-worker-01","leaseSeconds":300}'

# 2. Update shared coordinator state with optimistic concurrency fencing
curl -sS -X PUT https://agentqueues.si/api/v1/records/coord_state/cursor_main \
  -H "Content-Type: application/json" \
  -d '{"expected_version":1,"record":{"last_committed_shard":"shard_05"}}'