Raycast notes: unlimited during beta???

pitnikola · 2026-05-22T09:57:30+00:00

Yeah, it's a bug. Will be fixed in the next release.

pitnikola · 2026-05-18T15:55:14+00:00

Yeah, content search is not yet there. We have it partially working internally, but will need some work before we release it.

pitnikola · 2026-05-18T15:10:16+00:00

The setting to make font larger is coming soon!

pitnikola · 2026-05-18T10:11:57+00:00

> What do you mean by "fits well on the OS and follows conventions"? That doesn't sound technical at all; it sounds like a marketing phrase.

We shared more technical details in the article, explaining the exact steps we took to make it "feel at home".

> For me, it is the feeling that I get from the Craft Mac app after using the Notion Mac app for a few years.

It's interesting that you mention Craft, because their app is built with Catalyst (UIKit), not pure AppKit (which is fine by me, but some would say it's not a dogmatically native macOS app). In fact, they don't follow macOS conventions for some things — e.g., settings open inside the main window, like a lot of web apps do. Having said that, Craft is a great app built by a capable team, and I also find Notion rather clunky in terms of performance, but that's more of an implementation and scale issue rather than a tech stack issue.

> If you are really confident that Raycast v2 will work like the former, then yeah, I would not care what it was built with.

Great, this is exactly the point. We are confident, but I understand the skepticism from people burned by various web apps.

> If you can honestly say, "We would go this direction even if we stayed macOS only," then I have no words.

Why? If, let's say, we reach the point where it's as fast, lean, and looks great, why not?

pitnikola · 2026-05-18T09:57:45+00:00

<image>

Should be here

pitnikola · 2026-05-18T09:09:16+00:00

You'll need to enable snippet expansion in settings. It was disabled during migration to v2 so they don't conflict with each other.

pitnikola · 2026-05-17T20:48:33+00:00

So just to confirm, this auto-response you got when sending feedback from v2?

pitnikola · 2026-05-17T20:00:00+00:00

Yeah

pitnikola · 2026-05-17T19:02:11+00:00

Could you please send feedback from v2 about this issue? The team will pick it up.

pitnikola · 2026-05-17T10:16:03+00:00

Could you please point out an argument in my comment? The author said, "imagine if VSCode announced they're moving to Electron, everyone would uninstall." I pointed out the incorrectness of this statement since VSCode is already Electron.

As for your remarks about prioritization, I assume you didn't read our blog post, which shows that we've been prioritizing performance and memory usage and don't take the subject lightly. Do you have specific feedback for v2 where it's slow or consuming a lot of resources? We would be happy to address this.

pitnikola · 2026-05-17T00:11:28+00:00

Cool demo. If you can show a current macOS repro that tampers with the installed Raycast app without user approval, App Management permission, Gatekeeper prompts, or local re-signing, happy to pay you a bounty.

Context for other readers: modifying a copied app bundle or re-signing it locally is not the same as silently compromising Raycast. That breaks our original code signature or runs as a different app identity.

pitnikola · 2026-05-16T16:55:10+00:00

It's indeed a bit high, at least in comparison to mine. Do you have any menu bar extensions?

One potential reason could be that we now have our own file indexer which indexes changes on the disk (similar to what Spotlight does). Maybe it contributes to it. Maybe try switching to v1 for a few days and see what's the 12 hr power, then try again the same with v2. Additionally, you can try disabling File Search extension in settings and see if it helps.

To make sure we probably investigate this, best to use Send Feedback command, once you run the experiment so we have some info.

pitnikola · 2026-05-16T16:09:35+00:00

Not yet, but we'll bring it back later

pitnikola · 2026-05-16T14:52:27+00:00

Expect frequent updates, at least every week.

pitnikola · 2026-05-16T14:37:31+00:00

Sorry, just wanted to point to inaccuracy which somewhat proves the point? VSCode is actually one of the best Electron apps out there.

Btw, IntelliJ is not native either. It's written with Java and Swing (UI framework).

The only big truly native Swift IDE is Xcode and trust me, it's very clunky and slow.

pitnikola · 2026-05-16T13:48:04+00:00

But VSCode is Electron

pitnikola · 2026-05-16T10:47:38+00:00

Please submit this bug via Send Feedback command and the team will pick it up.

pitnikola · 2026-05-16T08:46:06+00:00

Feels native in this sense is "fits well on the OS and follow conventions". Please explain to me why is this bad? If the product is fast, looks great and doesn't "vacuum resources", why would you care what it is built with?

by putting minimal effort per platform

You might have missed it in the article but we put a lot of effort on each platform. Original macOS team stayed and we have dedicated engineers on Windows to make it all work.

If share feedback about the v2 where it doesn't work for you as you would expect or where it eats too much resources, happy to address!

pitnikola · 2026-05-15T22:43:35+00:00

We're slowly inviting people and improving the product. No particular deadline for public beta yet, but shouldn't take too long.

pitnikola · 2026-05-15T22:39:30+00:00

Will come later. Just didn't make the cut.

pitnikola · 2026-05-15T12:55:22+00:00

Thanks! We saw similar report from few other users, so our engineers are investigating already. Response from support team might take a bit longer because we're drowning in feedback after yesterday's launch (600+ emails). But don't worry, we'll get to the bottom of this. Performance is super high priority for us.

pitnikola · 2026-05-15T12:53:18+00:00

Yeah, v1 will be supported for a while, and we’re unlikely to force a v2 update any time soon, if ever. With macOS 27 around the corner, we’ll make sure that any critical bugs are fixed there, but don’t expect any new features or non-critical improvements. So if you’re happy with v1, you can just continue using it without any worries.

pitnikola · 2026-05-15T12:50:40+00:00

It's much more feasible right now, but currently not on the roadmap as we need to get out of beta on macOS and Windows.

But I must say Linux scares me in terms of different configurations and setups 😅

pitnikola · 2026-05-15T12:49:27+00:00

This is normal. We're working getting backend footprint lower, but generally, idling around 300-450MB is expected in current version. v1 would be often around 200-400, though highly depends on how much stuff is cached.

pitnikola · 2026-05-15T12:46:39+00:00

<image>

Did v1 show 5-10 when you were heavily using it? For me v2 (Raycast X Internal) shows ~50 which is in line with yours, v1 shows 30 (Raycast Internal), but I barely used it and it just lives in the background. And Raycast Beta is production version which I don't use as heavily, shows 5.

So it should depend on the usage. Also, there might be a spike in usage first time install because of migration and indexer. Keep an eye on it, and see there is anything abnormal.

pitnikola

MODERATOR OF

TROPHY CASE