LongCat-2.5-Preview does not inherit a browser login. To use it with signed-in project pages, connect a local agent to Tabbit Browser through Tabbit CLI, ask it to collect a few named sources, and stop at a draft review checkpoint. One naming detail matters: Meituan’s current API docs now list LongCat-2.5; the September Preview is a historical label. Check the live console before configuring a model route.
This is a local-client, model-route, and browser-connector workflow. It is not a claim of native Tabbit integration. Meituan’s September 25 changelog documents LongCat-2.5-Preview and compatibility with OpenCode and other agent environments. Its November 2 update announces LongCat-2.5. The current API quick start lists LongCat-2.5 at https://api.longcat.chat/openai and the Anthropic-compatible endpoint. Do not assume the Preview API name still works.
Key takeaways
The model interprets page content and prepares a draft; a local agent calls Tabbit CLI.
Check the model route, skill discovery, launcher connection, and site login separately.
Keep the first run read-only, include source URLs, and stop at a human review checkpoint.
OpenCode's
@tabbitsyntax is client-specific, not a universal command.
Check model and browser access
| Layer | What to check | Pass condition |
|---|---|---|
| Model | Official or API provider for LongCat-2.5-Preview | The model appears in your current account picker and tool settings are documented |
| Client | OpenCode or another host with local tools | It discovers the skill and can call the model route |
| Skill | ~/.agents/skills/tabbit/SKILL.md, invoked as @tabbit in OpenCode | The client confirms the skill loaded |
| Launcher | ~/.local/bin/tabbit-cli | It diagnoses and reaches the intended Tabbit environment |
| Website | The page you are authorized to read | You signed in within the Tabbit Browser environment the CLI reaches |
Check each layer separately. A model that answers a prompt does not prove it has browser tools. An open Tabbit tab does not prove the site session works. Use a client that can call the official LongCat API and run local tools. OpenCode can discover ~/.agents/skills/tabbit/SKILL.md; call the skill with @tabbit, then inspect the client to confirm it loaded. The LongCat model route, the skill discovery, the local Tabbit CLI launcher, and the website session are separate checks. In the current LongCat API selector, try the documented LongCat-2.5 name rather than copying an old Preview ID.
Choose text extraction or visual handoff
Use this workflow when a team needs a short project brief from an authenticated wiki, dashboard, or release page. The agent reads only pages you authorize and writes a separate named draft. It does not change the source workspace.
| Page evidence | What to pass to the model | When it fits | Control |
|---|---|---|---|
| Readable text and tables | DOM or OCR text extracted by the local agent | Labels, dates, and field values | Remove unrelated personal data; keep the URL |
| Layout or badge state | A cropped, redacted screenshot | Meaning depends on visual position or icon | Confirm the client supports image attachments |
| Ambiguous or conflicting state | A small text excerpt and one crop | One evidence type is inconclusive | Flag for review instead of guessing |
Use the current LongCat-2.5 API route if the provider console confirms access; treat LongCat-2.5-Preview as a historical name when the current docs do not expose it. For a different gateway, verify its exact model slug and tool-call support in that client. A million-token context window does not remove the need to limit sources and cite each statement.
Create a named draft and stop for review
Sign in to the site yourself in Tabbit Browser. Then ask your local agent to read the named pages, use the model to organize evidence, and save a separate draft. The names and rows below are an illustrative test fixture, not proof of access to your workspace.
Use @tabbit and Tabbit CLI to read only the three project pages I name below in my signed-in Tabbit Browser. Do not edit them. Create a separate document named "Release brief, draft 01". For each finding, include the exact source page title, URL, visible date, one short supporting excerpt, and whether it is fact or interpretation. Add a "Conflicts and gaps" section for dates or statements that disagree. Then write a brief of no more than 5 bullets using only supported claims. Stop and show the draft with its source links. Do not publish, share, or update the original pages. If the current LongCat route is unavailable, report that before using another model.Expected output: A separate brief with at most five sourced bullets and a conflict list. Every claim points to a page the reviewer can reopen.
Open the saved draft in a separate Tabbit Browser task tab, reopen every source link, and leave the document marked "Needs human review". You can keep using your other browser tabs while this review task runs.
| Draft status | Meaning | Next step |
|---|---|---|
| Supported | The page directly shows the field or state | Reopen the source and confirm it |
| Unclear | Related text exists but does not settle the claim | Keep it under "Needs human review" |
| Missing | The target field or record is absent | Do not fill it in automatically |
| Ready for review | Every claim has a URL and no write action ran | Review the full draft before deciding |
Install Tabbit Browser and connect the local agent
Start by installing Tabbit Browser, then sign in to sites you are authorized to use. The local Tabbit CLI entry on macOS/Linux is ~/.local/bin/tabbit-cli; an installed skill can live at ~/.agents/skills/tabbit/SKILL.md. OpenCode can invoke a discovered skill with @tabbit. Other clients may expose a skills list or use another syntax, so do not assume a universal /tabbit command.
Skill discovery, CLI access to the browser, and the site's existing login are separate checks. In a local test, a second named task reused a short-lived test session in the same Tabbit environment. That verifies session reuse in that tested environment; it does not prove native integration with LongCat-2.5-Preview. Task tabs are separate, so you can keep using other browser tabs while the agent works. For the connection boundaries, read Tabbit CLI guide, connect an agent to an existing browser, the first-task checklist, and the browser MCP vs CLI guide. For client-specific setup, see Codex CLI setup. For the browser itself, install Tabbit Browser; review browser-agent security and the browser-for-agent overview before granting tools.
Build a source-linked brief without editing the source pages
The two opened Reddit reports are anecdotal and come from one thread. X showed no post bodies, and YouTube results appeared without a verified comment. Treat them as stop-condition examples, not an evaluation of this browser workflow.
Based on the official material, LongCat-2.5-Preview's documented input and tool abilities can help organize evidence on the model side. A local Tabbit agent still opens the signed-in page. If your client cannot load the skill or send images, use text extraction and label it accurately; do not describe an unavailable capability as tested.
Try the read-only recipe on a non-sensitive test page first. Save it as "LongCat-2.5-Preview browser review, draft 01", verify every URL and status, then decide whether the same recipe fits a real workspace.
FAQ
Can LongCat-2.5-Preview use my browser login?
No. The model needs a local agent and browser connector. Tabbit CLI gives a supported local client access to Tabbit task tabs, where the site must already be signed in.
Which model name does the official API use now?
The current LongCat quick start lists `LongCat-2.5`. The changelog records `LongCat-2.5-Preview` in September and the current LongCat-2.5 release in November. Check the live console before using an older name.
Can I use this from OpenCode?
LongCat’s changelog says the Preview works with OpenCode and other agent environments. Confirm the API route and model name in your current OpenCode provider setup; availability can depend on account and region.
What does Tabbit CLI do in the workflow?
It connects a local client to task tabs in Tabbit Browser. It does not add the LongCat model to OpenCode or create a native Meituan-Tabbit integration.
Should the agent edit our shared wiki?
Start with read-only access and save the output in a separate draft. A person should check sources and approve a later edit separately.
How do I keep a long-context brief accurate?
Limit the source list, attach the URL and date to each claim, and flag disagreements. A large context limit is not evidence that every page was read correctly.