4 ms·
It's a "problem" of compute, I think. If you query without an account on ChatGPT you will see the model look up less stuff and research less, than when you have
by super256 16d ago
It's a "problem" of compute, I think. If you query without an account on ChatGPT you will see the model look up less stuff and research less, than when you have a paid account and choose "medium" or "high" in the effort slider.
Which makes sense, because of you have looked into search and crawlers you notice that search is actual quite expensive (which is why e.g. Kagi charges a few bucks for search every month).
- Catloafdev 16d agoIt's not strictly compute, because this has noticeably improved in open-weight models too, such as Gemma and Qwen. I suspect they noticed this issue and adjusted their training to be better about it over time.
- ahmedfromtunis 15d agoI built a toy news-summarizing agent with Gemma 4, and it was so frustrating, actually, because of the cut-off date. The model wasted over half the token budget, each time, on internal debates over the current date. When generating a World Cup summary, for example, it refused to believe qualification rounds were over and refused to even call the web searching tool to collect the data. I injected the current datetime at the very beginning of the system prompt, but Gemma refused to believe it! The m-effer insisted the timestamp was fake and hypothesized it was being evaluated in a synthetic lab test with simulated future dates! No amount of system prompting could convince it to trust the clock. That was the most frustrating and bizarre "bug" I ever faced!
- ThunderSizzle 15d agoDid you try other models (e.g. Qwen3.6 or others)? I'm curious how others fare. I've noticed Qwen3.6 struggles a bit with today/date based logic.
- carlos_rpn 15d agoQwen 3.6 did the same thing for me. Only after some cajolling it finally went to check the history I asked it to (I had been testing KoboldCPP's web search).