- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes CLUE, a latent reasoning method. CLUE pairs a trainable latent encoder with a smaller, frozen text model. It adds a contrastive loss to GRPO that favors verified correct trajectories under paired latents over latents from unrelated problems, without requiring ground-truth reasoning traces. Experiments cover four mathematical benchmarks and GPQA, alongside latent-swapping and communication-budget analysis. Results are promising for the 1.7B scale, but mixed at the 4B scale.
Critical strengths
- Useful objective with a controlled ablation. Removing the contrastive loss reduces Math500 accuracy from 84.68% to 82.63% and GPQA from 35.04% to 28.91%. This supports a contribution beyond simply adding a larger latent encoder.
- Evaluation goes beyond aggregate accuracy. Latent swaps, domain transfers, and reasoning-style probes directly examine whether conditioning affects the receiver. This makes the paper more informative than a benchmark-only comparison.
Critical weaknesses
- The latent swap results don't cleanly establish beneficial latent reasoning. Eq. 9 stops gradients through the positive score and explicitly suppresses correct trajectories under mismatched latents. As a result, the paired vs. random gap can just reflect learned sensitivity to mismatches rather than helpful guidance. The Math500 gap is also modest (only 0.60 points).
- The advantage doesn't come from fair comparisons. CLUE trains a larger generator, while SoftCoT trains only a small linear projector and HRPO uses LoRA. Direct receiver GRPO also uses a different model capacity and compute budget, and slightly outperforms CLUE on average at 4B scale. Without matched resource comparisons and measured latency / transmitted bytes, the broader superiority and efficiency claims lack empirical backing.
Questions for authors
see weaknesses
2 comments
Thanks for the extra results. The small gain from paired latents on Math-500 and the higher training cost still remain a concern. I’m keeping my score at 2 for now.
Answer to Reviewer En1V
Thanks for the review and the questions! We address your concerns as the following:
Beneficial Latent Reasoning
The stop-gradient applies only to the paired score within the auxiliary contrastive term. GRPO continues to optimize answer correctness under paired conditioning. Without this detachment, the contrastive objective would update both branches. Our routing deliberately leaves direct paired-response optimization to GRPO while directing the auxiliary gradient through the mismatched score.
Our ablation shows that adding the contrastive objective improves paired task accuracy at fixed architecture and trainable capacity, with gains of up to 6.13 percentage points. These improvements occur under ordinary paired evaluation and cannot be explained solely by depressing accuracy due to sensitivity to mismatches. The observed paired-message advantage is also positive across all datasets evaluated with latent swaps. In contrast the outcome-only baselines show no consistent paired advantage.
To complement these results with a comparison that does not introduce mismatched conditioning. We evaluate a learned, input-independent prefix shared across questions, using the same frozen receiver and latent positions (see Table 2). CLUE exceeds this control by 2.38 and 2.20 percentage points on Math-500 and OpenThoughts30K. This provides additional evidence of task-performance benefits beyond degradation under latent swapping.
Ablation on Problem-Specific Latent Utilization. Accuracy with paired latents and latents generated from randomly selected other evaluation examples. Parentheses report changes relative to paired latents in percentage points.
Trainable Parameter Comparison
We added an additional ablation to investigate CLUE under comparable trainable parameters. To this end, we train a CLUE variant following SoftCoTs frozen setup, optimizing only the residual connection and latent input embeddings to the latent encoder (denoted as w.o. encoder tuning in Table 2). Trained on the same data, CLUE w.o. encoder tuning outperforms SoftCoT on Math-500 (82.14 vs. 76.28) and OpenThoughts30K (64.29 vs 56.98). SoftCoT, trained without contrastive supervision, shows no consistent accuracy advantage from using latents generated for the same problem rather than random replacements. Notably, a simple learned prefix also outperforms SoftCoT on both datasets. CLUE retains this advantage across all three datasets even without encoder fine-tuning.
Resource Comparison
Our comparisons match the text-generating model size within each scale. CLUE’s additional, larger encoder constructs the latent prefix in a single forward pass, which the receiver then prefills before generating its answer. Inference time is therefore dominated by autoregressive decoding, rather than by the additional encoder pass. In the profiled CLUE configuration, the encoder takes approximately 0.02 seconds or 1.4% of total inference FLOPs per question, while text generation accounts for nearly all model-call latency.
We additionally report end-to-end latency under native Hugging Face decoding for the 4B encoder and 1.7B text model (Table 5). CLUE achieves comparable measured latency compared to direct GRPO (180.62 s/q vs 178.45). We do not claim a speedup, but interpret more efficient reasoning as similar latency alongside higher accuracy. Frozen-encoder CLUE is the fastest post-trained configuration at 138.11 seconds. The zero-shot comparison shows that GRPO finetuning increases latency across methods.
Estimated training compute is 901.2 PFLOPs for CLUE, compared with 650.7 for direct GRPO and 716.0 without contrastive training. The contrastive objective therefore adds approximately 25.9% training compute relative to the same-architecture ablation. However, contrastive scoring is performed only during training and introduces no corresponding inference-time scoring overhead.
Efficiency comparison for Qwen3-1.7B / Qwen3-4B → Qwen3-1.7B.
Transmission Cost
At comparable task performance in the evaluated configuration, latent communication uses 64 KiB per example versus 8 KiB for text. SoftCoT and CLUE transmit the same latent payload. The communication-budget advantage is therefore fewer sequence positions, not fewer transmitted bytes.