> ## Documentation Index
> Fetch the complete documentation index at: https://www.osohq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Edge Proxy

> Route agent traffic through Oso's edge proxy for full session monitoring.

The Oso edge proxy is a reverse proxy at `agents.osohq.cloud` that sits between AI agents and their LLM providers. It captures the full content of agent sessions, including prompts, completions, tool calls, and metadata, and feeds them into Oso for monitoring and alerting.

## What it captures

When agent traffic flows through the edge proxy, Oso records:

* **Prompts** sent to the LLM
* **Completions** returned by the LLM
* **Tool calls** and their parameters
* **Model metadata** (which model was used, token counts)
* **User and session identifiers**

This data powers [session monitoring](/oso-for-agents/session-monitoring) and [alerts](/oso-for-agents/alerts).

## Supported agents

The edge proxy works with any agent that allows configuring a custom base URL for its LLM provider. Currently supported:

| Agent          | Environment |
| -------------- | ----------- |
| Claude Code    | CLI         |
| Codex          | CLI         |
| Gemini CLI     | CLI         |
| Claude Desktop | Desktop     |
| Cursor         | Desktop     |
| Antigravity    | Desktop     |

<Note>
  Agents with hardcoded LLM endpoints that don't support custom base URLs cannot use the edge proxy. For those agents, consider using the [browser extension](/oso-for-agents/integrations/browser-extension) or [EDR integration](/oso-for-agents/integrations/edr) for discovery.
</Note>

## Setup

For step-by-step configuration instructions, see the [Quickstart](/oso-for-agents/quickstart-coding-agents). The quickstart walks through:

1. Getting your Environment ID from the Oso UI
2. Configuring your agent to route through `agents.osohq.cloud`
3. Verifying sessions appear in your dashboard