Use Rivya chat for research, prompt shaping, tool sessions, image-assisted analysis, saved context, and image or video handoffs.

Use this AI chat workflow guide when the work starts with research, planning, prompt shaping, image-assisted analysis, tool-based chat, or a handoff into image or video generation.

Chat in Rivya is more than a generic conversation box. It is where ideas get clarified, where tools open into real working sessions, and where many image or video tasks actually begin.

The Current Chat Entry Points

Today, chat can be entered from several places:

/chat: public discovery page
/ai-models/[modelSlug]: public model-first start
/tools/[toolSlug]: public tool-first start
/studio/chat/[modelSlug]: authenticated saved chat workspace
/studio/chat/session/[sessionId]: reopen an exact saved session
/studio/tools/[categorySlug]/[toolSlug]: authenticated tool-based chat entry

The public paths are useful for discovery and first-run starts. Real conversation state and saved continuity matter most in the authenticated Studio flow.

Plain Chat vs Tool-Based Chat

Use plain chat when:

the task is still exploratory
you expect the direction to change a few times
you want to choose the framing yourself

Use a tool-based chat entry when:

the task shape is already narrow
you want a preset instruction layer helping from the first turn
AI Calculator or AI Solver already matches the job

Right now, tools are not separate apps. They are chat entry points with a default model, starter prompts, and a clearer frame from the first turn.

What a Chat Session Can Carry

A current Rivya chat session can keep more than just text.

It can carry:

the selected chat model
a tool preset, when the session started from a tool
an image attachment for analysis
the saved message history itself

That is why /studio/chat/session/[sessionId] matters. It is not reopening a temporary transcript. It is reopening a working conversation with its model and tool context intact.

Image Attachments and Prompt Work

Chat currently supports an image attachment flow for analysis-oriented work.

Right now, the split is pretty simple:

chat is at its best when you bring in an image for analysis, explanation, or prompt work
once the task moves into audio, video, or document-style media, the matching dedicated workflow is usually the smoother place to continue
image, video, and audio sections still carry the fuller media workflows

That makes chat useful when the job is:

explain what is in this image
improve this image prompt
turn this image into a stronger video prompt

When an image context is present, the chat UI can also expose quick actions for image analysis and prompt improvement. This is one of the clearest places where chat starts feeding the rest of the product instead of staying isolated.

How Chat Hands Off Into Image and Video

One practical Rivya pattern is:

use chat to clarify the brief
ask for a stronger image or video prompt
move into the matching image or video workflow
continue the project from saved history later

Some replies can also come back as ready-to-use prompt sets, with separate sections for image and video use. That is why chat belongs close to creation workflows, not only in a “writing” bucket.

What Gets Saved, and What Does Not

Chat is saved as:

chat sessions
chat messages

This is different from image, video, and audio generation, which become async task records.

So the practical split is:

chat lives in session history
generation lives in task history

If you want to reopen a conversation, use History and then return to /studio/chat/session/[sessionId].

Public Chat vs Full Studio

The easiest rule is:

public chat helps you start
studio chat helps you continue

If you are not signed in, public pages are still useful for comparison and getting started. But real chat execution is tied to account state, so the actual working flow is strongest once you are inside the authenticated Studio.

Good Starting Patterns

These are the most reliable current patterns:

fuzzy brief: start in plain chat
narrow reasoning or math task: start from a tool entry
existing image you want help with: attach it in chat first
preparing a still or motion workflow: use chat to generate the next prompt before spending heavier generation credits

Chat Workflow Checklist

When the deliverable is still thinking, writing, reasoning, or planning, check:

Start in chat when the task is open-ended or needs clarification.
Pick a model based on reasoning depth, coding needs, vision support, and cost shape.
Move into image, video, or audio only when the deliverable becomes a media asset.
Save useful threads before turning them into prompts or production briefs.
Use tools only when the chat task has a repeatable shape, such as calculation or step-by-step solving.

Recheck When Chat Becomes Production

Recheck when the task starts requiring uploads, generated media, billing-heavy runs, or long-term saved continuity. That is often the point where Chat should hand off to another Studio.

Rivya AI Chat Workflow Guide