Projects and chats
Find saved work, keep discussions separate, and open the right workspace.
Projects contain an application, its development environment, build history, settings, and production relationship.
Chats contain standalone Ask conversations. They are useful when you want advice or product planning without changing an application.
Projects and chats can begin from similar ideas, but they preserve different kinds of work. A project owns an app and its development history. A standalone chat owns a conversation. Keeping that distinction clear prevents an early discussion from being mistaken for an application and helps you return to the correct place later.
Use descriptive names as soon as an idea becomes recognizable. The title appears in recent lists, search, and account pages, so a meaningful name saves time for everyone on the team.
Example: “Should we offer customer self-service?” is a useful Ask chat. “Customer self-service portal” is the project created after the team approves that direction.
Recent items
Studio home shows compact recent Chats and Projects. On mobile, expand either section to reveal its recent items. The heading links open the complete list.
Recent items are shortcuts, not the complete account history. The subtitle identifies whether an item is an Ask conversation or a project ready to continue. If two titles look alike, use that label and the icon before opening one.
Example: A recent conversation called “Wholesale pricing” may contain planning only, while a project with the same words contains the working quote portal. Open the project when you expect Preview and Build controls.
Project list
Console → Projects provides the account-wide view. Open a project to return to its Chat/Preview workspace. Status and last activity help distinguish active development from older work.

A Draft label means the project is still in development. Live status and Domain tell you whether customers can reach a published release.
Search by the language your team actually uses: project name, owner, or connected domain. The cards help answer three separate questions—what is being built, who is responsible, and whether a production release exists. A polished thumbnail does not by itself mean the app is published.
Deletion is permanent and broader than closing a conversation. Confirm that the project, saved versions, and development history are no longer needed. A separately owned domain may remain in the account and should be parked or reassigned intentionally.
Example: A card can show a finished-looking CRM preview while its status remains Draft and its domain says Not connected. Customers cannot use it until an authorized person publishes it.
Chat list
Console → Chats contains Ask conversations. A conversation can be copied or deleted according to the available controls and your permissions. Delete requires confirmation because it removes saved history.

Search conversations by topic, then use the filters to separate independent advice from project work. A project chat can influence its attached app when you use Build. A standalone conversation remains discussion until you deliberately turn the agreed idea into a project.
Copy is useful when you want a separate discussion that begins with similar context. Delete removes the saved conversation, so use it for disposable or incorrect chats rather than as a way to organize important decisions.
Example: Filter to Project chats when you need the conversation that produced version 6 of the Retail CRM. Filter to Conversations when you need the earlier discussion comparing CRM permissions.
Turn an idea into a project
If an Ask conversation reaches an implementation decision, use its build action. Mango9 carries the relevant conversation forward so the project can enter the normal brief/build path.
Review the direction before making the transition. The conversation may contain alternatives you rejected, so the final message should identify the chosen outcome and any firm boundary. The new project can then ask brief questions and build from the decision without requiring you to paste the full chat.
Example: “Build the appointment-reminder option we chose: email 24 hours before the visit. SMS and customer accounts are out of scope for the first version.”
Naming
Rename projects and conversations so they describe the outcome, not the first message. “Wholesale quote portal” is easier to find than “hello” or “new project.”
Include a client, department, or purpose when your account contains similar work. Avoid putting passwords, private customer records, or temporary status notes in a title because names are shown throughout the workspace.
Example: Prefer “Northstar sales CRM” and “Northstar support portal” over two projects both called “Northstar app.”