Mistral Vibe is the current name for Le Chat, which introduced Black Forest Labs image editing in July 2025. Use the same Mistral chat sign-in, or BFL's separate Kontext API for a named editing model. 1, 3, 8
What are the key facts about Le Chat image editing?
| Fact | Verified detail |
|---|---|
| Developer | Mistral AI provides Vibe, formerly Le Chat; its Le Chat image-editing partnership was with Black Forest Labs. 1, 8 |
| Released | Le Chat's advanced image-editing announcement: July 17, 2025. 1 |
| Type | Conversational assistant with a documented Le Chat image-editing integration. 1, 8 |
| Size or parameters | Not published for the image-editing integration in Mistral's announcement. 1 |
| License and access | App access now uses Vibe; the Le Chat image-editing announcement provides no downloadable integration weights. 1, 8 |
| Where it runs | Mistral's web and mobile apps; chat.mistral.ai remains the entry point. The direct Kontext API runs separately at BFL. 3, 8, 9 |
What image-editing workflow did Mistral introduce in Le Chat?
Mistral's Le Chat announcement describes generating an image, then requesting edits that preserve recognizable people, objects, and design elements. It presents revision as part of the conversation. 1
For example, start with a product scene and ask for a different setting. Then inspect the product before changing the lighting. This is a suggested working sequence, not a guarantee that every detail will survive.
Black Forest Labs documents related capabilities in FLUX.1 Kontext, including object changes, iterative edits, and replacement of text within images. Its direct API accepts an image and a written instruction. 3
Mistral's editing announcement identifies BFL as its partner without naming a Kontext endpoint or parameter count. BFL's direct documentation supplies an explicit model choice for an API integration. 1, 3
The useful unit of work is a requested change plus a preservation instruction. Try: “Make the mug pale blue. Preserve its handle shape, its position on the table, and the direction of the shadow.”
Before submitting that request, decide which of those details matters most. If the handle defines the product, judge it first. This gives you a concrete acceptance criterion instead of relying on whether the whole scene feels attractive.
What are the limits of Le Chat image editing?
The Le Chat editing announcement documents an app feature and supplies no integration weights. BFL publishes FLUX.1 Kontext dev separately for users who want a downloadable editing model. 1, 4
Mistral's launch article specifies no fixed image quota, output resolution, or underlying editing checkpoint. Use it for the documented editing method rather than an account allowance. 1
Mistral named FLUX Ultra for generation in February 2025 and announced BFL image editing in July. Its current documentation places the conversational experience in Vibe Chat. 1, 2, 9
Those sources do not specify Vibe's current image-model routing. Use the named BFL API below when your workflow requires explicit selection of FLUX.1 Kontext pro. 1, 2, 3, 9
For Kontext itself, the authors' technical report includes editing failures and identity degradation. That is a reason to review a result carefully, particularly when a face or object must remain recognizable. 5
Treat a successful example as evidence for that edit. Keep the original nearby and compare details after each revision. A pleasant new background should not distract from a changed face, missing component, or altered label.
For an exact product, list the required properties. Include the outline, visible controls, material, and printed text. Use that list to decide whether a generated variation is suitable for the intended use.
How do you access Vibe and use the FLUX Kontext API?
Open Mistral's chat app with your existing login. Mistral says Le Chat accounts and conversations carry over to Vibe, with the conversational experience available in Chat. 8, 9
For the documented Le Chat editing method, create an image and ask for one specific change. For current app navigation, follow Mistral's Vibe guide. 1, 9
Begin with a simple scene that makes the intended change visible. A single object against an uncluttered background is a useful test choice because you can state clearly what should change and what should remain.
Write the first instruction as a small revision: “Place this teapot on a linen-covered table. Keep its shape, glaze color, and handle unchanged.” Inspect the returned image before asking for another change.
If the result is acceptable, save it as a separate revision. If it fails your preservation checks, return to your original and narrow the request. Avoid combining several unrelated corrections before you have identified the actual failure.
For developers who need explicit model selection, BFL offers a separate Kontext API. Create BFL API credentials using its quick start, then use the editing documentation for request and polling details. 3, 6
This example submits a direct BFL request, independently of Vibe. Set BFL_API_KEY in your environment and use an accessible image URL that you control. 3, 6
import os
import requests
response = requests.post(
"https://api.bfl.ai/v1/flux-kontext-pro",
headers={"x-key": os.environ["BFL_API_KEY"]},
json={
"prompt": "Make the teapot pale blue; preserve its shape and position.",
"input_image": os.environ["INPUT_IMAGE_URL"],
},
timeout=60,
)
response.raise_for_status()
print(response.json()["polling_url"])
Poll the returned URL until the status is Ready, then retrieve result.sample. Handle failure statuses as described in the documentation; the submission response is a task record, not the completed image. 3
How does Le Chat compare with direct FLUX Kontext access?
| Route | Useful distinction |
|---|---|
| Le Chat / Vibe | Mistral documented conversational BFL image editing in Le Chat; the app is now accessed as Vibe. 1, 8 |
| FLUX.1 Kontext pro API | Explicit hosted model endpoint with documented request parameters. 3 |
| FLUX.1 Kontext dev | Downloadable editing model with a separate non-commercial weight license. 4 |
Choose between these routes based on the amount of control you need over the application. A conversation can suit exploratory revisions; an API suits a repeatable request format; local weights require their own deployment work.
The Kontext open-weight guide covers the local alternative. For broader visual direction, use the FLUX photography guide.
Keep your evaluation task the same across routes. Write down the source image, required edit, and preservation criteria before comparing outputs, so that a different request does not get mistaken for a better model.
Is Mistral Le Chat now called Vibe?
Mistral has renamed Le Chat to Vibe. The same chat.mistral.ai login remains available, and Vibe Chat retains the conversational experience. 8
Can I install Le Chat's image editor locally?
Le Chat's editing announcement supplies no downloadable integration weights. FLUX.1 Kontext dev is a separate downloadable BFL model with its own non-commercial license. 1, 4
Does Le Chat guarantee the same face after every edit?
Mistral's Le Chat announcement describes recognizable characters as an editing feature. Review each result; the separate FLUX.1 Kontext technical report documents identity-preservation failures. 1, 5
Should I use the API for an automated editing workflow?
BFL's FLUX.1 Kontext API offers a named endpoint and documented request handling. It requires BFL credentials and operates separately from Mistral Vibe. 3, 6
Sources
- Mistral's image-editing announcement
- Mistral's February Le Chat announcement
- BFL Kontext image-editing documentation
- Official Kontext dev model card
- Kontext authors' technical report
- BFL API account and key setup
- Mistral chat application
- Mistral's Le Chat to Vibe name change
- Current Vibe modes and access
Top comments (0)