The conversation menu

The header of a conversation tells you which conversation you are in and how it is doing. The ⋯ menu at its right holds everything you do to the conversation or to the relay that is not part of writing a message. This page lists both, one row per item, with the labels exactly as the app shows them.

The header #

From left to right:

Added in 0.9.17 On a phone (a window up to 680 px wide) the header has two rows. ☰, the title and the buttons share the first, so the title gets the width the buttons leave. The via agent line, the chips (watching, watched, scheduled), the working folder and the session usage sit side by side on the second row, across the whole header, and a chip no longer breaks inside its text. A header with nothing for the second row stays one row. The desktop header is unchanged.

The model and the reasoning effort are not in the header. They are chosen in the composer; see Models and reasoning.

The status dot #

The relay's status dot sits at the top of the conversation list, next to + New Chat. Hover it for a sentence that says more than the colour.

A tunnel that is set up but not connected leaves the dot green and says so in the tooltip, for example Web relay reachable; Cloudflare tunnel disconnected.

The ⋯ menu #

The menu is in the same order everywhere. Some entries need an open conversation and are left out, not greyed, when none is open; the others are there whenever you are signed in, so ⚙️ Settings is reachable on a fresh install. The first two lines are information; only 🚮 Empty queue in the second is a control.

Two actions that older versions had, 🗜️ Compact and 🔄️ Refresh history, are no longer in the menu. Compacting is the /compact command in the composer; see Compacting.

In the shared view only the Day or Night entry is left, and the menu button stays usable even when the shared conversation could not be loaded.

About OAR Added in 0.9.11 #

ℹ️ About OAR names the relay's version in the menu, for example ℹ️ About OAR · 0.9.19, and opens a window with what this relay is and has done:

• the version, the commit (for a git checkout) and when the relay started;
• each provider that is switched on, with its CLI and SDK version and whether it is online. DeepSeek is not in this list, even when it is switched on;
• conversations, turns and messages since the first conversation, turns per provider, and the usage the providers report: Copilot premium requests, Cursor and Grok tokens and cost, Claude Cloud cost. DeepSeek turns are counted, but their spend is on the DeepSeek usage card, not here;
• uptime, the size of the database and the workers that run.

With Check for updates automatically on, it names the latest version; with the check off it says where to turn it on. It sends nothing to oar.sh itself. Viewers of a shared link do not get the entry.

The window reads GET /api/about, which needs the access token. The relay counts a large database in small steps and keeps the totals for a minute, so reopening the window at once shows the same numbers.

The tmux console #

🖥️ Inspect tmux console opens a window titled tmux Console Inspector (read-only) with the session id and a status line. It is a view, not a terminal: you cannot type into it, and it has no refresh button. Closing it, or clicking outside it, ends the view and the worker is unaffected. A conversation that has no session yet answers with the notice Select a conversation with a bound SDK session first.

What you see depends on the conversation's agent:

The view follows the worker live. If that live stream ends while the worker is still running, the window switches to a snapshot of the screen taken about every 0.7 seconds. If it cannot load its terminal display from the internet, it falls back to plain text and the status line says so.

The inspector needs the conversation's worker to run in a tmux session, which happens on Linux and macOS with tmux installed. On Windows, and on a host without tmux, the entry is still in the menu and the status line shows tmux is unavailable on this relay host. It also refuses when the worker is not running: Session worker not found, or Session worker is not active followed by its state. See Restarts and resuming for how workers are run.

Restart web relay #

🌄 Restart web relay asks first, then queues a restart of the relay. The restart waits until no turn is running, so it never interrupts one; a banner on every device shows the wait. The relay comes back within moments and the open page reconnects. How long it waits, what survives and what is lost is on Restarts and resuming.

Added in 0.9.13 The window lists first which sessions' turns the restart would wait for, how many messages it would hold and which background tasks keep running. 🌄 Restart when idle queues the restart; Restart now does not wait. The banner names the sessions as links, shows how long it has waited and has Restart now and Cancel restart. After Ask after a queued relay restart has waited (30 minutes by default) it asks whether to restart now, keep waiting or cancel. Choosing the menu entry while a restart is queued shows the same choices.

Any signed-in browser can queue the restart: it needs the access token and nothing else. Added in 0.9.11 Before 0.9.11 the relay refused it over the local network and from a proxy on another machine, yet the page reported success. When the relay refuses the request now, the page shows the relay's reason, and a request that got no answer says so. From a terminal on the relay's machine, oar restart does the same.

Suspend host #

💤 Suspend host (see also Suspend host) opens a window titled Suspend host that lists what is still running (turns, background agents, open CI runs). With nothing running it asks Put this PC to sleep? and the machine sleeps 30 seconds after you confirm, with a countdown banner on every device that has a Cancel button. With agents still active it offers 💤 Suspend when idle: the machine sleeps once they have finished and everything has been quiet for 2 minutes. Reopen the entry (now 💤 Suspend pending…) or use the banner to cancel.

It works only when the relay runs on Windows. On another system the window says Host suspend is only available when the relay runs on Windows. The entry is shown by default on every system. Show Suspend host action in Settings → General shows or hides it in your browser; see Settings.

Kill session #

☠️ Kill session asks for confirmation, then stops the conversation's worker and the processes it started. A turn that was running ends and needs a retry or a new message; the conversation, its history and queued messages stay, and the next message starts a fresh worker that resumes the provider's session. Use it when a conversation is stuck, when Stop does not work, or when the agent should start again to pick up new tools or settings. The entry is greyed out while the conversation has no worker session. Details are on Restarts and resuming.