@jafupy@raycast Seems like a bug (you see the search bar and other UI, so it has nothing to do with the fact that it's a webview).
Can you please send feedback with logs using this menu item? We'll take a look.
While I enjoy Codex, it's frustrating that they don't have a $100-200 plan in Teams. This makes Claude Code much more attractive cost-wise.
@thsottiaux any chance we will see similar thing in Codex?
Quite hard to answer the question of "how much," but we do leverage AI coding agents heavily in the team, where they produce good results. That said, a lot of high-polish UI and nitty-gritty details are not AI's strongest suit, so it still required a lot of manual work or careful steering from engineers. Now, with the foundation laid out, it's much easier to add new incremental features with AI.
@BuildWithTom@bedesqui@raycast lol, he's showing the .config folder with Raycast extensions which are literally the same between v1 and v2 (React and Node), as you can see on the screenshot (raycast and raycast-x). Has nothing to do with the v2 stack ๐คทโโ๏ธ. Igor is asking if we could reduce the size of those.
@IGamidli@raycast We haven't shipped content indexing yet, but it's in the works. If you heavily relied on it, you might still want to use Raycast v1. If not, yeah you won't need Spotlight index in Raycast v2.
@n3o773@peduarte@M2Fauzaan@raycast This has nothing to do with webview vs non-webview. Just a matter of implementation. In v1 we use fully custom control and support dragging. In v2 just didn't get to this yet, but it's on the list. Even the liquid glass is possible with enough effort.
https://t.co/NZ6s5tYsPc
@M2Fauzaan@raycast In Raycast v1, we didn't use the provided AppKit components, and they were all custom. So it's less about web vs. non-web. It's just custom controls.
@JaceThings@thomaspaulmann@raycast Wait, 85/s is ultra slow. Something is off. It should be tens of thousands per second... Do you have some external hard drives?
@Ruben266592 @sindresorhus All public extensions go through review in our public repo and security checks before they are published. Also, not on purpose, but we're so slammed with extension submissions that the review phase takes a while, so it's very hard to sneak in a malicious package.
@IftatBhuiyan@sindresorhus We had this experiment internally at some point, but we have inner panels that use liquid glass, and Apple doesn't recommend piling them on top of each other, according to their guidelines. But let's see, maybe we'll add some setting in the future.
The AI stuff you posted above has nothing to do with "webslop," does it? More like a product decision, which is a fair critique. For what it's worth, in v2 we made a lot of improvements to AI chat and now have the foundation to make it much better.
As for "Raycast's appeal is that it's a faster and more reliable Spotlight" โ the new version is as fast, if not faster, while indexing much more. Your point about the fact that you cannot trust "webslop" sounds like something we wouldn't be able to address.
@bardonadam@peduarte@sindresorhus Try asking AI to write even one feature like Raycast Notes natively for macOS and Windows, and see the result you get. You're up for a surprise.
A complex stack makes the initial investment harder. But building new features and polishing existing ones is much easier now.
everything you need to know about how the team built the new @raycast from the ground up
honestly worth a read ๐ https://t.co/vP4OUpIHSV
there's nothing to hide
@pampas9000@raycast Could you please send the numbers you get when idle via Send Feedback command? Somewhat higher is expected for now, but we're working on optimizing it.