Skip to content
All conferences

PyTorch Day Korea

1 in 5

replies from the compiled 1.2B cited a search it never made, on our first test set. As a GGUF, none of 640

Seoul, 21 November 2026

The Search It Never Made: When a 1.2B On-Device Model Should Call Web Search.

Whether a small model on a phone searches when it must, on 160 public questions, four phones and two builds of the same weights.

The talk

In a model-driven agent loop, a small model on a phone decides whether to search the web or answer from its weights. A wrong call costs either a fabricated fact or several seconds and a network round trip.

The talk puts that decision to 160 public questions from RetrievalQA, PopQA and FreshQA, through a shipping open source Android assistant on four phones, with the same LFM2.5 1.2B weights as a compiled ExecuTorch export and as a GGUF. The two builds did not decide alike.

The evidence

The same weights, two builds

LFM2.5 1.2B, web search the only toolCompiled, 8da4w ExecuTorchGGUF, Q4_K_M llama.cpp
Searched on the 75 questions that need it1 to 3 of 7533 or 34 of 75
Cited a search it never made32 to 35 of 1600 of 160, on each of four phones

160 rows an arm, seed 7, on the Dimensitys, Tensor G5, Exynos 2400 and Snapdragon 8 Elite, with web search the only tool offered. Correct answers are left out here: their grading was later revised, and the notes below carry both versions.

A standing note
These are not clean measures of the model's own judgment. On 21 of the 75 questions, the app's prompt note asks for a lookup. The GGUF obeyed it on all 21, which is two thirds of its 33 calls, and called on 12 of the other 54. The compiled model obeyed it on none.
A second test set
On a second set of rows, on one phone, the GGUF did narrate a search it had not made, twice in 160 replies in each arm. So its zero holds for the first set only.
A later correction
The follow-up note on why the compiled model narrates is corrected too: ExecuTorch's LFM2 graph carried state between prompts in a reused runner.

Where and when

Conference
PyTorch Day Korea, hosted by the PyTorch Korea User Group
Date
Saturday 21 November 2026. The session's time is not published yet.
Room
Centerfield East 18F, AWS Korea, 231 Teheran-ro, Gangnam-gu, Seoul
Track
Run

Watch and read

Keep reading

All conferences
  • GitHub Universe

    24 tasks

    of real work on ten setups. Each bar is tasks finished; the bright ones ran locally

    San Francisco, 28 October 2026

    When is local Copilot worth it?

    The same Copilot CLI agent on the same real tasks: open-weight models you serve yourself against hosted Copilot.

    Alpha Romer Coma

  • PyTorch Conference Europe

    Compiler Tax

    what surprises developers moving PyTorch workloads to ASICs

    Paris, 8 April 2026

    De-mystifying PyTorch for ASICs

    A code-first check on moving PyTorch from GPUs to Google TPUs and AWS Trainium, and when it is worth doing.

    Alpha Romer Coma

  • PyTorch Day Japan

    27×

    faster prefill on a second turn: Qwen3-1.7B on ExecuTorch, reusing 1,192 tokens

    Tokyo, 10 December 2026

    When the KV Cache Cannot Roll Back

    How a phone skips re-reading a 2,050-token agent prompt, built twice because the app's two runtimes have different cache constraints.

    Alpha Romer Coma and Arjhine Ty