The Atlas Window
Export
The Atlas window keeps your conversation, project context, and generated results together. Open it from a supported product’s menu or docked panel.
The numbered callouts identify 1 the product header and 2 the conversation. The composer and request controls sit below the conversation.
Main controls
| Area | Purpose |
|---|---|
| Product header | Shows the product context supplied by the product integration. |
| Chat tabs and All chats | Return to earlier work or start a separate conversation. |
| Conversation | Displays your requests, answers, plans, progress, and generated file cards. |
| Composer | Enter a request or a slash command. Use Shift+Enter for a new line. |
| Attachment chips | Show context pinned to this chat. Remove a chip with its × control. |
| Paperclip | Attach files supported by the selected provider and model. Drag-and-drop and clipboard screenshot paste are also supported. |
| Model and effort controls | Choose the active provider, model, and reasoning effort. Provider settings do not switch this selection. |
| Settings button | Account, provider setup, project instructions, file-access settings, updates, and sign-out. |
Use /ask, /plan, or /gen to make your intention explicit. A natural-language request can also express that intent. See Commands and shortcuts for the full list.
Keep conversations focused
Continue in the same chat when asking about the previous answer, correcting a file, or building a plan. Start a new chat for an unrelated feature. Changing products creates a separate chat so a result is not continued under a different product API.
Attachments stay with their chat and are included again when you send another request. Remove stale context before changing the subject. A Unity object attachment is read again at send time; the snapshot is not a continuous recording of the scene.
Read a result
Expand a file to review the source before choosing its file action. A multi-file result has individual file cards and an Apply all action when the complete result is ready. A saved plan has its own Save plan… action.
Show work exposes request progress when available. It is useful for understanding whether Atlas is collecting context, generating, or validating; it does not replace reading the final result.
For supported failures, Atlas offers Retry request or Resume package build. Let Unity finish compiling or reloading before using them.
Persistence
Atlas saves bounded, project-local chat state across window closures and domain reloads. It is not an unlimited archive. Save useful plans as Markdown and generated code as ordinary project files. Clearing a chat removes its local working conversation; it is not a server-data deletion request.
Continue with Providing context or Generating and applying code.