Urgent.News

What's breaking now, across thousands of outlets.

Tech

O agente não precisa pensar em voz alta

Hybrid Reasoning Agents combinam raciocínio latente com ações em texto - e forçam a separar eficiência, observabilidade e validação. Agentes de LLM ainda raciocinam e agem quase só em texto. Cada passo intermediário vira token legível, mesmo quando ninguém precisa ler o raciocínio — só o resultado ou a chamada de ferramenta. O custo sobe. A latência também. Raciocínio latente (em espaço contínuo,…

Hybrid Reasoning Agents blend latent reasoning with text-based actions, forcing a separation between efficiency, observability, and validation. Unlike LLMs that primarily think and act in text, these agents alternate between latent (unspoken) and text (environmental) modes within a single generation. A lightweight module, HybridLink, manages the transition, while a continuous working memory preserves the hybrid context across turns.

During training, two-step processes (HybridSFT and HybridRL) teach the model to coordinate both modes and decide when to remain silent and when to speak. In benchmark tests across 11 tasks and three model scales, Hybrid Reasoning Agents achieved about 10.4% performance improvement over text-based agents and previous latent methods, with token reduction ranging from 35% to 55%, inference speeds between 1.8x and 2.6x faster, and cost savings estimated between 2.7x and 3.7x.

For production environments, the key advantage is not merely cost reduction, but the improved efficiency and readability, making it clear when text is necessary (e.g., API calls, diffs, user responses, audit evidence) and when it can remain latent—provided there's a way to recover or sample that internal reasoning when validation demands it.

This shift in engineering software assisted by AI changes the design of supervision pipelines. Production teams must measure not just the complete textual log, which could be wasting tokens unseen, but also when to keep the intermediate steps hidden and when to expose them for inspection. The decision to separate when to think in silence from when to expose step-by-step actions is an architectural and governance choice, not a prompt detail.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Assume Nothing Persists: Five Free-Tier Myths and a Restart Drill You Can Re-Run

Free compute is easy to start and easy to misread. Your demo works on Friday afternoon. Do you know it works on Monday morning? Here is one reframe that kills most of these myths at once.

  • Free tiers provide temporary access, not permanent servers
  • Data stored locally can be lost; categorize data wisely
  • Health checks must test both liveness and readiness

48-Hour Field Notes: A Crash Mid-Batch Proved My Queue Had No Memory

My batch job had a very confident opinion about progress, and that opinion lived entirely in a Python variable. If the process died, the variable died with it, and the next run started from zero like…

  • Queue lost memory during crash, causing workers to restart from scratch
  • Journal implemented to survive terminations and track item status
  • Lease system with expiration prevents loss of data in between claiming and completion

Time Magazine Profiles John Ternus

Andrew Chow, writing for Time: Just below the broad smile he’s been wearing all morning, John Ternus’ hands are shaking. On this September day in Silicon Valley, Apple’s new CEO is surrounded by…

More from Monday 19 October →