To let Mistral Vibe read a page that is already signed in, run the local Vibe CLI on the same machine as Tabbit, make sure Vibe can discover the Tabbit Skill or run the installed CLI, then verify access with a harmless read. Vibe’s open-source CLI and VS Code extension use a local runtime; the browser Vibe surface uses a cloud runtime, so a browser session on your laptop does not automatically transfer there. Tabbit CLI is a practical local browser handoff, not a native Vibe integration claim.
A Reddit user comparing local Vibe CLI with Vibe in the browser said the CLI “feels like a tool I can trust to get a job done end-to-end” in that setup (thread). That is one user’s report, not a general performance result. A Mistral employee replied that the team was aligning the harness and asked for a reproducible issue report. Use this as a reason to verify the actual runtime boundary, not as a speed claim.
Key takeaways
Use the local client and verify its actual Skill or shell access.
Check the signed-in page with a harmless read before asking for research.
Save an explicitly named draft and keep a human review checkpoint.
The browser path at a glance
| Surface | Where it runs | What to verify |
|---|---|---|
| Vibe CLI / VS Code | Local runtime on your computer | Can reach the local Tabbit CLI if shell access is allowed |
| Vibe in browser | Cloud runtime | Does not inherit a local Tabbit profile by implication |
| Web search | Search results and linked pages | Can find public sources, not operate your signed-in tab |
Verify the client before the session
Vibe-specific check, according to the official Skill documentation: confirm the executable is vibe, the folder is trusted, and the intended user Skill is discoverable from ~/.agents/skills/. Vibe supports /skill-name for a user-invocable skill; the official Tabbit quick-start documents /tabbit for supported agents, but do not assume Vibe has that alias. If discovery is absent, read the Skill path or invoke the installed ~/.local/bin/tabbit-cli from Vibe shell with the task name required by its CLI. Avoid confusing Vibe web Code sessions with local Vibe CLI.
A practical Tabbit workflow for this task
Use the API cross-check as a constrained task. Ask Vibe to open the internal documentation URL already logged into Tabbit, extract only endpoint names and required fields, and compare them with named files in the repository. Save api-doc-crosscheck-draft.md. Keep the internal fixture path and sample endpoint names illustrative; replace them with approved real inputs. Review every cited URL and symbol before the draft becomes a ticket or documentation change.
Use this prompt as a bounded template. Replace internal paths with approved inputs; the sample is not a claim that the named content exists.
Review the internal API documentation already open in Tabbit. Compare only the endpoint names and required fields against `src/api/client.ts` and `src/api/types.ts`. For each mismatch, return the documentation URL, file and symbol, evidence, and confidence. Do not edit files, submit forms, or publish. Save the result as `api-doc-crosscheck-draft.md` and stop for human review.A decision table for the handoff
| Stage | Proceed when | Stop when |
|---|---|---|
| Skill discovery | Vibe can load the local Tabbit Skill or shell command | Only /tabbit is assumed and the command is unknown |
| Session access | A read-only page check returns the expected page title | The page redirects to sign-in or shows an access error |
| API comparison | Each claim maps to a doc URL and repository symbol | The source page or API version is unclear |
Related setup guides
For another client, the same order applies: discover the client skill, check local launcher reachability, verify the signed-in host, then save a reviewable draft. See the Tabbit CLI guide. Start with a test page you can inspect manually, and keep the site action read-only.
FAQ
Does Mistral Vibe have native Tabbit integration?
This workflow uses the local Tabbit CLI through a Skill or shell. Do not call it native unless Mistral and Tabbit document a supported integration.
Can Vibe browser use my local login?
Not by assumption. Mistral describes a cloud runtime for browser Vibe and a local runtime for CLI/VS Code. Verify the environment that owns the session.
What command invokes a Tabbit Skill?
Vibe documents `/skill-name` for user-invocable skills. Check that the Tabbit Skill is discovered before relying on an alias.
How do I check private API documentation?
Use a read-only task, list the exact page URL and repository symbols, then check each citation yourself.
Can the agent edit or publish the draft?
This workflow stops at a named review draft. Require a human to approve any write or publication.
What if Vibe runs remotely?
A remote runner cannot be assumed to reach your desktop Tabbit session. Use only a separately supported local handoff.