Find and Continue Saved Rivya Chats

Return to a saved chat when you want to continue the same conversation. Rivya saves completed conversation turns to your account; an unsent draft in the input box is not a saved message or a project backup.

Reopen a Conversation

1. Sign in with the account you used for the conversation and open /history/chats.

2. Find the card by its title, model, date, and last-message preview. Tool conversations also show the tool name when available.

3. Choose the continue action to open that session. Wait for its saved messages to load before sending anything.

4. Review the last answer, the selected model, and the available controls. Correct outdated facts in your next message.

Reopening a session does not send a new message or charge for a new response. Sending the next message can consume credits. See History for the distinction between chat records and generated files, and Chat Studio for the composer and controls.

Know What Is Saved

A new session is created when you submit a message. Its title comes from the opening message. Successfully completed conversation turns are available when you reopen it, along with the session's model and tool context and supported chat settings.

Do not assume everything visible on screen has been saved. Text you have not sent and attachments waiting in the composer are not saved conversation messages. A partial streaming answer, a failed turn, or an unanswered message may be absent after reloading. An empty session card does not prove that a response finished.

Copy important drafts and approved text to your own document before leaving the page. Saved attachment references do not guarantee that the underlying file remains accessible indefinitely. Keep your original uploads and download media results using Output Downloads.

Continue, Start Fresh, or Change Models

Continue the existing session when the next question depends on earlier messages. Review the relevant context first; saving a conversation does not make its factual claims correct. Long conversations still have to fit the selected model's input limits. Check Model Fields and Parameters for model-specific constraints.

The new-session action clears the current conversation, unsent input, and pending attachments from the workspace. It does not delete the earlier saved conversation. Open that earlier conversation from chat history when you need it again.

Changing the model starts a separate conversation rather than transferring the whole saved thread to another model. Copy a short summary of the goal, verified facts, and the exact text you want to carry forward. Before switching, preserve any unsent draft. Available tools and controls depend on the destination model; consult Model Availability if a previously used model cannot be selected.

Check Credits Before the Next Message

A saved session is not a prepaid bundle of future replies. Each new message is a new turn, and earlier conversation content can contribute to the input used for that turn. The displayed starting credit amount is not a fixed price for every message.

Check the model and supported options before sending. For reservation, final settlement, and credit returns, read Credits and Billing and Task Lifecycle. If a reply fails or the connection drops, check the saved session and credit transactions before resending; another submission may incur another charge.

Carry Decisions into Generation

Use chat to develop a brief, then copy the approved prompt and necessary references into the image, video, or audio workspace. A saved chat does not automatically restore every generation setting or store every generated media file.

For example, keep a product's verified features and approved wording in the chat, save the chosen image separately, and record the model and settings used for it. Chat Workflows and Prompt Writing Basics explain how to turn that context into a useful next request.

If a Session or Message Is Missing

Check the account and open chat history rather than generation history. The generation list's most-recent-24 limit does not apply to the chat list. If the session page reports a loading error, retry loading it before sending a message into an empty-looking workspace.

A missing last message may have been unsent, failed, or not fully saved; absence alone does not establish a billing outcome. Copy any text still visible that you need to keep. If the issue persists, contact [email protected] with your account email, session URL or ID if available, model, approximate message time and time zone, and the exact error. Do not send login codes or API keys. See Troubleshooting.