For most queries it is around the same level. Time spent isn't always the best tell of quality, particularly when the search engine used returns little noise
I don't think the reasoning level is what makes it for me. I am treating this as a search engine. I want the thing to fetch/read from index as many pages as possible. Either that or as many agentic tool calls as needed. That takes time.
Also when testing, if you know a piece of information exists in a website, but the information doesn't show up when you run the query, you don't have the tools to steer the engine to work more effectively. In a real scenario you don't know what the engine missed but it'd be cool to steer the engine in different ways to see how that changes the end result. For example, if you're planning a trip to japan, maybe you want the AI to only be shown a certain percentage of categories (nature, night life, or places too), alongside controlling how much you want to spend time crawling, maybe finding more niche information or more related information.
For me, space+f is a "fuzzy search", a filter to find by filename. You can omit some characters, e.g. `pack/back/conf` would show `packages/backend/config.z`.
I have muscle memory now, so I'd have to open the editor to confirm it. There is also another mode, that works a bit like grep I think? I haven't used it but seems that you can look for matches in file content.
It's really funny how they basically advertised YouTube music to a customer emailing them with a frustration about being advertised to when they shouldn't.
