Open it
clauded uiThe GUI is an optional component downloaded on demand: the first run installs it, after which it just opens. Available on macOS and Windows; on Linux use the command line. Install-related commands are on the Install page.
Menu bar / tray
The console lives in the macOS menu bar (the Windows tray) as a quick-access menu:
- Status line — tells you at a glance whether things work right now
- Launch Claude CLI… / Claude Desktop / Claude Web
- Launch CodeX CLI… / CodeX Desktop / CodeX Web
- Background service — start or stop it; the label follows the current state
- Open console (⌘O) and Quit (⌘Q)
When something is wrong with the environment, an extra highlighted line appears in the menu; clicking it applies the suggested fix.
Console window · Home
The window has just two tabs — Home and Logs. Technical detail is folded away at the bottom of Home.
Overall status
One line at the top says whether you are good to go. Failed actions, or a status feed that stopped updating, appear as a red banner right below it, with one-click copy of the full error.
Claude panel / CodeX panel
One block per platform, side by side on a wide window and stacked on a narrow one. Each block contains:
| Section | Contents |
|---|---|
| Enable switch | Turn it off and your editor extensions and desktop app immediately go back to your own configuration |
| Three launch buttons | Open web / Launch CLI / Launch Desktop |
| Launch options | "Skip permission prompts" (--dangerously-skip-permissions); on the Codex side, "YOLO mode" (--yolo). CLI only, and the choice is remembered |
| Account card | The dedicated account assigned to this device — "not assigned yet" and "device removed" are spelled out here |
| Readiness | Three dots for CLI / VS Code / Desktop: grey = not installed, amber = downloading or not ready underneath, green = ready |
| Which copy | The executable path and version in use, switchable between "Managed by Clauded", "System install" and "Choose…" |
| Editor integration | Whether VS Code, Cursor and Windsurf are wired up; extensions pointing elsewhere or unreadable settings are named explicitly |
| Desktop | Whether the desktop app is installed; if not, the launch button above downloads it and progress shows on this card |
Background service
Running state plus a start/stop button. When it is down, the card says plainly that Claude cannot connect.
Device login
Device number, plus Log in / Log in again / Log out. Logging out asks for confirmation and explains that your original Claude credentials will be restored.
Route
A single line with the current route. "Switch" expands every candidate with its latency and reachability so you can pick one directly; "Auto-pick fastest" measures and chooses for you.
Diagnostics (collapsed)
The latest error (the gateway's own wording plus a request ID), endpoint address and latency, process pid, daemon and GUI versions, install location, whether start-at-boot is on, and whether the command line is on your PATH. The last two come with "Enable" and "Fix" buttons when they are not set up.
Console window · Logs
- General log / Request log as two sub-tabs, each with a live count
- Record requests switch — off by default; once on, every request is logged (takes about two seconds to apply) and clicking a row expands the full request / response detail
- Filter, Pause / Resume, Clear (the list only) and Purge (truncates the log files and deletes request details — irreversible)
The request table shows time, method, URL, status, duration and byte counts. A status of "direct" means that request did not go through the proxy.
The GUI and the CLI are one thing
Every action in the interface runs the same clauded command underneath, so anything you click shows up immediately in clauded status, and vice versa. If the command-line component is missing when you first open the GUI, it installs clauded before showing the main window.