| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/ai-gateway/integrations/coding-agents/ | [Back] [Original] |
Coding agents send model requests to a provider on your behalf. By pointing the agent at AI Gateway instead of the provider, you observe and control that traffic without changing how you work.
Routing a coding agent through AI Gateway gives you:
Follow the setup guide for your coding agent:
Coding agents routinely send source code, configuration files, and snippets to model providers. That traffic can include API keys, customer data, or other sensitive material. Because AI Gateway sits between the agent and the provider, you can inspect and control it without changing the agent.
Data Loss Prevention (DLP) scans request and response bodies against detection profiles and either flags or blocks matches. Use it to catch secrets, credentials, or regulated data leaving (or returning to) the agent.
Note
Many coding agents stream responses by default. When DLP response scanning is enabled, AI Gateway buffers the full provider response before returning it, which increases time-to-first-token. If you need low-latency streaming, set the DLP policy Check to Request only, or use a separate gateway for latency-sensitive traffic. Refer to streaming behavior.
After you configure a tool, confirm that traffic reaches AI Gateway.
Send a prompt from the coding agent.
In the Cloudflare dashboard, go to the AI Gateway page.
Go to AI Gateway ↗Select your gateway, then select Logs. Confirm that the request appears with its model, token count, and latency.
For more information on logs, refer to Logging.
| Web Proxy Viewer | New URL | Original Page |