AI chat

Use Studio chat for interactive work. Describe the outcome, review the response, and steer the next step in the same conversation. Chat is different from an agent bundle. Chat starts with your message and stays conversational. A bundle is a reusable definition that can run manually or from a trigger. Studio and Slack chat can take up to 1,000 steps per turn to investigate, make changes, and finish. Available credits and time limits can stop a turn earlier. Autonomous agent bundles have no default step cap; an author can set an optional limit in the bundle’s runtime configuration.

​

Send a request

While a turn is running, Studio shows its progress in order. When the answer starts streaming, the progress area folds into a single row while the answer fades in. The row reads Worked for 18s when the turn reported how long it took, and Work details when it did not. Select it to review the thoughts and tool activity for that turn, in the order they happened. The reported duration stays the same when you reload the conversation. You can stop a running turn from the chat input. In a long conversation, Fimo may compact earlier context so the conversation can continue. Your visible chat history remains available. If a workspace problem stops a reply, Studio shows “Something went wrong.” Select Retry to try the request again.

​

Answer a question from chat

When your request has enough direction, chat starts the work without asking you to confirm routine details. If one missing answer prevents it from continuing safely, chat shows a short form and waits. The form stays pinned directly above the message box for as long as it is unanswered, so it does not scroll away while you read the conversation. Its place in the history reads “Waiting for your answer…” until you reply. You have two ways to answer:

• Submit the form. This sends your selections on their own. Anything you have started typing in the message box stays there, unsent.
• Send from the message box. Your message goes out together with whatever you have already picked in the form, as one turn. If you have picked nothing, it is an ordinary message, and sending it still closes the form.

Both appear in the chat history, so you can review them after a reload. A message sent with answers keeps your own words and the answers side by side. Select Minimize to fold the form down to a single line above the message box. It cannot be dismissed, because the work is waiting on it. The line shows the question you are on; select it, or press Enter with it focused, to open the form again. Your answers and the step you were on are kept, including while you move the chat between the side panel and the floating window.

​

Choose a model

When model choices are enabled for your project, use the picker beside the message box to choose Auto or a manual model. GPT-6 Astra is available for demanding reasoning and coding work. In a narrow chat, such as on a phone or a docked side panel, the picker shows only the model icon. Point to it to read the model name, or select it to change the model. Project members who can manage the project can open Settings → Models to choose which manual models everyone can use. Showing the picker is a personal browser setting, while the available model choices apply to the whole project. Chat may present project content, comparisons, assets, and analytics as interactive tables or visual summaries. These blocks use information available in the project. If the requested data or asset is unavailable, chat tells you instead of showing an estimate.

​

Use connected tools

Chat can use supported services that are ready in Connections. If a required connection needs setup, open Project settings and complete it before continuing. Production chat does not offer an in-chat setup handoff while Connections access is being rolled out.

​

Check remaining credits

If you have permission to view billing, your remaining credits appear beside the message box, including on phones and in a narrow side panel. Select the balance to see the breakdown of monthly, purchased, and earned credits.

​

Handle overlapping changes

If chat work overlaps with newer changes, Studio keeps the pending work available and asks you to resolve the conflict. Review both versions before applying a resolution. Resolving or merging project changes does not publish the live website. Publishing remains a separate action.

​

Use automation for repeatable work

Create an agent bundle when the same goal should run again with defined triggers and review rules. Use a scheduled command when one existing command should run on a cron.

​

What’s next