Chats
Start conversations, understand context, and keep long-running work organized as your history grows.
Start from the right place
Most users begin a chat from an assistant, but chats also make more sense when you think about scope:
- use a normal chat for standalone work
- use a project chat when the conversation depends on project files or project instructions
- switch context carefully when moving between private work and organization work
What makes a chat easier to manage now
The app has added more chat management controls over time, including better reliability and organization features. Depending on your workspace state, you may see options such as favorites, archives, or search-oriented history tools around your chat list.
Treat the thread as working context
The chat thread keeps the evolving conversation state. That is useful, but it also means the thread can become cluttered if you keep changing goals.
Use mentions in shared contexts
Shared chats can support teammate collaboration as well as assistant responses. If your workspace uses mentions, they are best for team discussion inside a conversation without forcing every note to become an AI prompt.
Move to projects when context should persist
If a chat keeps depending on the same files, recurring instructions, or collaboration boundary, move that work into Projects.