Needle2 is not presented as a shrunken general chatbot. It is a 14MB agentic model focused on selecting tools and producing structured arguments on phones, wearables, smart-home devices, and robots. That narrow target matters. Local execution can remove a network round trip, preserve more user data on the device, and give an agent stack a cheap final layer for routine actions.

Cactus treats tool calling as retrieval and assembly rather than broad knowledge recall: match a request to a supplied tool name, extract values, and emit the expected JSON. The model is trained around consumer-device actions and structured extraction. Its published evaluation shows that it can often maintain valid output formatting despite its size, while also acknowledging larger gaps on unfamiliar enterprise APIs and Java or JavaScript tool schemas. Small size does not erase distribution boundaries.

The public demo made those boundaries concrete. Community testers reported a request to make a room warmer producing a cooling command at 65 degrees. Other prompts caused the model to invent a front-door lock call when it should have declined to use any tool, or to ignore brightness and temperature-unit details. These are not cosmetic chatbot errors. If the output controls a thermostat, lock, vehicle, or payment flow, a fast malformed decision can have a physical or financial consequence.

That distinction suggests a practical deployment model. Reversible, low-risk tasks such as changing a screen or starting media may be good candidates for a tiny local caller. Higher-risk actions need an allowlist, unit normalization, calibrated confidence thresholds, and explicit confirmation. Training must also make “call no tool” a common and successful outcome. A router can send ambiguous or multi-step requests to a larger model instead of forcing the smallest layer to answer everything.

Several participants asked whether 14MB is a useful optimum or simply the smallest impressive headline. A 28MB, 140MB, or even larger local model might offer a better reliability-per-watt tradeoff while still fitting comfortably on modern hardware. Useful micro-LLM evaluation should therefore report memory, battery use, latency, abstention quality, and the cost of wrong calls—not only benchmark accuracy or minimum binary size.

The Needle2 project page provides architecture and evaluation details. The Hacker News thread is especially valuable for its concrete failure cases and questions about size tradeoffs. The next test is not whether a 14MB agent can call a tool, but whether a system can reliably decide which requests that agent should be allowed to handle.

#micro-llm

Needle2 Fits an Agent into 14MB, but Its Mistakes Define the Real Test