Skip to main content
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?

Quickstart

Install Rye, sign in, start the local proxy, and run a supervised agent session.

Why Rye exists

Understand the governance gap around AI coding agents and why Rye supervises them from outside the assistant.

Agent supervision

Use rye wrap for PTY supervision, file-change telemetry, approval capture, and proxy environment injection.

Command reference

Review the main commands for auth, daemon control, proxy routing, shims, history, policy diagnostics, and upgrades.

​
How Rye fits

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.
Start with Quickstart. It takes one workstation from install to a captured agent session.