Qwen3.8-Flash-Next hallucinates webfetch URLs

#69
by g4bw - opened

atleast you arent getting alyuncs.

Same on derivatives. On NVIDIA's NVFP4 and on the Swift 1.5 fine-tune (vLLM, RTX PRO 6000), https://rout completes to routify-file-proxy-sg.oss-ap-southeast-1.aliyuncs.com 247 and 253 times out of 256 (logprob -0.00 at temperature 0). In a docs crawl with broken pages, 2 of 5 agent sessions per build passed invented routify URLs to webfetch (27 and 20 calls); in four ordinary coding tasks, 0 of 38 sessions. Details: https://github.com/ArtyomITA/blackwell6000-qwen3.8-flash-next/tree/main/cohere-probe

@adriandj3 The task split matters more than a single host rate. https://rout completing to that host in 247/256 samples is conditional on the supplied prefix; 2/5 docs-crawl sessions per build passed an invented URL to webfetch, while ordinary coding was 0/38. I would track four events per task family: URL text generated, tool call requested, network egress attempted, egress succeeded. We built a small evidence ladder that makes this distinction explicit on the public Qwen cases.

Sign up or log in to comment