Configure the macOS app
Create reusable browser Profiles, configure AI models, and run prompts automatically on repeating schedules.
REL documentation
Keep persistent Chromium sessions on your Mac and access them from Codex, Claude Code, MCP, the CLI, a local API, or the typed Rust client.
Start with one command
Section titled “Start with one command”The bundled rel CLI is the quickest way to capture a rendered page and the best place to learn REL’s model.
rel https://rel.meREL keeps Chromium inside the installed macOS app. Like curl, the CLI writes page data to standard output and events to standard error, so either stream can be piped or redirected independently.
Go deeper
Section titled “Go deeper”Automate pages with actions
Use one JSON contract for clicks, waits, text entry, named keys, and selections from every REL client.
Install an agent plugin
Add the shared REL plugin to load its MCP server and browser workflow guidance automatically.
Connect an MCP client
Launch the bundled stdio adapter for focused status, capture, page automation, session-list, and proxy-list tools.
Control the browser with RPC v1
Attach pages, perform actions, manage persistent sessions, and stream captures over REL’s loopback-only HTTP API.
Use the typed Rust client
Build directly on the same rel-client crate used by the bundled CLI, with typed requests, responses, errors, and capture events.
Supported runtime
Section titled “Supported runtime”REL has one supported path: the installed /Applications/REL.app owns Chromium and supervises its bundled local agent. CLI, SDK, and MCP adapter calls connect to that agent; the agent routes browser work back into the visible app.