LongCat 2.0 is worth a pilot when you need long context, open weights, or a low-cost agent route. It is not a simple “cheap frontier model” decision: the route, tool wrapper, data terms, and review loop matter as much as the token price.
The dated anchor is the 2026-06-30 LongCat announcement and the model card checked on 2026-09-20: 1.6T total parameters, about 48B active, 1M context, and a MIT license. The OpenRouter snapshot checked the same day showed $0.30/$1.20 per million input/output tokens. Those are different facts from a Tabbit session, a self-hosted machine, or a first-party account. Start with the LongCat 2.0 model page, then choose the route that matches your risk and workload.
Key takeaways
LongCat 2.0 publishes open weights, a 1M context window, and deployment examples for Transformers, vLLM, and SGLang.
The official benchmark table is useful for scope, not a neutral leaderboard: the publisher supplied the harness and corrected some task sets.
OpenRouter showed a low dated price, but provider telemetry, cache terms, and data policy are separate questions.
Community reports describe a capable, coherent workhorse and also buggy coding, repetition, and integration friction.
Keep a small repository fixture, a stop condition, and a human review step before putting the model into an agent loop.
LongCat 2.0 at a glance
| Question | Evidence checked 2026-09-20 | Decision boundary |
|---|---|---|
| What is it? | Sparse mixture-of-experts model; 1.6T total and about 48B active | Active parameters do not predict your latency or total bill by themselves. |
| Context | 1M tokens in the official card and OpenRouter snapshot | Provider, client, prompt serialization, and memory strategy can reduce the usable window. |
| License and weights | Official card lists MIT and downloadable weights | You still own hardware, serving, upgrades, monitoring, and security. |
| Coding/agent signal | Official Terminal-Bench 2.1 70.8 and SWE-Bench Pro 59.5 | The numbers use the publisher's harness and do not guarantee your repository or tools. |
| API snapshot | OpenRouter displayed $0.30 input / $1.20 output per million, AtlasCloud only | Price and availability are dynamic and are not a first-party SLA. |
| Browser route | Tabbit can be evaluated as a separate product session | No authenticated LongCat task was run for this article. |
Read the agentic browser explanation before treating a browser assistant as an API wrapper. If you need a wider browser comparison, use AI browser comparison, and use best practices for Tabbit Browser for the surrounding workflow.
What changed in the model
The technical announcement describes LongCat Sparse Attention (LSA) with streaming-aware, cross-layer, and hierarchical indexing. The card also describes a 135B-parameter N-gram Embedding component and training on hundreds of billions of 1M-context tokens. In practical terms, the design is aimed at keeping very long codebases, research material, and agent traces usable without treating every token as equally expensive to attend to.
The official examples are unusually operational: Claude Code, OpenClaw, and Hermes are named integrations, while the card shows Transformers, vLLM, and SGLang commands. That is evidence that the authors care about repository editing and tool use. It is not a promise that every harness will parse the same tool-call wrapper. The LongCat prompts page is a better place to inspect task material; this overview does not copy a system prompt.
Official results, with the harness beside them
| Benchmark | LongCat 2.0 score |
|---|---|
| Terminal-Bench 2.1 | 70.8 |
| SWE-Bench Pro | 59.5 |
| SWE-Bench Multilingual | 77.3 |
| FORTE | 73.2 |
| BrowseComp | 79.9 |
| RWSearch | 78.8 |
| IFEval | 90.0 |
The LongCat card says unstarred values were measured in-house under a unified harness; starred comparator values came from external reports. The technical post says Terminal-Bench used Claude Code in an 8c16g sandbox, temperature 1, top-p 0.95, top-k -1, and a six-hour agent timeout. The SWE-Bench runs used Claude Code in a 4c8g environment and note that problematic tasks were corrected. FORTE used 15 enterprise occupations, 45-minute tasks, a 2-CPU/4GB environment, 500-second API timeouts, and at most ten retries. Those details make the claims more useful, but they still do not turn vendor results into an independent replication. See the LongCat review collection for evidence records with their individual conditions.
Access is four different decisions
Self-hosted weights
The MIT-licensed card includes Transformers, vLLM, and SGLang deployment paths. That is the clearest route when code and documents cannot leave your controlled environment. It also transfers the hard parts to you: GPU or NPU capacity, quantization, batching, upgrades, observability, and incident response. A model card is not a hardware quote. Treat the browser automation guide as a workflow reference, not as a substitute for serving design.
First-party or regional API
The eesel review, last edited 2026-08-04, describes a low promotional route and regional payment constraints, including scheduled token-pack availability and short expiry. Because that page is a secondary snapshot rather than a newly reopened first-party invoice, use it to identify questions: region, payment method, expiration, invoicing, retention, training use, residency, and SLA. Ask the provider for the current answers before sending enterprise data.
OpenRouter
The OpenRouter page checked on 2026-09-20 showed $0.30 per million input tokens and $1.20 per million output tokens, with $0.006 cache reads, 1M context, and AtlasCloud as the listed provider. It showed P50 latency around 2.35 seconds, about 38 tokens per second, and dynamic uptime/availability telemetry. Those numbers are a route snapshot, not a model guarantee. Provider billing and provider data handling remain separate from the published weights.
Tabbit
Tabbit is a product session, not an automatic pass-through of your OpenRouter or first-party invoice. A selector, quota, context policy, and data contract can change independently. This research did not run an authenticated LongCat task or capture qualified screenshots, so the article does not claim LongCat quality, latency, availability, or pricing inside Tabbit. Check the live account before planning a workflow.
What users report outside the score table
The community evidence is directional rather than a benchmark. A July r/vibecoding post described about 50M tokens for roughly $2 and a cache-heavy 27M-token task; account, currency, and invoice details were not supplied. An August r/SillyTavernAI user described a week of non-thinking role-play with faithful instructions and coherent prose, but persistent repetition in long stories and concern about the provider’s phone requirement. An X post described the strongest visual-physics result in one shared physics-plus-coding fixture across three models; the prompt and scoring rubric were not published.
The eesel review also quotes one Hermes Agent user who liked planning and long-context app work, and another who found coding buggy and preferred DeepSeek. Taken together, these reports justify a narrow pilot. They do not support a universal ranking. Keep deep research tool-use patterns separate from a model’s marketing score, and record your own accepted output rather than rewarding fluent drafts.
Unknown risks before a serious deployment
The reviewed public material did not establish a complete current policy for retention, training on prompts, data residency, or SLA. “Not found” is not proof that a provider has no policy.
Some harnesses may not recognize the
<longcat_tool_call>wrapper described in the eesel integration discussion. Test tool parsing and error recovery before allowing write actions.The official search and research demos do not guarantee English routing, source quality, or citation completeness. One community report described an English question receiving a Chinese answer.
Open-weight serving can expose operational costs that a per-token API price hides: memory, electricity, staff time, failed runs, and security controls.
A 1M context maximum does not mean a 1M context prompt is affordable, useful, or stable. Measure retrieval, attention, latency, and accepted answer quality on your own corpus.
Scenario self-check
| Your situation | A sensible first test | Do not assume |
|---|---|---|
| ML or platform team with GPUs | Serve a quantized build in a disposable environment and compare throughput, memory, and output checks | The card’s deployment snippet is a capacity plan. |
| Coding-agent user | Give one small repository task with a fixed diff and tests, then inspect every tool call | 59.5 on SWE-Bench predicts your stack. |
| Research or RAG team | Use a dated document set, citation rubric, and language check | 1M context removes retrieval and source-quality problems. |
| Creative or role-play user | Run the same scene for short and long continuations and count repetition | One enthusiastic week-long report generalizes. |
| Privacy-sensitive enterprise | Obtain current retention, training, residency, and SLA terms in writing | A missing FAQ sentence is a privacy guarantee. |
| Short chat and low budget | Compare a small task at the actual provider with a fallback model | A low input rate controls output, retries, or tool costs. |
A practical next step with Tabbit
If your account exposes LongCat 2.0, use a reversible browser task: open one public documentation page, ask for a five-point extraction with source links, and verify each link manually. Do not grant write permissions or upload confidential material on the first run. Save the model ID, date, route, context size, latency, tool events, retries, and accepted corrections. If the selector is absent, that is a product-availability result, not a reason to substitute an API test.
Tabbit BrowserVerdict
LongCat 2.0 is a credible workhorse candidate for long-context coding, research, and agent pilots. The open weights and dated provider snapshot make experimentation accessible, while the official scores show useful task coverage. The decision should stop at pilot until you verify tool-call compatibility, accepted-output quality, and the data terms of the route you actually use. Choose self-hosting for control, an API for managed operations, OpenRouter for a clearly priced provider snapshot, or Tabbit only after checking the live product surface. Do not let the $0.30 input line stand in for the whole operating contract.
Sources
FAQ
What is LongCat 2.0?
LongCat 2.0 is Meituan's MIT-licensed sparse mixture-of-experts model. Its model card reports 1.6 trillion total parameters, about 48 billion active per token, and a 1M-token context window.
Is LongCat 2.0 open source?
The official Hugging Face card publishes weights under the MIT license and documents Transformers, vLLM, and SGLang deployment. Open weights do not make inference hardware, operations, or support free.
How much does LongCat 2.0 cost?
The OpenRouter page showed $0.30 per million input tokens and $1.20 per million output tokens on 2026-09-20. That is a provider snapshot, not a universal first-party price or a Tabbit subscription quote.
Is LongCat 2.0 good for coding agents?
The official table reports 70.8 on Terminal-Bench 2.1 and 59.5 on SWE-Bench Pro under the publisher's stated harnesses. Community reports are mixed, so test a reversible repository task with your own tools and acceptance checks.
Does LongCat 2.0 protect API data?
The reviewed public route material did not establish a complete retention, training, residency, or SLA policy. Confirm the current provider terms before sending confidential code or documents.
Can I use LongCat 2.0 in Tabbit?
This article did not run an authenticated LongCat 2.0 Tabbit task. Check the live selector and account terms; do not assume API billing, quota, or availability carries over.