Organize with Projects

Updated November 2, 2026 — Le Chat is now Vibe. As of May 28, 2026, Le Chat is now Vibe (still at chat.mistral.ai): a single agent for work and code, carrying over your conversations, settings, and subscriptions. The legacy Le Chat experience remains accessible in Chat mode; in Work mode, agents are now skills (invoked with @), memories are the knowledge base, and deep search is the Deep Research skill. Plans are now called Mistral Free, Pro, Team, and Enterprise. This lesson now uses the name Vibe; some menus described here may have changed names or locations.

Contextual folders for your projects

After a few weeks of heavy use, Vibe’s sidebar starts to look like a messy drawer. The Projects feature tackles this mess by grouping your conversations, documents, and instructions into dedicated spaces, organized by project, client, or topic.

A project isn’t just a filing folder; it’s a smart folder that preserves context. The reference documents it contains and the instructions you define there automatically apply to every conversation within it. You no longer have to reexplain your situation in every new exchange.

Create a project—and know when to

Creating one takes less than a minute:

1. Click New Project in the Vibe sidebar
2. Give your project a descriptive name (for example, “Q2 2026 Marketing Strategy”)
3. Add an optional description to clarify the objective
4. Configure specific instructions if needed

The real question is when to open a project instead of a standard conversation. The trigger: a set of related tasks that would benefit from sharing a common context. A new client or contract, a marketing campaign, a software development project, long-term documentary research, event preparation—all justify a dedicated space. A one-off question does not.

The document library

Each project can host reference documents that Vibe automatically consults during your conversations. Accepted formats cover most of what circulates in a business: PDFs for reports, contracts, and specifications; text files for notes, technical specs, and procedures; CSV or Excel spreadsheets for data; images for mockups, diagrams, and screenshots.

These files become the project’s knowledge base. If you uploaded a client’s specifications and ask, “What deadline did they commit to for phase 2?”, Vibe finds the answer in your document instead of serving up a generalization.

One habit to adopt, however: prune. Too many documents dilute the relevance of responses because the model has to arbitrate between sources that don’t all relate to your question. Keep only what serves the current project.

Project instructions

Instructions frame Vibe’s behavior for the entire project, like a persistent “system prompt” you no longer have to repeat. “Always respond in English in this project,” “Use precise legal vocabulary,” “Every response must include references to relevant law articles,” “Adopt our brand tone: professional but accessible”—these are all instructions that apply to the first conversation just as they do to the thirtieth, with each automatically inheriting the defined documents and framework.

A consistent naming convention will also save you time once you have ten projects or more. Sort by client (“Client — Acme Corp”), by topic (“Watch — AI and Regulation”), or by deadline (“Product Launch — March 2026”), but stick to a logic. When a project ends, archive it rather than deleting it: you keep the history and documents for future reference.

What a well-set-up project looks like

For a response to a request for proposal, the project hosts the client’s specifications, the scoring grid, references from similar projects, and the sales brochure. The instruction sets the tone: “Respond in a formal style. Every response must demonstrate our expertise and our compliance with the selection criteria.” You then open one conversation per section of the request for proposal.

For a mobile app development project, the library gathers functional specifications, UI/UX mockups, API documentation, and the style guide, while the instruction sets the technical framework: “The main language is Kotlin for Android and Swift for iOS. MVVM architecture.” One conversation per feature or per sprint is enough to keep exchanges readable.

For internal training, upload existing materials, previous evaluations, and learning objectives, then specify the audience: “The target audience consists of non-technical staff. Use concrete examples from daily professional life.” One conversation per module, and your design moves forward without you having to remind the model of the learners’ level every time.

Test the mechanism on a current topic: create the project, upload two or three documents, write its instructions, then ask a question whose answer can only come from your files. If Vibe cites them, the configuration is good.

Key points to remember

• Projects organizes your conversations by topic with a shared context
• Each project can contain reference documents and specific instructions
• Uploaded documents constitute the project’s knowledge base
• Project instructions automatically apply to all its conversations
• Adopt a consistent nomenclature and archive completed projects