Messages and conversations
Check model and workspace before starting. Give each conversation a clear objective; message history and project files are stored separately.
Open
Create and organize
Create/select conversations from the sidebar and group them by project. Item menus offer rename, pin and archive. Check model and directory after switching projects. Historical paths are not necessarily the active workspace. See the interface index.
Send a verifiable task
State objective, directory, constraints and acceptance criteria:
Fix the unresponsive homepage button in the current workspace. Read related files and explain the cause before editing. Keep the existing framework, run relevant checks and report results.
During execution
Inspect generation status, tool cards, questions and TODOs. Answer missing information and review approval targets. Completed TODOs still require artifacts and test evidence.
After execution
Verify files, command results or previews. See approvals and change review, and logs for request failures.
Interrupt and continue
After stopping, inspect completed edits and external operations. When a conversation is interrupted with no active run, use Continue to resume from its history. State completed work and the next objective.
Background commands or remote operations may keep running. Stopping chat is not a global process stop; see background work.
Other conversation operations
| Goal | Guide |
|---|---|
| Try another approach from history | Branches |
| Jump between turns or to the end | Navigation and gestures |
| Upload/reference files or compress history | Attachments and context |
| Divide work across models | Sub-agents |
| Organize completed tasks | Archive and restore |