Agent and Team pre- and post-hooks now run as background tasks in AgentOS, so they no longer block the main operation. This reduces end-to-end latency and increases throughput, especially under concurrent load. Teams should ensure hooks are idempotent and not dependent on synchronous completion.
Details
- Hooks execute concurrently and may complete after the primary request returns.
- Move any required synchronous logic into the main flow; treat hooks as asynchronous side effects.
- Expect reduced wait times and better parallelism in high-throughput environments.
Who this is for: Teams scaling agent workloads, multi-tenant platforms, and latency-sensitive use cases.