Chat quickstart

Open Chat from the sidebar. You land in a project with the composer at the bottom of the pane:

1. Type what you want done and press Enter.
2. Your message moves into the pane and the runtime starts. This takes about 25 seconds.
3. The message sends on its own as soon as the runtime is up, and the answer streams in.

That is the whole path. Everything below is what is happening while you wait, and what to reach for next.

The pause after Enter

Pressing Enter on a project with no running sandbox provisions one. The pane tells you so while it happens: your message at the top, then what is being provisioned and how long it has taken so far.

The first time you do this in a project, the panel also says that runtime time is billed. That notice appears once per project, at the moment spend starts, not on every message.

The meter runs until you stop it

A running sandbox accrues runtime credits whether or not an agent is working. Pause it from the runtime menu in the header when you step away, or reset it when you are done with the state inside it.

If the start fails, your message goes back into the composer. Nothing is lost.

Skipping the wait

The pause is a cold start, not a per-message cost. Once the runtime is running, messages send immediately, and the session list marks every row in that project running so you can see which of your projects are warm before you click into one.

Next

• Give the agent more tools: install a capability from the runtime cluster in the header. See Runtimes in Chat.
• Change who you are talking to or what is reasoning: see Agents & models.
• Learn the / palette, which is faster than any of the pickers: see Commands.