# Rein

> A control plane and CLI for governing AI agent operations routed through Rein.

## Public resources

- [Product overview](http://reincontrol.com/)
- [Installation, MCP setup, policy rules and API documentation](http://reincontrol.com/docs)
- [Claude Code integration guide](http://reincontrol.com/docs/integrations/claude-code)
- [Codex CLI integration guide](http://reincontrol.com/docs/integrations/codex)
- [Hermes Agent integration guide](http://reincontrol.com/docs/integrations/hermes)
- [OpenClaw integration guide](http://reincontrol.com/docs/integrations/openclaw)
- [OpenClaw 2.0 integration guide](http://reincontrol.com/docs/integrations/openclaw-2)
- [About Rein Control](http://reincontrol.com/about)
- [Contact Rein Control](http://reincontrol.com/contact)
- [Privacy at Rein Control](http://reincontrol.com/privacy)
- [Plain-text product and integration guide](http://reincontrol.com/llms-full.txt)
- [OpenAPI specification](http://reincontrol.com/api/v1/openapi.json)

## When to use Rein Control

Reach for Rein when an agent needs a command, file operation, deployment, or other tool call governed by an explicit identity, policy decision, human approval, or audit record. Use Rein MCP tools for MCP-capable hosts and the Rein CLI for direct shell and CI workflows. Do not fall back to an ungoverned native tool when an operation cannot use the configured Rein path.

Rein does not automatically govern tools that bypass its integration. Host restrictions require separate configuration and verification.