Needle 3 vs TypeSafe Jev: tool calling and setup
Compare Needle 3's 8 to 29MB device models with TypeSafe Jev, and learn about Python setup, fine-tuning and structured output limits.
Player not loading? Watch on YouTube
Needle 3 from Cactus Compute turns natural language requests into function calls and extracts structured fields from text. The presenter describes an 8 to 29MB model that works offline on phones, watches and small boards. Its intelligence ladder lets developers export different model depths from one set of weights.
The walkthrough covers Python installation, tool decorators and the difference between executing a call with agent.run and inspecting JSON with agent.complete. Function schemas constrain the output grammar, but valid JSON does not guarantee a correct decision. Confidence scores help applications decide whether to execute a call or request confirmation. Extraction copies spans from the input, so it cannot supply values absent from the text.
The presenter cautions that production use needs task-specific fine-tuning. Small base models score poorly in the cited tests, and unrelated requests can interfere with later calls when conversation state persists. Training uses JSONL examples and a LoRA adapter; export targets include desktop systems, Android, iOS, watchOS and WebAssembly.
The comparison contrasts Needle's open source, on-device execution with TypeSafe Jev's cloud approach. Jev reportedly produces a structured answer in one parallel pass, while Needle decodes tokens under a grammar. Both can still choose the wrong action despite producing valid structure.