Rill Browser

Rill is a free browser for the Mac where your Claude Code and Codex agents work beside you. It runs on the Claude Code or Codex plan you already have, and its purpose is simple: let you ask for work from the exact page you are already looking at, instead of leaving the browser to describe it somewhere else. Rill is for people who browse the web and build things at the same time — developers, researchers, writers, designers and teachers — and it keeps your browsing and your agents in one window. You can search, enter an address, or send a task from the same field, then carry on reading while the work happens. Rill starts from a specific frustration: an idea used to mean switching to the terminal. You found something on a page, then had to leave the page, open a terminal, find the right project, and restate the context you were just looking at. Rill's answer is that you now say it where you found it. The same problem shows up in browsing itself. Tabs pile up with no structure, and history becomes a flat list of timestamps that tells you nothing about what you were doing or what got finished. Rill is built to close both gaps: it carries the page you are on into the project that should handle it, and it turns your browsing into something you can read back later — where you went, what you asked for, and what got done. The core gesture is ⌘E. Press it on any page and a note opens over the page, holding what you were looking at — the page itself, or a paragraph or row you pointed at with a click — plus whatever you type. You describe the task in plain words, and Rill decides which project it belongs to. It finds your projects in your Claude Code and Codex history, so there is nothing to set up: no configuration, no mapping of folders. In the product's own examples, a task to 'Try this method on my data' routes to a project called longitudinal-study; 'Try this on one lesson' routes to lessons; 'Chart this against last year' routes to newsroom-charts; and 'Make my project pages like this' routes to portfolio. The project field shows Choosing a project, then the choice, then Sent. Not every request is code. When a task isn't meant for a project — finding a nonstop flight from San Francisco to New York, for instance — the destination reads On the web, and your agent goes looking in a tab behind yours. You keep reading. Agents tell you when they need something instead of waiting for you to check on them: in one example, Claude Code raises a bubble over the essay you are reading with the question 'Nonstop from SF to NYC. Needs your answer. Morning or afternoon departure?', offers Morning and Afternoon buttons, and carries on in the same tab after you answer. When a result lands, it lands where you were: one demonstration shows a chart titled 'July surface water temperature: one step, not a slope' appearing while you browsed the page, from the longitudinal-study project, marked Done · 2 files changed. Rill also organises the browsing itself. Tabs are sorted by AI into groups by what you were doing, each group carrying a one-line summary — in the sample start page, Music videos, Land and climate, Art collection and Space imagery. Task tabs sit among them, and a task tab on the web shows a thin red-orange line at its edge to mark work in progress. History becomes a journal rather than a log: a day is broken into stretches, each summarised in a sentence — for example, 64 pages in six stretches on Sunday, September 27, with 'Morning news and weather', 'Changepoint methods paper' (a task sent to lake-temps, done) and 'CPI chart for the newsroom' (a task sent to newsroom-charts, done) — plus a ribbon of the day and the individual pages with timestamps. After a few weeks, every project your agents have touched appears on one map: 38 projects in 6 areas named by AI, including Research and data, Writing and publishing, Design, Teaching, Home and life, and Tools and code, with finished work lit as Done. How Rill works overall is deliberately light. The AI features run the Claude Code or Codex installation on your Mac, under your own account, so Rill adds no model of its own and no API keys. Setup is three steps: download Rill and drag it to Applications; sign in to Claude Code or Codex — use either, or both, and Rill walks you through it; then press ⌘E on any page, and Rill finds your projects for you. Agents read pages as untrusted text, new tasks are read-only until you allow edits, and in git repositories each edit can be undone. A task on the web is told to stop before the step that pays, places an order, sends, posts or deletes unless you plainly told it to go through with it, and it cannot type into password, card or one-time-code fields. In a project, an agent browses in tabs of its own, without your logins, and clicks or types only when you allow it. The outcome is that context switching largely disappears. You no longer stop what you are doing to explain it somewhere else: the page, the highlighted paragraph or the pointed-at table row travels with the request, and the agent starts with the context you already had. Because projects are found for you from history, the cost of starting a task is a keystroke and a sentence. Because agents ask their questions inline and report when they are done, you are not polling them in another window — you answer or keep scrolling. And because tab groups, day summaries and the project map are generated from what you actually did, the record of your work stays legible: you can see which stretches of the day produced something and which projects your agents have touched. Concrete scenarios appear throughout the product's own material. A row of a consumer-price table, pointed at with a click, becomes 'Chart this against last year' in a newsroom-charts project, and the chart is waiting when you look. A release note for Polars 2.0 becomes 'Try this on one lesson' in a lessons project. A type foundry's page, with a paragraph pointed at, becomes 'Make my project pages like this' in a portfolio project. A city article becomes 'Find a nonstop from SF to NYC, Nov 12 to 16' — a task on the web. Beyond agent tasks, Rill works as a browser on its own: ask about a page and the answer opens beside it from the agent you already use; compare up to six tabs and get a table that quotes each page; let agents in a project read the web in tabs of their own. And with the beta talking feature, hold Fn and say the task out loud. Rill is currently free and in beta, for Macs with Apple silicon running macOS 14 or later. There is no new subscription and no API keys; the AI features run on the Claude Code or Codex plan you already have, and browsing works without them. Privacy is local by design: your history and passwords live on your Mac. History is kept as files on your Mac, for as long as you choose; passwords are saved in the Mac Keychain and unlocked with Touch ID; AI features run under your own account; and tab sorting and day summaries can be turned off in Settings. The browser's basics are covered too — passwords in the Keychain, private windows, and sign-ins brought over from Chrome, Arc or Safari. Rill lets you know when a new version is out. Rill's proposition is compact: your browsing, your agents, one window. It is a browser first — search, tabs, private windows, imported sign-ins, a Keychain for passwords — with an agent layer that uses the Claude Code or Codex setup you already run. Press ⌘E on the page in front of you, Rill finds the right project and passes the context along, and the work happens while you keep reading. Tabs sort themselves, history reads like a journal, and every project your agents have touched gathers on one map. Free, in beta, on Apple silicon Macs, and built on the plan you already have.