Browser UI

Ratel Local serves the browser UI from the persistent daemon. Run setup first, then open a fresh authenticated session:

ratel-local daemon open
# Equivalent shortcut
ratel-local ui

ratel-local ui --no-open prints the session URL instead. ui --port is no longer supported; choose the daemon port during first setup or service installation.

What you can manage

• See registered projects, connected MCP clients, and live user/project gateways.
• Add, edit, remove, and authorize MCP servers by scope.
• Import or link Claude Code and Codex, including duplicate-installation repair.
• Import and register skills by user, project, or local scope.
• Configure and preflight BM25, semantic, or hybrid retrieval under Settings.
• Install or remove the Claude Code statusline.
• Inspect backup metadata for recoverable writes.

When the experimental Cloud telemetry feature is enabled on the daemon, Settings also shows Ratel Cloud credentials and native Claude Code/Codex exporter controls. Those controls stay absent while the feature gate is off. See Experimental Cloud telemetry.

Agent Setup

Open the agent page for Claude Code or Codex to inspect its connection and native MCP entries.

• Link installs or reconciles the stable Ratel Local plugin. It uses the reviewed connector fallback only when a new plugin installation fails.
• Import previews MCP and skill changes before a revision-checked commit.
• Fix duplicate installation removes a recognized explicit Ratel entry when the plugin is already active.
• Switch to plugin removes the explicit fallback only after plugin installation succeeds.

Unrelated MCP entries are preserved. Cursor is not adapted here; use the manual Cursor guide.

Settings and reconnects

Retrieval settings have one validated save flow. A missing Hugging Face model requires explicit download confirmation; the dialog shows actual bytes and percentage before verification and commit.

Reconnect an agent after changing MCPs, skills, retrieval, or OAuth. New clients acquire the new gateway generation while existing clients finish on the revision they already hold.

Backups

Configuration changes use the same revision checks, journal, and backup path as the CLI. The UI does not have a general restore button.

ratel-local backup list

Open the matching ~/.ratel/backups/<timestamp>/manifest.json and follow Backups and rollback when manual recovery is required.

Security boundary

The daemon binds to 127.0.0.1. API requests require the daemon credential or a short-lived UI session token.

Treat the URL printed by ui --no-open as a credential. Do not forward, publish, or save it in project files.

Next steps