← All speakers

Yuval Belfer is a developer advocate whom AI21 identified as its Senior Developer Advocate in its World’s Fair 2026 announcement. His public technical presentations connect retrieval design with the reliability of model execution. In “Two Bugs That Hid in Plain Sight,” co-presented with Asaf Gardin, he frames a useful diagnostic distinction: an incorrect answer can reflect an engineering failure rather than a limitation to address through better training. High-confidence gibberish without a crash or warning warrants investigation of the system executing the model.

Belfer makes that distinction concrete through AI21’s Jamba models, which combine attention and Mamba state-space layers. He introduces a failure that was rare, appeared only after substantial workload, and was observed in vLLM rather than the other inference frameworks the team tried. Those conditions made an isolated prompt an inadequate reproduction: request history, scheduling and cache reuse were part of the problem. Gardin then explains the detailed investigation, including generating a continuation with vLLM and scoring that exact prompt-plus-continuation sequence with Hugging Face Transformers. Comparing corresponding token log probabilities holds the sequence fixed, exposing execution discrepancies without confusing them with independently sampled answers. Joint presentation, Gardin’s technical account.

The investigation also illustrates why architecture matters to debugging. Under constrained memory, a fresh request could receive only one scheduled token and be mistaken for a continuing decode. Mamba’s decode path reads recurrent state before updating it, so a reused cache slot could introduce another request’s history into the new generation. In the attention path described, current keys and values are written before reading, and sequence-length masking bounds valid positions. Carrying request IDs through vLLM’s forward context enabled a targeted breakpoint that exposed the misclassification. The team’s correction treated zero previously computed tokens as the signal for prefill—the path that initializes a new request—regardless of its scheduled token count. These are findings Belfer helped present; the supplied sources attribute the detailed debugging and linked contribution to Gardin. Technical explanation, merged correction and regression tests.

A second case gives developers a complementary lesson: changing resources can conceal a defect as well as expose one. Rollout-generation probabilities diverged from those recomputed by the FSDP training model before any weight update. Increasing completions per prompt moved periodic failures into the first rollout, allowing the investigation to shed accumulated training history and isolate inference. Larger state-cache allocations exposed unsigned 32-bit cache-index-by-stride multiplication wrapping around; smaller allocations avoided the offending offsets. Changing the index type to size_t supplied 64-bit arithmetic in the reported kernel. AI21 credits Gardin and Amir Koblyansky with this investigation. Belfer’s co-presentation makes its diagnostic value accessible: watch how a parameter changes the timing and reachability of failure, then identify which subsystem could produce that pattern. Joint presentation, credited overflow investigation.

Belfer also addresses retrieval choices. AI21 announced his 2026 session “Stop Chunking Like It’s 2022” around the premise that no single fixed chunk size suits every query. Its description proposed a simple multi-index approach and reported potential recall improvements of up to 37%, without retraining or additional LLM overhead. The supplied announcement establishes that proposed approach and company-reported result, rather than a complete experimental account. Together with his inference-reliability presentation, it shows his emphasis on examining implementation choices that quietly shape an AI application’s results. AI21’s session announcement.

Read the topics behind these talks

4 conference talks

Key ideas

Scroll to read ↓

Local-answer benchmarks reward finding the right passage. Aggregate questions expose a different requirement: complete evidence, structured extraction, and explicit query semantics.

  • Local answers hide system failures
    0:00 ↗
  • The optimization loop preserves the assumption
    2:32 ↗
  • Aggregate questions need complete evidence
    3:21 ↗
  • A small World Cup test exposes the gap
    4:38 ↗
  • Extract structure before answering
    5:44 ↗
  • Translate the question into an aggregation
    7:31 ↗
  • Structure creates its own correctness requirements
    8:00 ↗

Key ideas

Scroll to read ↓

As instructions accumulate, reliable output becomes a search and validation problem. Planning coordinates that work; an execution engine decides how to spend the time and compute.

  • Why is instruction following still a problem?
    0:00 ↗
  • From routing to reasoning and acting
    1:27 ↗
  • A plan needs an execution engine
    3:12 ↗
  • Turn requirements into a search and repair process
    4:49 ↗
  • Choose a path, then reduce the results
    6:05 ↗
  • Higher quality costs additional inference
    6:41 ↗
  • Use planning when the task requires it
    7:20 ↗

Key ideas

Scroll to read ↓

Asaf Gardin and Yuval Belfer trace two silent failures in Jamba inference: a scheduler that read another request’s state and a cache index that wrapped around. Logprob comparisons, repeatable workloads, and request identity turned confident nonsense into concrete engineering bugs.

  • Replay vLLM’s prompt and generated continuation through a simpler reference implementation, then compare corresponding token logprobs to investigate silent execution errors.
    5:18 ↗
  • A correct kernel can produce corrupt output when the scheduler calls it before its state is ready. In the first case, a fresh Mamba request entered decode and read earlier requests’ cached state.
    9:16 ↗
  • Reducing memory exposed the scheduling bug but concealed the index overflow. Treat changes in failure timing and reachability as diagnostic evidence, rather than assuming that disappearance means repair.
    4:47 ↗
  • Thread request identity down to the forward pass. It makes a repeatable bad response actionable by letting a breakpoint connect the request to its execution metadata.
    8:47 ↗

Key ideas

Scroll to read ↓

A small chunk can find a precise fact and miss a relationship spread across a scene. Yuval Belfer explains how searching several chunk sizes and combining whole-document rankings improves recall—and what that flexibility costs.

  • The useful chunk size depends on the question: narrow windows can find contained facts while losing relationships that need surrounding context.
    4:46 ↗
  • The oracle's reported 20%–40% recall gap measures headroom using known answers. It cannot choose a scale for an unanswered query.
    8:14 ↗
  • Multiscale indexing searches N window sizes, maps chunk matches to whole documents, and combines comparable document rankings with Reciprocal Rank Fusion.
    11:15 ↗
  • Belfer reports matching or beating the best fixed size across four datasets at roughly two to five times the memory. Parallel searches limit added latency; scale selection and better fusion remain open questions.
    13:44 ↗

References