Flakes
Flakes is a native macOS browser built on SwiftUI and WebKit, combining keyboard-first navigation with Drift AI, which answers questions across your open tabs and translates pages in real time. Browsing data stays on the device.
What is Flakes?
Flakes is a native macOS browser written in SwiftUI on top of WebKit, shipped as a universal binary for Apple Silicon and Intel and requiring macOS 14.0 (Sonoma) or later. The publisher presents it as an AI-native, keyboard-first browser, designed for thinking, not scrolling, and the interface follows that line: no permanent address bar, no tab overload, and a focus mode (⌘Enter) that hides everything except the page content.Navigation is built for the keyboard. h/j/k/l move around the page, f displays link hints, Shift+F opens a hinted link in a new tab, and a single command palette (⌘K) is the entry point for history search, commands, URLs and AI queries alike. Around that core sit split view (⌘|), multiple profiles with quick switching (⌘⇧P), private browsing (⌘⇧N), customizable shortcuts and drag-and-drop tab reordering.The AI layer is called Drift AI. It reads the open tabs and returns direct answers across all of them, translates pages in real time and supports a deeper conversation about whatever is on screen; since v1.2.0 that conversation lives in a sidebar (⌘⇧A) rather than the floating panel introduced in v0.9.0. The v1.2.0 release notes cite Claude 4.6, GPT-5.4 and Gemini 3.1 Pro. Two routes lead to the AI features: Flakes AI, the publisher's own API service reserved for Pro and Premium subscribers, or your own API keys, free to any signed-in user since v1.2.1.Privacy is presented as an architectural choice: browsing data stored locally, ad blocking on by default through uBOL rules downloaded on first use then refreshed periodically while the filtering itself runs on the machine, and a private mode that keeps no history and stays isolated in memory. The only request to the publisher's servers described by the privacy policy is the update check.Flakes is also unusually open to automation for a consumer browser: a native MCP server for LLM control (v1.1.0), 22 agent tools and an OpenClaw Gateway integration (v1.2.0), an interactive JavaScript console in the DevTools, and a shell command install for terminal use. Distribution is outside the Mac App Store, as a DMG or ZIP from GitHub Releases. The homepage is candid about maturity: Flakes is still early, built by a small team.
What it does
- Answer a question by reading across every open tab at once (Drift AI)
- Translate a page in real time
- Open an in-depth conversation about the content on screen, in the sidebar (⌘⇧A)
- Search history, run a command or open a URL from the ⌘K command palette
- Expose 22 agent tools through a native MCP server: navigate, snapshot, click, fill, scroll, get_links, get_text, get_console, search_history and others
- Accept remote driving by an AI agent through the OpenClaw Gateway integration
- Block advertising locally with uBOL rules, and strip the interface down to the content alone with focus mode (⌘Enter)
When to use Flakes / When not to
A quick filter to help you decide if Flakes is the right fit.
When to use Flakes
- macOS power users who work at the keyboard and are comfortable with vim-style keys and a command palette
- Developers who want a browser they can drive: native MCP server, JavaScript console in the DevTools, shell command install
- Research-heavy profiles living at twenty open tabs, who want direct answers drawn across every page at once
- Readers of foreign-language content, thanks to real-time page translation
- Privacy-conscious users: browsing data kept locally, ad blocking on by default, private mode isolated in memory
When not to use Flakes
- Windows, Linux, iOS and Android users: only a macOS build exists
- Anyone still on macOS earlier than 14.0 (Sonoma), excluded since v1.2.x, where v1.1.0 and earlier required 13.0
- Teams that need a data processing agreement, documented GDPR compliance or contractual hosting commitments: none of it is published
- Users attached to the mouse, to a permanent address bar and to a Chrome extension ecosystem: the product deliberately bets the other way
- Buyers who want to know the price before installing, and organizations that require a Mac App Store distribution or an identified publisher
How to use Flakes
A typical end-to-end flow, from setup to results.
- Open the Download page on the Flakes site, which redirects to the latest GitHub release of the chagel/flakes repository
- Take Flakes-vX.Y.Z-macOS.dmg, the recommended file, or the .zip archive
- Open the DMG and drag Flakes.app into the Applications folder
- On first launch, expect a macOS security warning: right-click (or ctrl-click) the app and choose Open, or run xattr -cr /Applications/Flakes.app in the terminal
- Start browsing straight away, since no sign-up is required to use the browser itself
- Press ⌘K to open the command palette, the single entry point for history, commands, URLs and AI queries
- Learn the movement keys: f shows link hints, h/j/k/l move around the page, Shift+F opens a link in a new tab
- Use ⌘Enter for focus mode, ⌘| for split view, ⌘⇧N for private browsing and ⌘⇧P for the profile switcher
- Press ⌘⇧A to open the AI chat in the sidebar
- To switch the AI features on, create an account with Email, Apple or Google, then either enter your own API keys or subscribe to Pro or Premium to use Flakes AI; shortcuts can be customized in the settings, and Flakes can be installed as a shell command for terminal use
Pros & Cons
Pros
- Free to download and free to browse, with no sign-up and no account
- AI features usable without a subscription since v1.2.1, by supplying your own API keys
- Browsing data kept on the device, with no tracking cookies or analytics claimed; the single outbound request to the publisher is the update check, limited to the app version and the OS version
- User API keys stored in the macOS Keychain and never transmitted to the publisher's servers
- Native SwiftUI and WebKit application: instant cold start and a minimal memory footprint, as announced
- Automation openness that is rare in a consumer browser: native MCP server, 22 agent tools, OpenClaw Gateway
- Sustained release cadence, from v0.8.4 on 19 December to v1.2.1 on 21 March
Cons
- macOS only, and macOS 14.0 or later since v1.2.x where 13.0 was enough before: raising the requirement excluded machines mid-course
- No public pricing: the Pro and Premium plans are named, but no amount appears on the site or in the release notes
- No publisher identification: no legal entity, no postal address, no country of establishment, and a single contact channel, hello@flakes.ai, with no contact page or help center
- No mention of the GDPR, no data processing agreement, no sub-processor list, no retention period
- Page content is sent to the publisher's servers as soon as Flakes AI is used
- Distribution outside the Mac App Store: a macOS security warning appears on first launch and has to be worked around manually
- Young project, described as still early and carried by a small team, with a GitHub repository at 3 stars and 0 forks; no interface language list is published either
Pricing & Plans
A permanent free plan is available rather than a time-limited trial: the browser is free to download and can be used without creating an account, and since v1.2.1 the AI features are free to any signed-in user who supplies their own API keys. Two paid tiers, Pro and Premium, are named in the publisher's release notes, together with a 7-day Pro trial for new users and a reference to earlybird pricing. No amount and no currency are published for either tier: the site has no pricing page, the release notes quote no figures, and a targeted search returned none. The lowest paid entry point therefore cannot be stated, and is only discovered after installing the application and creating an account.
- Free
- Pro
- Premium
Data, GDPR & hosting
A consolidated view of how Flakes handles your data.
GDPR overview
No GDPR implementation is documented. Checked on 23 August 2026 across the four public pages, in the visible text and in the archived HTML, the words GDPR, data protection and CCPA return zero occurrences. There is no stated legal basis, no data protection officer, no Article 27 representative, no described right of access, rectification, erasure or portability, and no mention of transfers outside the EU, of standard contractual clauses or of a data processing agreement. What stands in place of a framework is a privacy policy last updated on 15 December 2025, describing local storage and a single outbound update check, plus one published contact address, hello@flakes.ai, presented as the channel for privacy questions. The robots.txt does reserve rights under Article 4 of EU Directive 2019/790 on text and data mining, but that is a standard content-signals file, unrelated to the GDPR.
Who owns the data?
The terms claim ownership of the product only: Flakes and its original content, features, and functionality are owned by Flakes. Nothing in them assigns rights over what the user browses or creates. The privacy policy lists browsing history and visited sites, sessions and open tabs, preferences and AI-generated content as stored locally, and states that this data never leaves your device unless you explicitly choose to export it. An optional account adds an email address, a name if the sign-in provider supplies one, subscription status and billing information; the publisher says it does not share account information with third parties except for payment processing, without naming the processor. User-supplied API keys stay in the macOS Keychain.
Reuse rights
Flakes grants a limited, non-exclusive, non-transferable license to use the software for personal or commercial purposes, so anything produced while browsing can be reused at work without asking permission. The terms place no restriction on how users reuse their own browsing data or the content generated inside the browser, and grant the publisher no license over it; the privacy policy presents an explicit export as the only way that data leaves the device. The limits apply to the software rather than to the data: reverse engineering, decompiling and disassembling are prohibited except where the law allows them, as are breaking the law, infringing the rights of others, distributing malware and attempting unauthorized access to systems or networks.
Data retention & training
Hosting summary
No hosting country and no hosting region is mentioned anywhere on the site. Browsing data — history, sessions and open tabs, preferences, AI-generated content — is described as stored locally on the device, and user-supplied API keys stay in the macOS Keychain and are never transmitted. The publisher's servers are involved in two cases only: the update check, about which the privacy policy states No personal information, browsing history, or identifiable data is transmitted during this check, and the processing of page content by Flakes AI. The location of those servers is not specified. No jurisdiction is named, no sub-processor is disclosed, no data processing agreement is offered and no international transfer clause exists; the uBOL blocking rules are downloaded from an external source that is not named either. The marketing site itself is served behind Cloudflare, on the anycast address 172.67.218.81 in AS13335 with a node geolocated in San Francisco, but that describes the website's infrastructure rather than the Flakes AI service, and cannot be read as a hosting country for user data.
Things to keep in mind
Risks and trade-offs to weigh before adopting Flakes.
- The content of the pages you visit is sent to the publisher's servers as soon as Flakes AI is called, including on sensitive pages such as banking, health or an intranet if the chat is open on them
- AI answers that synthesize several tabs at once invite over-reliance and quietly erode the habit of opening and checking primary sources
- Installing outside the Mac App Store means bypassing the macOS security warning, by right-clicking Open or running xattr -cr: a gesture that should not become routine, since it disables a system protection
- No GDPR framework is published: no legal basis, no described rights, no data protection officer or Article 27 representative, and no retention period or deletion procedure for account and billing data
- The prices of the paid plans are not public, so the subscription commitment is only discovered after installing the application
- Dependence on a project the publisher itself calls still early, carried by a small team, while the terms state that Flakes is provided as is and that continuous availability is not guaranteed
- The publisher is unidentified — no legal entity, no postal address, no jurisdiction — which makes practical recourse close to impossible in the event of a dispute
Setup & Integrations
Technical difficulty
Installation is a standard macOS routine: open the DMG, drag Flakes.app into Applications. The one documented friction point is the security warning on first launch, the application shipping outside the Mac App Store — right-click then Open, or run xattr -cr /Applications/Flakes.app. Browsing needs no configuration. Switching on the AI features adds an account plus either personal API keys or a subscription. Advanced uses (MCP server, OpenClaw Gateway, shell command, JavaScript console) are developer territory. The real learning curve is not the install but the vim-style navigation and shortcuts.
Deployment
Integrations
Behind Flakes
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Which platforms does Flakes run on?
Do I need an account to use Flakes?
How much does Flakes cost?
Does my browsing data leave my Mac?
Is the content of the pages I visit sent anywhere?
Can I use my own API keys?
Is there a built-in ad blocker?
Can the browser be automated?
Where do I download the application?
Does the site document GDPR compliance?
Should you pick Flakes?
Flakes is a young product with a very clear point of view. Its first public releases date from mid-December, v1.2.1 landed in March, and the pace has been quick enough to include changes of direction the publisher does not hide: the macOS requirement was raised to 14.0, the AI chat moved from a floating panel to a sidebar, and the AI features were opened to personal API keys. The product bet is legible on every screen: keyboard first, minimal interface, and an AI that reads the tabs you already have open instead of a chatbot bolted onto the side.Privacy here is built into the architecture rather than promised in prose — browsing data local, ad filtering executed on the machine, API keys in the Keychain — which makes the legal side all the more striking. There is no legal entity, no address, no jurisdiction, a single contact email, and not one mention of the GDPR across the four public pages. Two paid plans are named without any published price, so the cost of a subscription is only discovered after installing.The result is a tool worth the detour for macOS power users, developers and research-heavy profiles who spend the day in twenty tabs and a terminal: the core of the product is genuinely free, including the AI features when you bring your own keys, and the automation surface (native MCP server, 22 agent tools, OpenClaw Gateway) is rare in a consumer browser. It is not a tool for an organization that needs a data processing agreement, an identified publisher or a documented retention policy, nor for anyone who wants to know the price before installing. Try it as an individual, treat the legal and pricing opacity as a genuine reservation, and keep sensitive browsing away from the AI sidebar.
- Choosing a selection results in a full page refresh.
- Opens in a new window.