Working with chats
Start conversations, find previous work, rename chats, and manage your chat history.
A chat holds one conversation with a coding agent. Each chat belongs to a project and has its own model, permissions, and conversation history. Use separate chats for tasks you want to return to independently, such as fixing a bug and reviewing a feature.
Start a conversation#
- Select the project tab you want to work in.
- Click New chat in the left toolbar.
- Check the model and permissions below the message box.
- Describe the task and submit your message.
New chats use your default model settings. An empty draft may be reused when you click New chat again before sending a message. Once you send a message, the conversation appears in the project's history.
For a useful first message, give the agent an outcome and a way to check it. For example:
Find why the settings form loses its values after a refresh. Fix the cause and explain how you verified the fix.
Use file references and attachments to point to relevant code or an image.
Return to a conversation#
- Click Chat history in the left toolbar.
- Browse the current project's chats, with recently updated conversations first.
- Enter part of a chat's title in Search history to narrow the list.
- Select the conversation to open it.
History search filters this project's titles. To search titles and message text across projects, click Search chats in the top bar (default Command+Shift+F on macOS or Ctrl+Shift+F on Windows/Linux). Results include local projects and connected SSH hosts. Selecting an archived result restores it; selecting a closed project's chat reopens that project.
If a host cannot be searched, reconnect it and try again. Narrow the query when results are truncated. You can also manage older conversations in Archived chats.
When multi-chat is enabled, selecting a conversation can bring it into the side-by-side layout. With multi-chat disabled, you view one conversation at a time.
Rename a chat#
Dream can generate a title after a conversation starts. To give it a more specific name, open the chat's … menu and choose Edit, or double-click the title. In Edit chat, enter the name and click Save. Use Cancel to keep the existing name.
Names such as “Fix settings persistence” and “Review settings tests” are easier to distinguish than several chats named after the same project.
Follow work in progress#
Enable Desktop notifications under Settings → General → Chat messages to get an alert when a chat finishes, fails, or needs input while Dream is in the background. Click a notification to open its chat. Notification sound is a separate option and can play even while Dream is focused.
A loading spinner identifies chats that are streaming a response. When you send a message, Dream scrolls it into view.
While an agent responds, the chat shows its progress and tool activity. Open tool details to inspect commands, file reads, or changes. When the agent supplies a task list, the task control beside the message box shows its progress.
History and project tabs include status indicators for work that is processing or has finished; project tabs can also indicate that an agent is waiting for your answer. Select the project and open the conversation to read its latest message. Use the stop control in the composer to end a response. Stopping a response does not undo file changes already made.
Replies run on the project's host, not in the window. If a client disconnects while a reply is running, the reply continues, and the chat reconnects to it automatically.
After a reply finishes, use View file changes from this reply in its footer to see the files it changed and restore any of them.
Queue messages#
You can send more messages while a reply is running. Type in the message box and send; the stop control becomes the send control while the box has text. Dream adds the message to the chat's Queue and runs it after the current reply, using the model shown beside it. Queued messages are saved on the host, so they survive restarting Dream.
The Queue appears above the message box while messages are waiting or a run needs attention.
| Control | What it does |
|---|---|
| Pause queue | Holds queued messages; the current reply still finishes |
| Resume queue | Continues with the next queued message |
| Cancel | Removes a message that has not started |
| Retry | Runs a Failed or Interrupted message again |
| Remove | Dismisses a Failed or Interrupted message |
Stop ends the current reply, along with any tasks it delegated, and holds the rest of the queue. Sending a new message resumes a paused queue and dismisses failed or interrupted messages.
A reply is Interrupted when its host stops before it finishes, for example during an update. The queue is paused afterward. Read the reply before choosing Retry, because the agent may already have changed files.
Close, archive, or delete?#
| Action | Result | How to return |
|---|---|---|
| Close a chat column | Removes it from the multi-chat layout | Open it from Chat history |
| Archive a chat | Removes it from active chat history | Restore it in Settings → Archived chats |
| Delete an archived chat | Permanently removes the chat and its messages from Dream | It cannot be restored through Dream |
Closing a column is useful when you need more space. Archiving is useful when a task is finished. Neither action reverts the agent's changes to project files.
To try a different approach while keeping the conversation so far, branch from a message. To prepare a task for later, save a prompt in Stash. For instructions you want to reuse across projects, create a reusable prompt and run it from the composer's + → Run prompt menu. Type $ to invoke an agent skill.