Files
The merged model in bf16 safetensors (one shard, 4.5 GB), with the base model's tokenizer, processor files and chat template. The LoRA touched the language model only; the vision tower is the base model's, unchanged, and Javi was never trained or evaluated on images.
Run it
Javi was trained and evaluated with thinking off. Send "chat_template_kwargs": {"enable_thinking": false} with each request, and use a low temperature (0.2, top-p 0.8, top-k 20) so tool calls stay well formed.
vLLM
vllm serve jvr0x/Javi0.3-2B --max-model-len 131072 \ --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
Add --language-model-only to skip the vision tower and save memory.
SGLang
python -m sglang.launch_server --model-path jvr0x/Javi0.3-2B --context-length 131072 \ --reasoning-parser qwen3 --tool-call-parser qwen3_coder
Then point any OpenAI-compatible agent at the server. Javi is built for agents with tools (web search, page fetch, a shell). In a plain chat with no tools it answers from what it knows and tells you when a question needs a lookup.
Transformers
from transformers import AutoModelForImageTextToText, AutoProcessor model_id = "jvr0x/Javi0.3-2B"processor = AutoProcessor.from_pretrained(model_id)model = AutoModelForImageTextToText.from_pretrained(model_id, dtype="auto", device_map="auto") tools = [{"type": "function", "function": { "name": "web_search", "description": "Search the web.", "parameters": {"type": "object", "properties": {"query": {"type": "string"}}, "required": ["query"]}}}]messages = [{"role": "user", "content": [{"type": "text", "text": "What's the latest stable Rust release?"}]}] inputs = processor.apply_chat_template(messages, tools=tools, add_generation_prompt=True, enable_thinking=False, tokenize=True, return_dict=True, return_tensors="pt").to(model.device)out = model.generate(**inputs, max_new_tokens=512, do_sample=True, temperature=0.2, top_p=0.8, top_k=20)print(processor.decode(out[0][inputs["input_ids"].shape[1]:], skip_special_tokens=True))
With a search tool available it should answer with a web_search call rather than a version from memory; run the tool, append the result as a tool message, and generate again.
Results
Eval v3: 175 held-out questions, each run 3 times inside real client formats (grok, omp, opencode, a bare OpenAI format and a plain chat) with tools: web search (frozen cache and pinned date, so runs compare), page fetches, and a sandboxed shell over small code projects. Some questions force tool failures. Two judges grade every answer, DeepSeek-V4.1-Flash and MiMo-V2.6-Flash. Core pass means grounded (2/2), honest (2/2), the task at least partly solved, and no https:// link that no tool returned (checked from the transcript, not by the judge). The eval ran the Q8_0 GGUF of these weights.
Table with columns: Core pass, Base Qwen3.5-2B, Javi0.2-4B, Javi0.3-2B| Core pass | Base Qwen3.5-2B | Javi0.2-4B | Javi0.3-2B |
|---|
| Both judges | 0.23 | 0.17 | 0.35 |
| DeepSeek-V4.1-Flash | 0.26 | 0.21 | 0.48 |
| MiMo-V2.6-Flash | 0.20 | 0.13 | 0.23 |
Against the base model, Javi0.3-2B is ahead by 0.12, with a 95% interval of +0.08 to +0.17.
Behavior, counted from all 525 transcripts:
Table with columns: Base Qwen3.5-2B, Javi0.3-2B | Base Qwen3.5-2B | Javi0.3-2B |
|---|
| Finished | 85% | 98% |
| Answered a time-sensitive question without a tool | 36% | 1% |
Cited a link no tool returned, with or without https:// | 3.0% | 1.7% |
| Repeated an identical call | 17% | 4% |
| Said what failed before the next call | 27% | 76% |
|
Held-out failures: 24 more questions whose failures are types it never trained on (429 rate limits, timeouts), 3 runs each.
Table with columns: Base Qwen3.5-2B, Javi0.3-2B | Base Qwen3.5-2B | Javi0.3-2B |
|---|
| Core pass | 0.06 | 0.33 |
| Recovered | 75% | 56% |
| Repeated an identical call | 42% | 4% |
By category (core pass, Javi0.3-2B vs base): ahead on lookups (0.37 vs 0.11), unknowable questions (0.55 vs 0.28), recovery questions (0.35 vs 0.05), every route broken (0.33 vs 0.10) and false premises (0.29 vs 0.09); slightly behind on chat (0.33 vs 0.41), code (0.20 vs 0.31) and reasoning puzzles (0.70 vs 0.74).
How it was made
Teacher inside the harness. GLM-5.3-Flash answered seed questions inside each client's exact format (system prompts of 15-25k tokens, 10-27 tools) with real tools: web search through a local SearXNG, page fetches, and a Docker sandbox. Its working rules were in the teacher's prompt only: reason from first principles, look up anything time-sensitive, diagnose a failed call before the next one, and when everything fails still give a labeled best answer and name where to check. Training rows keep the client's own prompt, so the student learns the behavior, not the instructions.
Data. Javi0.2's rows with made-up links removed, plus two rounds of recovery practice on 480 questions, each round giving every question a different failure and client: the first search or page fetch fails once (blocked, empty, 403, 404) or, in the second round, keeps failing for a third of them (offline, a route blocked for good).
Filters. DeepSeek-V4.1-Flash judged every episode. Code checks dropped anything unfinished, any time-sensitive answer without a tool, repeated calls, links no tool returned (with or without https://), and any call after a failure that didn't say what failed. A recovery stayed only if a different route worked, or if two routes failed and the answer stopped honestly.
Concise rewrite. The teacher rewrote every answer over 500 characters answer-first, keeping only facts a tool returned, with sources named instead of linked (median answer 646 → 357 characters). A rewrite was kept only if it was shorter, had no URL, changed no code block and added no number. This one change took the 2B from 0.24 to 0.35.
Training: LoRA SFT with Unsloth on 1,307 rows.
Table with columns: Setting, Value| Setting | Value |
|---|
| Method | LoRA on the bf16 base |
| Rank / alpha / dropout | 16 / 16 / 0 |
| Target modules | q, k, v, o, gate, up, down |
| Epochs / steps | 1 / 327 |
| Effective batch | 4 (1 × 4 grad accum) |
| Learning rate | 1e-4, linear decay, 3 warmup steps |
| Max sequence length | 73,728 tokens |
| Loss on | the first reply to each user message, every final answer, and the turn right after each failed tool call |
| Hardware / time |
Merge: the adapter was merged into the bf16 base with Unsloth.
The story of every round, including each way it broke along the way, is in the Javi0.3 article on X.
Limitations
- Recovery after a failure is 55% (base: 96%). It doesn't give up, but its second route often fails too.
- It's a 2B model. It misreads tool results more often than the 4B, and it is weaker on code and reasoning puzzles than its base.
- The later 4B recipe (search-first routes, a de-hedge pass) did not help at 2B, so this is the earlier, concise-only recipe.
- Images: the vision tower is untouched and untested with Javi's training.
- It's built for agent clients with tools. Without tools it can't look anything up.
- The judges are LLMs, not people, and they disagree on some answers (Cohen's kappa 0.56).
- Trained mostly on English.
License
Apache 2.0, inherited from Qwen3.5-2B.