Chanhee from the Aside team replied with two interesting points. First, he reminded the user that you can already connect your existing password manager to Aside through Settings > Passwords, letting the browser’s AI agent access your saved credentials. Then he casually dropped something that hadn’t been announced before.

“We’ll ship mobile app soon, so it could reduce some issues,” Chanhee wrote.

The user replied saying they were excited for the mobile app and admitted they actually preferred Aside’s built-in password manager over Apple’s. Chanhee said, “Stay tuned.”

Before you get all excited. Keep in mind that there’s no concrete release date or even any hints of the UI and how it’ll stand out from the sea of mobile browsers. Still, it feels like a pretty natural next step.

When I first wrote about Aside, I mentioned that it’s what Dia and Comet should have been. It wasn’t all praise, though. One of my biggest complaints was performance. The browser felt heavier than it should have, especially for something that was trying to replace Chrome.

The nice surprise was how quickly the team reacted. A later update moved Aside to a newer Chromium version and made the browser noticeably faster in everyday use.

That wasn’t the only improvement. The browser also picked up a handful of useful features after its viral launch, followed by a profile switching system that feels a lot like Arc’s Spaces, making it much easier to separate work and personal browsing.

If you’re interested in trying out this feature, you just have to enable a flag. You don’t have to use Brave Canary or Beta for this, since it’s already live on the latest stable version (v1.92.141). In fact, the update also brings some minor bug fixes and a Chromium version bump. More on that here.

Follow these steps to enable tree stacking for tabs:

1. Update to the latest version of Brave (if you haven’t already). Then, enter brave://flags in the address bar.
   

   

2. Search for the keyword “tree,” and you’ll find an option that says “Brave Tree Tab.”

3. The option is disabled by default at the moment, and you’ll need to enable it from the dropdown menu. Following this, restart your browser.

4. Finally, head to Tab settings (by typing the word ‘Tab’ in settings search), and enable vertical tabs.
   

   

5. You’ll see an option that says ‘Use tree tabs.’ Check that box, and the feature should now work.

6. Open up a website, and then click a link within the site. It should open as a tree.
   

   

Earlier, we covered a story where a Brave employee confirmed that stacking of tabs in a tree-style was “coming soon.” While no ETA was offered at the time, it took almost two weeks for it to start showing up. It’s worth noting that the feature is still technically “experimental,” since it’s currently under a flag and is not directly available. It could be a bit buggy.

Regardless, you can now use Tree Tabs on Brave without needing to install any separate extensions, which is a welcome move.

A few weeks ago, I wrote about how OpenAI’s Atlas browser looked like it had been quietly pushed aside. The biggest giveaway for me was that the release notes had simply stopped. There wasn’t much communication, development looked slow, and it all felt like the project had lost momentum.

Not long after that, OpenAI confirmed what many had started to suspect. Atlas was being shut down in favor of the browser built into the ChatGPT app.

Ever since then, I’ve had an uncomfortable feeling while using Perplexity’s Comet. The similarities are hard to ignore.

I’ve been using Comet off and on for a while now, and it doesn’t feel like the same product it did a few months ago. One issue that I’ve noticed recently has to do with Agent mode. Sometimes it works. Sometimes it refuses to do anything useful. Other times it just gets stuck halfway through a task.

At first, I assumed it was just me. Then I came across multiple Reddit threads from people describing almost the exact same experience. One user wrote, “Agentic browsing is not working,” while another asked whether anyone else was having issues because the feature had become unreliable. That made me feel a little less crazy.

It’s not just the bugs either.

Perplexity seems completely focused on Computer these days. Almost every major announcement revolves around the new product. That’s understandable. Companies shift priorities all the time. But if you’re someone who actually uses Comet every day, it’s hard not to notice how quiet things have become.

The desktop browser hasn’t had public release notes since February. The last entry on Perplexity’s “What’s New” page was about Voice Mode. Since then, nothing.

That reminds me a little too much of Atlas.

I even ran into a strange issue where my Mac installation of Comet sat on version 143.0.7499.40 for what felt like forever. Every time I checked for updates, it would just sit there saying it was checking, without ever finding anything.

Google’s AI ambitions for Chrome continue to grow, and the latest Chrome Canary update for Android offers another glimpse at where the browser is headed. After months of development, Google has finally enabled an early version of a new Gemini-powered autofill search experience that lets users find saved information using natural language.

The feature is still unfinished, but its appearance in Canary marks meaningful progress compared to earlier builds that either crashed outright or failed to load.

This latest addition builds on Google’s recent AI efforts in Chrome, which already include the redesigned bottom navigation bar with Gemini integration and new Indigo AI-powered shopping experiences that we’ve highlighted previously.

The journey of this feature stretches back several months. In March, Google upgraded the Gemini bottom sheet in Chrome Canary by replacing generic prompt suggestions with contextual chips. Instead of asking users “What can you do?”, Gemini began suggesting page-specific actions such as summarizing an article or discussing a video currently open in the browser.

A month later, Google took another step by introducing Gemini Live inside Chrome’s Gemini bottom sheet. Although the interface closely resembled its desktop counterpart, the feature wasn’t functional. Attempts to start Live conversations resulted in microphone or connection errors, showing it was still very much under development. Around the same time, another experimental addition quietly appeared. Google introduced a mysterious “Search Spark” button in Chrome’s keyboard accessory bar. The sparkling icon immediately hinted at AI integration, but tapping it simply caused the browser to crash.

That has now changed.

The latest Chrome Canary release finally brings the new experience to life. Instead of crashing, tapping the Spark icon now opens a dedicated bottom sheet titled “Find and fill info with Gemini.” A notice explains that the feature is “powered by Personal Intelligence with Gemini” and can recall information from users’ connected apps, including Gmail, to help fill forms automatically.

According to a newly published security bulletin, the update addresses multiple vulnerabilities that affect earlier versions of Edge. Some of the flaws could potentially allow attackers to run malicious code on a victim’s device, while others could be abused to cause crashes, bypass security protections, expose sensitive information, or manipulate data.

The advisory doesn’t mention any evidence that these vulnerabilities have been exploited in the wild. Even so, browser updates like this are usually worth installing sooner rather than later since web browsers are one of the most common ways attackers try to target users.

This isn’t the first security update Edge has received this month. Earlier in July, Microsoft shipped another patch that fixed several vulnerabilities in the browser. We covered that release when version 150.0.4078.48 rolled out, so if you skipped that update as well, it’s a good time to make sure you’re fully up to date.

The bulletin lists more than 20 CVEs, including issues tracked as CVE-2026-15764 through CVE-2026-15778, along with CVE-2026-15899 to CVE-2026-15905 and CVE-2026-57980. For most users, the individual CVE numbers aren’t especially important. What matters is that the latest browser version includes fixes for all of them.

You can check your current version by opening Edge, selecting Settings, then About Microsoft Edge. The browser will automatically look for updates and install them if one is available. You’ll usually just need to restart the browser to finish the process.

Besides the vulnerability patches, Edge is also cooking up other privacy features. Earlier today, we highlighted that Microsoft recently introduced a feature that prevents screenshots of protected PDF documents stored in OneDrive and SharePoint, making Edge the first major browser to offer that capability.

Microsoft is tightening security for organizations that rely on Microsoft Purview Information Protection, and the browser is at the center of this change. Starting in August 2026, Microsoft Edge will begin enforcing screenshot restrictions for protected PDF documents opened in the OneDrive for Business and SharePoint web viewers. While the feature itself isn’t entirely new (desktop apps already respect these protections), this rollout finally closes a long-standing gap in the web experience. More interestingly, Edge will be the only browser enforcing the restriction at launch.

Edge becomes the preferred browser for protected enterprise documents

Microsoft says the update extends the “Do Not Allow Screen Capture” protection to PDFs rendered inside the OneDrive and SharePoint web viewers when they’re accessed through Microsoft Edge. Browser-rendered PDFs previously didn’t enforce this Microsoft Purview Information Protection (MIP) control, creating an inconsistency between desktop applications and the web. But once the rollout is complete, organizations using sensitivity labels with No Copy (EXTRACT) Permission will have those restrictions enforced automatically in Edge.

In practice, that means users won’t be able to take screenshots of protected PDFs opened through the supported web viewers in Microsoft Edge. The enforcement is enabled by default wherever applicable, respects existing Purview sensitivity labels and policies, and doesn’t affect PDFs without protection or labels that don’t restrict copying.

But only Microsoft Edge supports it

This is the part that immediately stood out to me. Microsoft explicitly states that other browsers and mobile web aren’t supported at general availability. That means organizations relying on Chrome, Firefox, Brave, Opera, Vivaldi, or any Chromium-based browser other than Edge won’t get the same screenshot enforcement for protected PDFs during the initial rollout.