To turn signed-in team pages into a source-linked note with Mistral Large 4, install Tabbit Browser and run Tabbit CLI from a local agent that can select the model. Check the Mistral API route or your own checkpoint first. Then let the agent read the pages in a separate task tab and bring the draft back for you to edit. Mistral model documentation
A user in the Mistral Vibe community wrote that Large 4 was not available in their Vibe interface and they had to add it manually in configuration. That report is a useful reminder to check the client’s model selector before building a workflow. Below, the example reads team reference pages and prepares a review draft. It does not publish or modify source pages.
Key takeaways
The model is only one part of browser use. The runtime, agent client, local browser tool, and site login each need a separate check.
Use Tabbit Browser for the signed-in workspace, and Tabbit CLI from a local agent for controlled page reads.
Keep the first run read-only. Name its output and ask a person to review it in the browser before saving or sharing.
A remote agent needs a separately supported local handoff; it cannot inherit a desktop session by assumption.
Confirm where Large 4 is available
| Check | What to verify | Stop if |
|---|---|---|
| Model availability | Selected client actually lists the model, or your local runner loads the checkpoint | Model is absent or runner fails to load |
| Tool execution | Client can run the Tabbit Skill or installed CLI locally | Only cloud tools are available |
| Browser ownership | Tabbit Browser is on the same device as the local agent | Agent runs remotely without a supported handoff |
| Site session | The intended Tabbit profile is already signed in | Page asks for login or displays the wrong account |
Skill discovery is separate from launcher reachability. A client might recognize /tabbit but still lack shell permission; a working tabbit-cli binary does not prove the model is selectable. Check both. Some clients use /skills; Pi uses /skill:tabbit. Use the syntax shown by your client.
According to the official model documentation, Mistral published Large 4 as a public preview on Oct 6, 2026, first through Studio/API; the official model docs now list open weights and function calling. Treat the route as either an API model or a downloaded checkpoint, depending on actual serving setup. The API model ID is mistral-large-4. Do not claim that any specific agent client lists it without checking.
Drafting a team note with Mistral Large 4
Pick the route your client actually supports. For the API, confirm that it accepts the documented mistral-large-4 model ID and the tool-call schema your agent uses. For open weights, confirm that your local runner supports the checkpoint and that the agent can reach that runner. The model provider does not automatically provide Tabbit CLI.
Ask for a draft with citations, not a polished answer. Keep the first pass to a pair of reference pages and one output document. Name the draft, list every source URL and date, then open it in Tabbit Browser. Compare the claims against the source pages before you save it anywhere.
A Vibe commenter said a fresh CLI install exposed the preview model without extra configuration, which differs from the original poster’s setup. This is why setup instructions age quickly: client version and model route matter. The report does not establish current Vibe support for every account.
Do not ask the model to write into a shared page on the first run. If a team document needs an update, copy the reviewed draft into the editor yourself and follow your normal approval process.
Deployment decision table
| Task | Model-specific question | Browser check |
|---|---|---|
| Draft from team references | Does the chosen client expose Large 4 by API or local runner? | Compare every sentence with its cited page |
| Run the checkpoint locally | Can the available machine load the selected quantization? | Confirm the runner owns the browser tool separately |
| Use an API client | Are the model ID and tool schema supported? | Verify local handoff and login independently |
| Publish a document | Has an editor accepted the draft? | Keep publish controls out of the first run |
Mistral’s preview API and later open-weight distribution are different deployment choices. Neither changes the browser steps below.
Ask for a note with page-by-page sources
This asks for a named draft, source links, explicit uncertainty, and a stop before any write action.
Read the two team reference pages I name. Extract each claim, its source URL, and any date shown. Draft a short internal note titled “Release notes review — draft”. Use only facts visible on those pages. Mark conflicts as “needs review”. Do not click buttons that save, send, publish, or change records. Return the draft text and a source checklist.A practical browser option: Tabbit Browser
Tabbit Browser is useful when the task depends on a website where you are already signed in. Install it, sign into the target site in the profile you intend to use, and let the local agent call Tabbit CLI for a bounded read. The CLI works in a separate task space, so you can keep using your other tabs while it gathers the requested fields. Review the draft in the browser before any write action.
This is a workflow recommendation, not a claim that the model ships with Tabbit integration. The model provider, the agent client, and the browser bridge are separate components. Verify the model selector and local tool permission in the client you choose. Tabbit cannot make a cloud-only runner local.
For setup details, see the CLI guide, existing-browser connection guide, first task checklist, MCP versus CLI guide, Codex setup, agentic browser explainer, browser agent guide, and Tabbit Browser overview.
“For me, Mistral Large 4 is still not an option in Mistral Vibe CLI and I have to manually add it via the config.”
u/MiuraDude on Reddit. This is an individual report, not evidence of a general capability or availability.
“On a fresh install of Vibe CLI yesterday I got the option to use ML4 Preview directly without any more config though.”
u/Accordeon-Foireux on Reddit. This is an individual report, not evidence of a general capability or availability.
Sources and community notes
According to the official model documentation, Mistral published Large 4 as a public preview on Oct 6, 2026, first through Studio/API; the official model docs now list open weights and function calling. Treat the route as either an API model or a downloaded checkpoint, depending on actual serving setup. The API model ID is mistral-large-4. Do not claim that any specific agent client lists it without checking.
Sources
FAQ
Does selecting the model give it browser access?
No. The client must connect browser tools to the intended profile. Verify access with a harmless read.
Can it reuse my existing website login?
Yes, when local Tabbit CLI connects to the Tabbit Browser environment where you signed in. Never share credentials with the model.
Is `/tabbit` available in every client?
No. Skill discovery varies. Some clients use `/skills`; Pi uses `/skill:tabbit`. Check the client’s actual syntax.
Can a cloud runner reach my desktop browser?
Only through a separately supported local handoff. Do not assume a cloud runner can reach your device.
Should I let the agent publish its draft?
Keep the first task read-only. Review the named draft in Tabbit Browser before any write.
What if my client cannot select this model?
Check the client’s model list, provider settings, and runner support. Public availability does not prove client compatibility.