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

# Introduction

> Secure AI coding agents with local supervision, policy enforcement, and audit trails.

Rye secures AI coding tools such as Claude Code, Codex CLI, Cursor, and Windsurf.

It runs on developer workstations as a local CLI and daemon. Rye wraps agent processes, routes model traffic through a policy-aware proxy, captures local session telemetry, and uploads normalized audit data to the Rye control plane.

Use Rye when you need to answer these questions:

* Which prompts, files, tool definitions, and model responses crossed the network boundary?
* Which policy rule allowed, denied, or flagged a request?
* Which developer, device, process, and assistant session produced an event?
* Which files changed during an agent session?
* Which local approvals expanded an assistant's operating boundary?

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Install Rye, sign in, start the local proxy, and run a supervised agent session.
  </Card>

  <Card title="Why Rye exists" icon="shield-check" href="/why-rye">
    Understand the governance gap around AI coding agents and why Rye supervises them from outside the assistant.
  </Card>

  <Card title="Agent supervision" icon="terminal" href="/agent-supervision">
    Use `rye wrap` for PTY supervision, file-change telemetry, approval capture, and proxy environment injection.
  </Card>

  <Card title="Command reference" icon="square-terminal" href="/commands">
    Review the main commands for auth, daemon control, proxy routing, shims, history, policy diagnostics, and upgrades.
  </Card>
</CardGroup>

## How Rye fits

```txt theme={null}
developer
  -> rye wrap or app shim
  -> AI coding assistant
  -> Rye local proxy or API shim
  -> policy decision
  -> model provider

local telemetry
  -> Rye daemon
  -> SQLite cache
  -> Rye control plane
```

The local proxy sees model API traffic. The wrapper sees the agent process, terminal session, approvals, and file changes. The ingester reads assistant history stores. The control plane receives normalized events so security and engineering teams can inspect the full workflow.

<Tip>
  Start with [Quickstart](/quickstart). It takes one workstation from install to a captured agent session.
</Tip>