# Sandboxed agents run over AgentOS on a Postgres queue alone

> Agno's AgentOS accepts sandboxed agent runs on POST /agents/{agent_id}/runs when the durable queue has Postgres and no Redis.

- Published: 2026-10-19
- Author: Ashpreet Bedi
- Categories: Changelog
- Canonical: https://www.agno.com/blog/sandboxed-agents-run-over-agentos-on-a-postgres-queue-alone
- Markdown: https://www.agno.com/blog/sandboxed-agents-run-over-agentos-on-a-postgres-queue-alone.md

Agno's AgentOS now lets a sandboxed agent's `POST /agents/{agent_id}/runs` through when the queue is durable and its store serializes sessions, which `PostgresDb` and `AsyncPostgresDb` do. With `QueueConfig(durable=True, db=...)` and no `redis=`, the route answers 202 for a background run, and 200 for foreground and streaming runs.

The other submission checks stay as they were, including the registered-instance check and the session-owner check. Without a durable queue the route still refuses, now with `Sandbox API execution requires a durable queue with shared session admission`.

![Real output from a background POST /agents/coder/runs on a sandboxed ClaudeAgent with QueueConfig(durable=True, db=PostgresDb) and no Redis, using a stand-in sandbox. Before: 400, Sandbox API execution requires a durable queue with Redis coordination and shared session admission. Now: 202, status PENDING, with a run_id.](https://www.agno.com/images/v3-1-5-sandbox-runs-without-redis.png)

The capture comes from FastAPI's `TestClient` against an embedded Postgres, with a stand-in sandbox that has no compute, since the route answers before any container starts.

Redis still matters once you run more than one replica, because it carries run events and cancellation between them.

See the [cookbook](https://github.com/agno-agi/agno/blob/main/cookbook/frameworks/sandbox/docker/sandbox_claude_agentos.py), and learn more about [multi-replica deployments](https://docs.agno.com/agent-os/background-execution/multi-replica) in the documentation.