Conversations
rho works through conversations stored in Nexus. A selected model answers, and a runner supplies working files and tools. This page covers the browser page; Telegram, editors and the terminal are other entry points to the same conversations.
Entry points
| Entry point | Use it for |
|---|---|
Browser — the stack's rho URL, or rho console --open on a host | Settings, Telegram setup, ongoing conversations, questions, approvals, execution controls and schedules |
| Telegram | Ongoing conversations, files, voice and controls from an allowed chat |
| Editor through ACP | Conversations inside a compatible editor |
Terminal — rho run "..." | One noninteractive request with output and an exit code |
Start and continue
Open rho and choose Connect to Nexus when no browser session exists. Later logins preserve the runtime's Agent connection; signing out ends only your browser session.
Create a conversation with an available model and runner. The runner uses its default working directory. The model picker starts at Automatic, which lets rho use the agent's Preset. Send the first request and follow the answer and tool activity.
Choosing a specific model pins that provider and model, even when it matches the default. Reopening a conversation restores its original model choice; Last response in the model menu shows the route that actually answered, which can differ after fallback. Leaving the picker untouched preserves the conversation's model intent. Choose Automatic to clear an override on the next message and use the current Preset again.
- Sending another message while work is running steers the current reply at its next model boundary by default.
- Sending when idle starts a new turn.
- Reopen a saved conversation to continue from its durable history. Rename, archive and restore controls organize the list; there is no delete.
- Conversations lists the Main Agent's ordinary conversations in the selected workspace. Its archived view uses the same scope. Bot history and child executions stay outside this list.
- Bots is separate. A Bot's sidebar name opens its unique current conversation; its settings button opens identity, Home, channel target and history controls.
The composer offers three ways to deliver a message to running work: steer (the default) hands it to the next model boundary of the running reply; queue holds it for a later turn; Send now inserts a model boundary immediately while long tools keep running and deliver their results later.
Ctrl+Enter or Cmd+Enter sends normally in a new or idle conversation and uses Send now during running work. With an empty composer, it promotes the latest waiting steer instead of sending its words again.
Scroll upward to read earlier messages without following new output. Jump to latest returns to the bottom and resumes following.
Conversation titles
After the first request is accepted in a new conversation, rho generates a short title from your input in the background. The title follows your input's language. Title generation keeps the conversation's access restrictions. Later messages do not generate another title, and a manual rename takes precedence. A title-generation failure leaves the conversation and its reply available; you can rename it yourself.
Choose Settings › Defaults › Conversation title model:
| Choice | Behavior |
|---|---|
| Follow current model | Use the model selected for the first request; this is the default |
| None | Turn automatic titles off |
| A specific model | Use that available text model for titles |
The choice applies to future first submissions. It does not rename existing conversations or change the model answering your messages.
Execution controls
- Questions and approvals appear beside the work. Answer or decide the specific pending item there; see Approvals and questions.
- Pause / resume suspend and continue execution.
- A failed step can be retried or abandoned.
- Stop stops execution, including background work derived from the reply after it was delivered. Closing the browser or switching conversations only detaches the viewer.
- Regenerate produces a new candidate answer for a turn and permanently stops the replaced candidate's unfinished work. Selecting an older candidate never revives its work.
Drafts and uncertain sends
A failed or uncertain send keeps its draft and request identity for a manual retry on that page. Reloading discards this pending state, so inspect the history before resubmitting an uncertain message after a reload.
Retention
Old conversation text stays readable and searchable after Nexus's retention policy removes execution details; the page labels missing details. Administrators set the window; see Retention, usage and budgets.
Bot conversations
A Bot has one current conversation. Its page shows current and historical conversations, including archived rows, across their original workspaces. Open a history row to read it; Resume makes it current again.
New conversation immediately creates a conversation in the Bot's Home Workspace and selects it. New and Resume archive the replaced conversation unless its Workspace is already archived. In that case, the switch leaves the previous conversation unchanged. After restoring that Workspace, use Resume to select the old conversation before sending new input. Other archive failures prevent the switch from completing.
Switching does not stop accepted work. Old work and late results stay with their original conversation; use Stop explicitly when needed. Changing Home affects only future new conversations.
The Bot settings include Subagent, which starts on. Turning it off makes future requests execute directly in the main Bot conversation. This also applies after New, Resume and Fork. Bots always keep Code mode off; existing workers retain their captured tools and can finish normally.
Bot conversations are read-only in the browser except for Stop, including history that is no longer bound to a channel. Continue messages and approvals in the Bot's Telegram target. Attachments remain readable. The Bot's introduction is static text and does not start a model request.
Browser access
After pairing, Settings › General › Opening this page decides what a browser needs before it can use rho:
| Choice | Behavior |
|---|---|
| Automatic | Opens by itself on this machine; asks for a Nexus sign-in from other machines |
| Open | Opens for anyone who reaches the page |
| Nexus sign-in | Always asks for a Nexus sign-in |
| Unlock password | Asks for rho's own password, stored as a salted digest |
A page admitted by the gate holds no Nexus account; Settings names how it got in and offers Sign in with Nexus for actions that need one. Changing or removing the password ends every other unlocked browser.