LongCat-2.5 Released

Native multimodality for agentic tasks — 1.6T parameters, ~48B active per token, vision folded into the backbone, and long-horizon RL at scale

Announced November 1, 2026 · Available on the LongCat API Platform November 2, 2026

What Was Announced

The LongCat team released LongCat-2.5, a native multimodal model aimed squarely at long-horizon agentic tasks. Total parameters stay at 1.6 trillion with roughly 48 billion activated per token — the same envelope as LongCat-2.0. What changed is the training target: 2.0 was built for agentic coding, 2.5 is built for agents that finish projects, and it can see.

Three shifts define the release:

  • Vision moves into the backbone. Images become multi-level discrete tokens, so text and vision share one token stream and one objective — no separate encoder adapter pipeline.
  • RL gets long. More long-horizon trajectories in long-sequence training, plus large-scale long-horizon reinforcement learning across synthetic data, constructed environments, and multiple harnesses.
  • Infrastructure absorbs the cost. Long-context training and W4A4 inference are optimized on domestic accelerators, with train–inference numerical consistency enabling efficient large-scale rollout.

The combination — native visual understanding meeting agentic coding — is what the team calls visual coding: reading a screenshot, a rendered viewport, a chart, or a UI and acting on it inside the same reasoning loop that writes the code. That is what makes the creative-design and 3D demos possible rather than aspirational.

Timeline: Preview to GA

Date Milestone
June 30, 2026 LongCat-2.0 released as open weights (MIT), the direct predecessor
September 25, 2026 LongCat-2.5-Preview on the LongCat API Platform: 1.6T MoE, ~48B active, 1M context, 128K max output, new image understanding, dual OpenAI/Anthropic protocols
November 1, 2026 LongCat-2.5 announced with full technical report: discrete visual tokens, agentic RL scaling, W4A4, complete 33-benchmark evaluation
November 2, 2026 "LongCat-2.5 Now Available" in the LongCat API Platform changelog

The preview drew attention for a non-technical reason too: OpenCode listed LongCat-2.5-Preview as a free model for two weeks with zero data retention, which gave Western developers a low-risk way to test a Chinese frontier model inside an existing agent workflow.

1. Native Visual Representation

LongCat-2.5 represents visual signals as multi-level discrete tokens so the backbone processes visual and textual inputs in one unified token format. The design has three parts.

Discrete native-resolution vision transformer

To reach a token-level abstraction for visual primitives analogous to language modeling, the team applies residual vector quantization (RVQ) to native-resolution features from a Semantic-and-Aligned Encoder (SAE), following the method established in LongCat-Next. Multi-level RVQ is the specific fix for visual discretization's information bottleneck: one codebook level preserves semantics, the residual levels preserve detail.

Offline visual token preprocessing

Because the tokenizer is fixed, visual token IDs are precomputed and cached offline. The backbone therefore only ever sees pretokenized sequences. In practice this simplifies long-sequence packing and partitioning, improves load balancing across distributed training, and removes the vision encoder from the training graph entirely — which is what makes the parallelism story later in this post tractable.

Native visual representation

Visual codebook embeddings are learned jointly with the backbone. On a smaller MoE probe model with about 3B average activated parameters, t-SNE visualizations show visual and textual embeddings interwoven rather than clustered apart — an early signal that both modalities land in a shared semantic space.

2. Scaling Agentic RL for Long-Horizon Tasks

The team frames RL scaling as the key lever for pushing intelligence further, and they scale the pipeline on four axes simultaneously: data, environments, algorithms, and harnesses.

Large-scale data synthesis and environment construction

For coding tasks the model must learn from real environment feedback, so the pipeline builds environments, not just prompts. Filtered GitHub pull requests and linked issues are annotated by agents, environments are synthesized, and each task is validated with fail-to-pass (F2P) and pass-to-pass (P2P) tests. Real internal coding tasks with their own acceptance criteria broaden coverage of ordinary engineering work.

Verification is treated as a moving target. Live rollout pass rates drive relabeling and filtering, while offline analysis of false-positive and false-negative trajectories continually corrects and extends F2P tests — improving coverage of the task description rather than merely matching the diff that happened to merge.

Asynchronous RL and stability

Long-horizon tasks produce a heavy-tailed rollout distribution. LongCat-2.5 uses asynchronous partial rollouts: each RL step maintains an oversampling ratio, and when a batch is filled, in-flight trajectories are interrupted, saved, and resumed in the next sampling phase. Oversampling increases with precomputed pass rates, and zero-gradient groups — where every rollout succeeds or every rollout fails — are filtered out so the effective gradient signal stays meaningful.

The cost of asynchrony is staleness: tokens in one trajectory may originate from different historical checkpoints. The fix is twofold — clip the discrepancy between sampling-policy and current-policy log-probs, and rescale each token's gradient contribution by its accumulated historical discrepancy, bounding the gradient bias staleness would otherwise introduce. Numerical differences at equal weights are handled by the train–inference alignment described below.

Reward hacking and output behavior

Task environments are hardened during training: network access disabled, git history and cached files removed, and an LLM judge auditing trajectories for exploits. Behaviorally, the model is penalized for repetitive reasoning and repeated tool calls during multi-turn interaction; overthinking and rapid response-length growth are counteracted by redistributing reward among positive samples rather than applying a blunt length penalty.

Mixed training and generalization

The model adapts to similar tasks and harnesses during RL. Only a small number of scaffold adaptation examples are needed in earlier training stages. During RL, tasks aligned with different benchmarks are mixed and their scaffolds scaled in varying proportions — mixed training across tasks and scaffolds improves generalization, and gains on one task reinforce gains on others.

3. Expert Fusion Under Long Turns: MOPD Refined

LongCat-2.5 retains the MOPD expert-group mechanism from 2.0, with separate groups optimizing agent capability, reasoning, and interaction — multi-turn task execution, single-turn reasoning, fine-grained instruction following, and safety defenses that do not trade away usefulness.

In MOPD the student samples online per domain and the expert teaches via full-vocabulary KL divergence on those samples. The samples must reflect the student's real behavior, and the teacher must be able to give a trustworthy signal on them. Earlier work controlled distribution shift by splitting teacher trajectories into per-turn prefixes as student context. LongCat-2.5 goes one level finer: each teacher reply is split at fixed length into per-cut prefixes, and student self-sampling is capped at that length — directly addressing shift that occurs inside a single long response, which is exactly the shape of an agent turn.

Cost is controlled structurally. All prefixes from one teacher trajectory are grouped and sent to the same inference engine, sharing prefill computation and KV cache. At training time the teacher trajectory is a trunk and student samples are branches; Tree Attention lets a single forward and backward pass train every sample in the group, eliminating redundant computation and storage on teacher tokens.

4. Infrastructure: Under 80 GB Per Card

LongCat-2.5 uses long-sequence training in both mid-training and supervised fine-tuning. The binding constraint is that domestic accelerators have less than 80 GB of memory per card, so the training system is designed around memory first and topology second.

Supernode-aware parallelism

Parallel groups are configured to match the supernode topology: FSDP and EP degrees equal the card count per supernode, and CP never exceeds it. That keeps parameter all-gather, expert-token all-to-all, and KV all-gather inside the high-bandwidth interconnect. Hybrid vocabulary parallelism shards the base embedding, LM head, and N-gram embeddings across the DP × CP domain for further memory savings.

Expert-parallel load imbalance is handled by threshold-triggered dynamic expert replication built on MoonEP. Replication only activates when imbalance crosses a configured threshold, which avoids the trap where added communication costs more than the balance gains — and avoids the two OOM modes: routed tokens overflowing the receiver, comm operations overflowing the sender.

The discrete image-token design pays off here as well: with the vision encoder out of the training graph and image token counts known at packing time, modality load ratios are predictable, so modality proportions stay approximately uniform across data-parallel ranks.

Dual-shard FSDP

Parameters are sharded within each supernode's FSDP domain, while FP32 master weights and optimizer states are sharded further across FSDP domains through HSDP replicas — preserving parameter communication efficiency while cutting resident memory. Parameters, gradients, and optimizer states are organized into contiguous flattened buffers that support non-uniform sharding and Muon optimizer sharding. Gradients are written directly into weights and temporary buffers are reused, reducing intermediate copies and peak memory.

At the communication layer the system uses zero-copy AllGather/ReduceScatter to eliminate the intermediate copy in default collective algorithms; EP packs tokens together with routing probabilities and uses an AIV-based path to relieve AICPU task-expansion bottlenecks; parameter prefetch overlaps AllGather with compute while managing contention with CP; and ScMoE overlaps EP communication with dense-branch compute. Host-side overhead is trimmed by batching gradient operations, merging metric reductions, CPU core pinning, and NUMA-aware scheduling.

Combined, the FSDP configuration delivers 86% higher per-card throughput than a DDP baseline on long-sequence SFT.

Production-grade train–inference consistency

Building on IsoExec, GLM-5, and XoRL, the team built a consistency scheme where training, prefill, and decode each pick their own parallel configuration while per-token log-probs remain bitwise identical. Both sides use efficient batch-invariant operators with aligned framework math and complete backward support. It is enabled by default in experiments and production, and serves as a shared numerical regression baseline for operator and framework iteration.

Two extensions go beyond community solutions, both targeting cases where differing parallelism breaks alignment:

  • TP: instead of split-K partial sums requiring a reduce-scatter, compute the full K dimension. Training keeps weights sharded and uses weight all-gather plus input all-to-all so each rank completes the full-K GEMM. Prefill follows the same approach; decode converts o_proj/fc2 to column-parallel, using input all-gather, full-K GEMM, and output all-to-all — avoiding both per-step full-weight aggregation and cross-card numerical summation
  • DCP: training forward and prefill adopt matching sparse-attention operators that reproduce decode's KV chunking and reduction order under the given DCP configuration, aligning precision across all three modes

PD disaggregation for long-context rollouts

For long-context multi-turn rollouts with controllable load, LongCat-2.5 separates prefill and decode instances and optimizes three things together:

  • Larger effective cache: prefill uses QCP to allocate compute per token and KVP to store KV by page, avoiding the KV redundancy MLA incurs under TP. Once KV is migrated back to device memory, HiCache releases main-memory copies that nothing else references. Weight management and actor offload are rebuilt on Mooncake to free more memory for HiCache
  • Cross-layer prefetch to hide transfers: LSA's odd layers reuse the previous even layer's top-k indices, so odd-layer KV can live entirely in host memory with only a small working cache on device. Once an even layer produces its indices, the next odd layer's KV is loaded ahead and overlapped with the current layer's remaining compute — nearly doubling decode KV capacity at no TPOT cost
  • Capacity-aware scheduling: the router admits requests based on L1+L2 cache capacity and total request tokens, prioritizing groups close to completion so batches fill and caches release early. This prevents the recompute avalanche where multiple long trajectories alternately evict each other's prefixes

A 3:2 prefill-to-decode instance ratio was optimal for the tested long-context workload.

W4A4 inference

For a 1.6T MoE, the inference solution quantizes expert weights and activations to 4 bits and runs matmuls on native INT4 units. Accuracy builds on FlatQuant's learnable equivalent transformations, further tuned for MoE, and matches the unquantized model on every evaluated downstream task.

  • Data path: a shared input transformation across experts quantizes before token replication and dispatch, so one INT4 representation is reused through expert communication and computation
  • Kernels: transform, scale computation, quantization, and packing fused into dedicated operators; weight layout and transposed access optimized to reduce movement and conversion
  • System: compute–communication pipeline overlap tuned separately for prefill and decode according to data dependencies and hardware constraints
Online stress test vs. W8A8 INT8 Change
Prefill throughput+43.3%
Decode throughput+42.77%
TTFT−15.91%
TPOT−19.72%
GMM kernel1.73× average speedup

5. Evaluation Results

The release compares against GPT-5.5, GPT-5.6-Sol, Claude-Opus-4.8, and Claude-Opus-5 in the headline charts, with the full table also covering GLM-5.3, Kimi-K3, and DeepSeek-V4.1-Flash. All LongCat-2.5 results use enable_thinking=on, temperature=1.0, top_p=0.95; competitor scores marked with an asterisk come from public technical reports, blogs, or official leaderboards, and unmarked ones are self-run and indicative only.

Headline scores

Benchmark LongCat-2.5 LongCat-2.0 Best in comparison set
Terminal Bench v2.188.470.8DeepSeek-V4.1-Flash 90.6
Terminal Bench v4.038.53.0Claude-Opus-5 53.9
DeepSWE v1.164.69.7DeepSeek-V4.1-Flash 74.2
PaperBench82.145.2GPT-5.6-Sol 83.3
BrowseComp91.979.9LongCat-2.5 91.9
AutomationBench v1.065.151.8LongCat-2.5 65.1
HLE (w/ tools)63.137.5Claude-Opus-5 64.7
MCP Atlas83.161.8Claude-Opus-5 85.8
NL2Repo60.540.9Claude-Opus-5 75.3
3DCodeBench (Text→3D)55.4—LongCat-2.5 55.4

How to read the numbers

Two things stand out, and one of them is not flattering.

The vertical jump is enormous. DeepSWE v1.1 goes from 9.7 to 64.6; Terminal Bench v4.0 from 3.0 to 38.5; PaperBench from 45.2 to 82.1; SkillsBench from 36.8 to 63.3. Those are not incremental gains from more pretraining data — they are the shape of a step change in post-training. It is the clearest evidence in the release that long-horizon agentic RL, not scale, is doing the work.

But leadership is partial. LongCat-2.5 tops the comparison set on BrowseComp, AutomationBench, ALE v1.1, ResearchRubrics, and 3DCodeBench, and lands close on Terminal Bench v2.1 (2.2 points behind) and PaperBench (1.2 behind). Claude Opus 5 still wins the hardest repo-scale and job-simulation tasks: Terminal Bench v4.0 by 15 points, NL2Repo by nearly 15, Program Bench by 11.5, JobBench by 1.3, GDPVal-AA by 2.9. DeepSeek-V4.1-Flash leads DeepSWE v1.1 and Terminal Bench v2.1. On pure vision benchmarks LongCat-2.5 is mid-pack — VideoMME 85.2 against 90.0 for Kimi-K3, MathVision 96.5 against 97.8.

The honest summary: a strong all-round agentic model with a distinctive visual-coding edge, competitive on breadth, not yet dominant on the frontier's hardest engineering tasks.

6. Showcases

Eight end-to-end demos accompany the release, all generated by the model in single sessions. Each targets a different failure mode: sustained physical reasoning, multi-source reconciliation, 3D composition, and long HTML output that has to actually run.

Demo What it tests
Real-time fluid simulationHigh-FPS interactive page with live fluid dynamics; physics reasoning plus rendering performance
3D artifact showcaseWebGL page with a 3D model, drag-rotate, scroll-zoom, double-click focus, wireframe toggle, and cultural info panel
City dioramaComplex road grids and building clusters in isometric 3D with coherent low-poly lighting
Miniature scene assetsMulti-tier carousel; layered geometry, mixed materials, game-asset stability
Chinese-style aestheticsTheme palette components plus explanatory copy; design-to-typography workflow
Business operations analysisReconcile multi-channel data, fix metric definitions, compute true margin, produce supply/marketing/inventory recommendations
Feedback analysis reportDeduplicate, track updates, rank by severity and business goal, emit clickable HTML report
Event invitation generatorUpload a venue photo, describe the event, get an invitation and sign-up page with attendee list and CSV export

7. Access and the Open-Weights Question

LongCat-2.5 is served through the LongCat API Platform and longcat.ai. The API is compatible with both OpenAI and Anthropic request formats, and the model works inside Claude Code, Codex, Hermes, OpenClaw, OpenCode, and Kilo Code — for most teams that means a base-URL and model-name change, not a rewrite.

No open-weight release has been announced. This is worth flagging because it breaks a pattern: LongCat-Flash-Chat, Flash-Thinking, LongCat-2.0, LongCat-Next, Video-Avatar, and Image all shipped weights under permissive licenses, and LongCat-2.0's MIT weights remain available. 2.5 is API-first. Pretrained-model watchers read this as the moment Meituan's open-weights posture shifted from default-open to commercial-first; whether it holds depends on the next two or three releases, not on this one.

Practical consequence: if your architecture assumes self-hosting a current LongCat flagship, 2.0 is still the newest usable open weight, and 2.5 should be treated as a hosted service with the usual latency, data-residency, and pricing dependencies that implies.