On this page
Projects, conversations, and tasks
Understand project progress, nested conversations, standalone Chats, and the visible task lifecycle.
Projects keep related work together. Conversations are the ongoing discussions inside a project, while standalone Chats are available for work that does not need a project home. A task is a requested piece of work that can show progress, questions, permissions, and resulting changes.
Projects
Keep repository work and its related conversations together. A project can show progress and remain expanded as you move through the work.
Conversations
Open a child conversation for a distinct goal. Its entry remains under the project rather than being duplicated in the standalone Chats list.
Chats
Use the separate Chats area for a conversation that does not need to live under a project.
Choose Projects or Chats
Open the project that owns repository work, or use New chat from the standalone Chats area for an independent conversation.
Confirm the visible context
Check the project, workspace, selected files, attachments, and settings before sending a new task.
Follow progress and review the result
Use the conversation, project progress, plan details, visible activity, and checks to stay oriented from start to review.
What the navigation shows
A project can remain expanded while you move between its child conversations. The expanded state helps you return to the same work area, while a separate Chats area keeps standalone conversations discoverable. A child conversation is not also added as a duplicate standalone item.
| Visible state | What it means | Useful action |
|---|---|---|
| Project progress | The project shows current work and its child conversations. | Open the relevant child conversation. |
| Processing | The active conversation shows work in progress. | Wait, or send a focused follow-up if clarification is needed. |
| Updated recently | A relative time indicator shows recent conversation activity. | Open it to review the latest visible details. |
| Standalone Chat | The conversation belongs to Chats rather than a project. | Use New chat for another independent starting point. |
Keep plan detail connected
When a plan is available, its detail view can organize the work into Modules, Design Documentation, and Conversations. Read each area in the context of the project goal and check that the proposed work still matches the request.
When should I start another conversation?
Start another conversation when the desired outcome or context changes. If the new request is a follow-up to the same goal, keep it in the existing project conversation so the visible history remains understandable.
Read Past Work Reports to understand reusable earlier context, or Delegated work to follow visible grouped activity.