Less waiting, more control in chat

Release 2.32 improves the chat experience from opening a project to sending your next request. You can see what is loading, stop a response, and keep writing while work is in progress.

New

• Stop a response from the composer. The Send arrow changes to a square Stop icon while RiverX is working. Click it to stop the current response in Chat, OpenCode, Codex, or media generation. The status shows when stopping is in progress.
• Know what chat is preparing. An animated loader names the current step, such as checking your workspace, preparing project context, or loading conversation messages. You can draft your message while setup finishes.
• Retry a failed load. If a conversation cannot finish loading, use Try again. Your draft stays available while you retry.

Improved

• Get back into chat sooner. Conversation setup can proceed while the full model list loads. Your saved project model stays selected when the list arrives.
• Less waiting for project context. RiverX reads your project's notes and instructions together when preparing a new conversation.
• Read saved history while updates load. When you return to a conversation you have opened before, saved messages can appear while RiverX checks for the latest history. An Updating conversation indicator makes that refresh visible.
• Write the next request while a response runs. Type a follow-up and press Enter to add it to the waiting requests. You can prepare the next change without waiting for the current response to finish.
• A composer that clears after sending. Your submitted message and attachments leave the input area without waiting for the full response. New text and files you add while RiverX works are kept.
• Control what happens after Stop. Stopping a response pauses waiting requests. Choose Resume queued requests when you are ready to continue. Completed file changes stay in your project; stopping does not undo them. An action already underway may finish before the response stops.
• Loading feedback that respects reduced motion. The current step remains visible even when loader animation is disabled by your device preference.

Fixed

• Failed sends no longer lose your draft. If a message could not be submitted, its text, attachments, and selected skill are restored for retry. Text you have started writing for the next request is preserved.
• Follow-up requests are no longer ignored during generation. Pressing Enter on a new request adds it to the waiting requests, while repeated submissions during an upload are blocked.
• Stop also works during preparation. A request stopped before it has started is no longer sent afterward when preparation finishes.
• An upload cannot restart work after Stop. If a follow-up file is still uploading when you stop the current response, that follow-up stays in the composer for you to send later.
• Retrying a new conversation keeps it new. A failed attempt no longer silently reopens an older conversation. If the first attempt already created the new conversation, retry continues that same conversation instead of creating another one.
• History refreshes preserve waiting messages. Pending and queued requests stay visible when newer conversation history arrives.
• Older loads cannot replace your latest selection. A delayed result from a previous conversation no longer takes over the loading feedback for the conversation you just opened.

Open a project from your dashboard to use the updated chat.