Skip to content

Send your first message

You’re signed in and looking at a blank conversation. This tutorial walks you through your very first chat — about 60 seconds, start to finish. By the end you’ll have asked a question, watched Chat work through it, read the answer, and checked where the answer came from.

The input bar (we call it the composer) sits at the bottom of every conversation. It’s a single rounded card with a text box on top and a row of controls along the bottom.

When you’re starting fresh, you’ll also see it front and center on the Welcome screen. Either one works — they’re the same composer.

Click into the text box and type a real question. For your first message, try something self-contained that doesn’t depend on any of your own files yet, for example:

What’s the difference between a fixed-rate and a variable-rate loan?

A few things worth knowing as you type:

  • The box grows as you write, so longer questions stay readable.
  • There’s a 4,096-character limit per message. A small counter appears when you’re getting close, so you won’t be caught out mid-thought.
  • Enter sends your message. Use Shift + Enter to add a new line without sending. (If you’d rather have Enter add a new line instead, you can flip that in Preferences.)

Press Enter, or click the Send button on the bottom right of the composer.

Your message appears at the top of the conversation, and the assistant starts working on its reply. While it’s thinking, the Send button turns into a Stop button — click it any time if you want to cut a response short.

Chat doesn’t just guess at an answer. It works through your question in clear steps, and it shows you what it’s doing in a small thinking view above the reply. You’ll see plain-language steps roll past, such as:

  1. Loading conversation — picking up the thread so far.
  2. Understanding your intent — figuring out what you’re actually asking.
  3. Checking safety guidelines — making sure the request is appropriate.
  4. Gathering information — pulling in relevant material (when your question calls for it).
  5. Filtering results — keeping what’s useful, dropping what isn’t.
  6. Building context — assembling everything it needs to answer.
  7. Generating response — writing the answer.
  8. Composing response — formatting it for you to read.

This usually takes a few seconds. You don’t have to do anything during this stage — it’s there so you can see how Chat reached its answer, not just what it concluded. You can expand the thinking view for a more detailed trace if you ever want it.

The reply streams in as it’s written, so you can start reading right away. It will be formatted for easy reading — headings, lists, and tables where they help.

Underneath the latest reply you’ll find a row of quick actions to keep the conversation moving without retyping:

ActionWhat it does
Explain moreAsks for a more detailed version of the same answer
Refine thisAsks Chat to improve and tighten its previous reply
Try different approachAsks for the same answer tackled a different way
CompareShows two versions side by side so you can pick the better one
CopyCopies the reply to your clipboard
RetryRegenerates the reply from scratch

If the answer offers you choices (like A) … B) …), those turn into one-click buttons — just tap the one you want to continue.

When Chat draws on a specific source to answer you, it tells you exactly where. You’ll see small numbered markers like [1] in the text, and a Sources Used card below the reply.

  • Click a numbered marker to jump to its source and see a short preview — the title, a snippet, and a link.
  • Open the Sources Used card to review everything the answer leaned on.

This is what lets you trust an answer rather than take it on faith: you can always trace a statement back to where it came from.

In about a minute you:

  • Found the composer and typed a question.
  • Sent it with Enter (or the Send button).
  • Watched Chat reason through the answer step by step.
  • Read a streamed, formatted reply and used the quick actions.
  • Checked citations to see where the answer came from.