OMEGA Ω™

@micheltrillo This is vibe coded, right? You forgot to delete an AI system message and posted it on your website: "If you want to be more aggressive, set the Chromium bar value to a specific headline example (650 MB) and keep the label “varies by browser”.

Funny but sloppy.

@chrismessina Great share. “3M+ lines across thousands of files” 😳 is serious output, especially if Cursor was effectively running for a week and the browser was AI authored end-to-end.

To that post's comment "It kind of works! It still has issues and is of course very far from Webkit/Chromium parity...", my target with Omega has been the opposite philosophy: the smallest possible native footprint that still delivers a credible web experience, where the only latency you feel is the network and the remote server, not the app itself.

To your question, though, I’m at a 50/50 right now as macOS is newer terrain for me, even if Swift isn’t. If this were iOS, Liquid Glass would be almost trivial, where on macOS I had to fabricate the illusion manually. The Standard vs Fortress toggle, the page Zoom slider, and the ON/OFF switches are all hand-built “glass” experiments, and they landed better than expected.

Now I’m curious what Omega’s code line count is...shall I count? I'll get back to you on that. 🫡

And going forward, I’ll absolutely lean harder into AI to accelerate feature velocity. I can’t type fast enough, and some of what users will expect next, especially AI integrations and more complex capabilities, benefits from this machine-assisted augmentation.

@saad_zafar 1,000,000% we have a choice, or at least we should, to decide whether we allow ourselves to be tracked, tailed, and distilled into a commoditized user profile designed for someone else’s monetization, delivering virtually no value back to us. For me, Omega is the last browser I intend to use. That’s precisely why I’m relentlessly focused on making it secure, private, lightweight, and, frankly, as aesthetically, irresistibly sexy as possible. ❤️🫦🤣

@alexcloudstar I hope to meet your expectations, sir. Bookmark import is a priority, so I’ve added it to the roadmap. Stay tuned!

@tony_hsieh2 Amnesia Mode in OMEGA is implemented using WKWebsiteDataStore.nonPersistent(), which means WebKit keeps cookies, cache, local storage, and other website data in an ephemeral in-memory store and does not write that session into the normal on-disk browser profile.

That said, macOS virtual memory can page portions of RAM to disk under memory pressure, so in a strict sense any in-memory browsing session could be paged out. Practically, macOS swap is protected via encrypted virtual memory, so it is not a straightforward “recover plain text from disk” situation, but I still would not market it as “forensically guaranteed.”

The right comparison is that it is in the same class as standard incognito or private browsing, which is designed to prevent local persistence after the session ends, not to defeat a compromised machine, live memory capture, or network-side logging.

More precisely, yet in theory, some session data could be written to disk if macOS pages memory out to swap. In practice, that swap is encrypted by the OS, so it is not meaningfully “recoverable” by someone doing normal disk forensics after the fact. The edge case is a high-capability attacker with live access to the machine (or encryption keys/memory state) while you are browsing, in which case “private browsing in RAM” does not protect you, and that is also true for standard "Incognito."

To reiterate, Amnesia Mode is designed to prevent your browser from saving a trail on your own disk after you are done, but it is not a magic cloak against these three classes of risk:

1. A Compromised machine

If your Mac is infected or someone has admin or root access, they can observe what you do in real time. They can read browser memory, capture keystrokes, take screenshots, or hook the network stack. Private or RAM-only storage does not matter if the attacker is already inside the house.

1. Live memory capture

Even on a clean machine, if someone can capture RAM while you are browsing (debug tools, malicious endpoint software, physical access with high privileges), they may extract session data like page contents, tokens, or cookies from memory. Amnesia Mode reduces what is left behind later, but it cannot stop someone from reading what exists right now in RAM.

1. Network-side logging

Even if your local browser leaves no trace, the network can. Your ISP, corporate proxy, DNS resolver, Wi-Fi operator, and the sites you visit can log traffic patterns, DNS queries, IP addresses, and server-side logs. Amnesia Mode is local. It does not erase logs that exist outside your computer. This part we are actively working on, meaning we can "blind" the intermediaries, but we cannot prevent network-side logging completely, as you already know, I'm sure.

In short, Amnesia Mode is about minimizing local persistence after the session ends, not about defeating active surveillance during the session or logs that live elsewhere.