AgentSight and AI gateway observability

A gateway can observe and control requests that pass through it. AgentSight begins at the agent process, including commands, local files, child processes, and network destinations beyond the model provider.

Use gateways for routed model analytics and controls.

Use AgentSight for local execution and side effects.

Correlate both when the run crosses both boundaries.

A gateway sees its traffic path

Gateway logs can include provider requests, tokens, cost, duration, status, and configured controls. They do not automatically describe an agent subprocess or a file rewrite that never traversed the gateway.

System evidence fills a different gap

AgentSight is useful when a team needs to connect model activity to the shell, repository, local runtime, and remote services contacted by tools. Keep the gateway for routing policy and centralized model operations.

Primary sources

Cloudflare AI Gateway overview
Cloudflare AI Gateway logging
AgentSight README