What Is Rill Browser and Why Is It Trending?
Key Takeaways
- Rill costs $0 and needs no API key. It runs on your existing Claude Code or Codex plan.
- It is a native, WebKit-based Mac browser. Press ⌘E on any page and it routes the task to the right local project.
- Page questions send up to 18,000 characters of page text to your provider.
- Tasks start read-only, and git repositories keep an undo for each edit.
- Limits: macOS 14 or later, Apple silicon only, beta status, no Chrome extensions, no passkeys yet.
- Agents read pages as untrusted text. Prompt injection risk is reduced, not removed.
The Core Architecture Built on Claude Code and Codex
Rill does not run a model. It runs your CLI.
Every AI feature calls the Claude Code or Codex command-line tool already installed and signed in on your Mac. Claude Code traffic goes to Anthropic. Codex traffic goes to OpenAI. Both run under your own account terms.
Press ⌘E and Rill builds a routing request. It holds your note, the page address and title, the selection or the first 2,000 characters of page text, and a catalog of your projects.
The catalog lists folders, stacks, README excerpts, git remotes, and recent commit subjects. Rill builds it from your existing Claude Code and Codex history, so setup is zero.
Everything else stays local. History, agent threads, and project indexes live as files on your Mac. Passwords sit in the macOS Keychain behind Touch ID. Private windows send nothing.
The maker, Manifold AI Inc., says the WebKit base is what makes Rill native to Mac.
Why Developers Are Shifting from Standard Chrome to AI Browsers
Rill's pitch is narrower than a Chrome replacement. It targets one job: the hand-off.
You spot a migration guide, a design reference, or a bug write-up. Then you switch to a terminal, find the right repo, and retype the context. That friction kills small ideas.
Claude Code and Codex both ship a browser inside the agent app. Rill reverses the direction. The agents sit inside the browser, next to the page that triggered the idea.
The maker argues extensions can only improve what the browser already holds. That is a design stance, not a hard limit. Both vendors' Chrome extensions already talk to local agents through native messaging.
Rill's own demos span research, teaching, and newsroom work, so the audience is wider than developers.
How to Use Rill Browser with Codex and Claude
Setting Up Your Existing Subscription Keys Without Extra Costs
There are no keys to paste. Rill reads your CLI sign-in, not an API key.
- Install Claude Code, Codex, or both. Run claude --version or codex --version and compare against the minimums on Rill's site.
- Download the .dmg from rill.love. Drag Rill to Applications.
- Launch Rill. It walks you through signing in to either CLI, or both.
- Open Settings › Agents. Answer with covers tab groups, search, and routing. Send tasks to picks the agent that does the work.
- Leave edits off until the routing earns your trust. New tasks start read-only.
Tab sorting and day summaries also call your provider, so expect them to use plan capacity. Switch them off in Settings if usage matters.
Executing the Command Shortcut (⌘E) for Instant Agent Prompting
Press ⌘E on any page. A note opens over the page with the page attached and a project chosen.
Select first. Highlight the paragraph, table row, or code block that matters. Without a selection, routing reads only the first 2,000 characters of the page.
Then write the task in plain words. Example: "Migrate us to the API in this guide. Touch only the payments module." Rill shows the project it picked and why. Change it with one click before you send.
Keep browsing. The At work tray tracks each task as At work, Needs you, or Done. Press ⌥⌘. to stop a task and cut its website access. Review each change file by file in the Threads panel.
Voice is in beta. Set it up once in Settings › Talking, then hold Fn and speak. Your voice is recognized on your Mac and the audio is never sent. Only uncertain sentences go to your provider as text.
Table 1: Standard Browsers vs. AI-Native Rill Browser
| Spec |
Standard browsers (Chrome, Safari) |
Rill |
| Engine |
Chromium (Chrome), WebKit (Safari) |
WebKit |
| Platforms |
Chrome: all major OSes. Safari: Apple platforms only |
macOS 14 or later, Apple silicon only |
| Cost model |
Free browser, separate agent plan |
Free browser, reuses your CLI plan, no API keys |
| Hand-off to Claude Code or Codex |
Copy-paste or a third-party add-on |
⌘E from any page, context attached |
| Project selection |
You pick the repo and re-explain |
Rill picks from CLI history and shows why |
| Agent access to logins |
Extension agents reuse your signed-in profile |
Project agents use isolated tabs; web tasks use your sign-ins |
| Page text sent to the AI |
Depends on the add-on |
2,000 characters for routing, 18,000 per question |
| Extensions |
Large stores |
None yet |
| Passkeys |
Supported |
Not yet |
The Developer Community Verdict: Pros, Cons, and User Feedback
What Early Product Hunt Users Are Saying
Early feedback from the launch thread skews practical. Launch threads also skew positive, so read it as use-case signal, not a reliability audit.
What users reported:
- Fast setup. One user opened Projects after install and found every repo they had touched with Claude Code already listed.
- Design references. Another pointed at a portfolio layout and told the agent to rebuild their homepage the same way.
- Migrations. A third used a library migration guide as the brief for an upgrade, work that used to sit untouched.
What users asked:
- Wrong project. The maker says the chosen project is visible before sending, one click corrects it, and Rill keeps its own per-turn undo snapshots independent of git.
- Extensions. One user called missing Chrome extensions a real cost, mainly for a third-party password manager. The maker points to Keychain imports and says it is open to supporting other managers.
- Reach. Others asked about phone-to-Mac tasks and agents beyond Claude Code and Codex. The maker says mobile is under consideration.
- Differentiation. Other AI browsers put chat beside the page. The maker says Rill instead delegates long-running agent work.
Rill reached the top five of Product Hunt's weekly leaderboard with roughly 380 upvotes in its first days.
Platform Restrictions: Mac-Only Limitations and WebKit Dependence
Rill needs macOS 14 or later and Apple silicon. No Intel Mac, Windows, or Linux build is listed.
WebKit is the engine, so expect Safari-class compatibility. Sites built on Chromium-only APIs, such as Web Serial or WebUSB, may fail, so check them in Chrome. Chrome extensions do not run.
Passkeys do not work yet. Rill's privacy page suggests a password or Safari instead.
Treat the privacy page's limits as the real spec:
- A web task acts as you, with your sign-ins. Stop-before-paying is an instruction to the agent, not a lock.
- Prompt injection is reduced, not solved.
- Codex tasks can read any file your account can, and what an agent reads goes to your provider.
- Agent tabs can reach local dev servers and devices on your network, such as a router page.
- Anything running as your account can read Rill's plain-text files. Turn on FileVault.
For legal and financial teams, data flow comes first. Page text goes to Anthropic or OpenAI under your account terms. Review those terms before sending client pages.
Table 2: Feature Matrix of Developer Coding Assistants
| Capability |
Claude Code |
Codex |
Rill layer |
| Built-in browser |
Yes, clean profile, no saved logins |
Yes, in the ChatGPT desktop app, not the CLI |
Rill is the browser |
| Signed-in browser control |
Claude in Chrome extension, started with claude --chrome |
Extension for Chrome, Edge, Brave, Opera, Vivaldi |
Web tasks reuse your Rill sign-ins |
| Site approvals |
Per-site prompts; classifiers screen built-in browser writes |
Allow once, this site, all sites, or decline |
Stops before paying, sending, posting, deleting |
| DevTools depth |
Console and DOM reads |
Optional full CDP, flagged elevated risk |
Not documented |
| File uploads |
Up to 10 MB per upload |
Chrome needs file-URL access; not in built-in browser |
Not documented |
| Control surface |
--chrome flag, /chrome command, VS Code @browser |
@Browser and @Chrome mentions, TypeScript SDK, MCP |
⌘E; no public API documented |
| Account limits |
Claude plan login; no API keys or cloud providers |
Availability varies by rollout and workspace |
Signed-in CLI, no API keys |
People Also Ask (FAQ)
How to enable browser in coder?
Assuming you mean Codex: the built-in browser ships inside the ChatGPT desktop app and installs automatically. Mention @Browser in a chat or press Cmd+T to open a tab. It is not available in the Codex CLI or IDE extension. For Claude Code, install the Claude in Chrome extension and start with claude --chrome.
Can Codex control a browser?
Yes, through three routes: the built-in browser, a browser extension for signed-in tabs in Chrome, Edge, Brave, Opera, or Vivaldi, and computer use for other desktop apps. Codex also accepts MCP servers, so Playwright or Chrome DevTools MCP can drive a browser in scripted runs.
How to connect Codex to Chrome?
Update the ChatGPT desktop app and open Settings › Computer Use. Choose Chrome, accept the plugin prompt, and install the extension from the Chrome Web Store. Confirm the browser shows Manage. Then start a Codex chat and mention Chrome with @. Use the browser profile where you installed the extension.
How to give Codex access to Chrome?
Approve sites as Codex asks: allow once, allow for this site, allow for all sites, or decline. Avoid all-sites access, which OpenAI flags as elevated risk. Manage allowlists and blocklists under Settings › Computer Use › Manage. Uploads also need Allow access to file URLs in the extension's Chrome settings.
Codex browser plugin & SDK integration?
The SDK wraps the Codex CLI. Install @openai/codex-sdk, call startThread(), then run() with a prompt. The built-in browser is a desktop-app feature, so SDK runs should add an MCP server for browser work. Rill needs none of this because it runs the installed CLI directly.
Legal Disclaimer
This article is provided for general informational purposes only and does not constitute legal, financial, security, or other professional advice, and The Dollar Craft and its authors disclaim liability for any loss arising from reliance on it. Product features, terms, and pricing may change without notice, were compiled from public vendor documentation and community posts that The Dollar Craft has not independently verified, and imply no endorsement by or affiliation with any vendor named, so readers should test any tool in a controlled environment and consult qualified counsel before routing confidential, client, or regulated data through it
Comments
Post a Comment