# Per-request isolation delivers safer concurrency and simpler multi-tenant operations

> We’ve introduced request-scoped isolation for agents, teams, and workflows. Each incoming request now runs against a fresh copy of the component while expensive resources (database connections…

- Published: 2026-01-13
- Author: Agno Team
- Category: Changelog
- Canonical: https://agno-com-nine.vercel.app/articles/per-request-isolation-delivers-safer-concurrency-and-simpler-multi-tenant-operations
- Markdown: https://agno-com-nine.vercel.app/articles/per-request-isolation-delivers-safer-concurrency-and-simpler-multi-tenant-operations.md

We’ve introduced request-scoped isolation for agents, teams, and workflows. Each incoming request now runs against a fresh copy of the component while expensive resources (database connections, models, MCP tools) are safely shared. This eliminates cross-request state leakage, reduces race conditions, and delivers consistent results under load. New factory helpers — get_agent_for_request, get_team_for_request, and get_workflow_for_request — simplify adoption with minimal code changes. This upgrade strengthens reliability for concurrent and multi-tenant deployments without breaking existing integrations.

Details:

- Deterministic behavior via deep-copy isolation per request
- Shared heavy resources keep latency and cost in check
- Updated routers and extensive tests for confidence
- Drop-in helpers standardize lifecycle management

Who this is for: Platform and product teams operating agents at scale, especially in multi-tenant or high-concurrency environments requiring predictable execution and low operational overhead.