Rill is a free browser for Mac where the Claude Code and Codex agents you already use work beside you. It is an AI-native browser built around the coding agents you already have rather than a new assistant of its own. You browse normally, and when something on a page gives you an idea, you press ⌘E to turn what you are looking at into a task for your agent. Rill finds the right project, passes along the context, and the agent works while you keep browsing. Rill is for people who already run Claude Code or Codex on their Mac and want to hand work to those agents from the page where the thought actually arrived.
An idea used to mean switching to the terminal. The moment you found something worth acting on — a method in a paper, a release note worth testing, a row in a table of consumer prices, or a page whose look you liked — you had to leave what you were reading, open a terminal, and describe from memory what you had just seen. Rill starts from the opposite position: you say it where you found it. Because the browser already holds the page, the text you selected, the row you pointed at with a click, or the paragraph you highlighted, the request travels with its context attached instead of being paraphrased. Rill also knows where the work goes. Your browser knows your projects, so each request lands in the right one without you having to work out which project a passing thought belonged to.
The core gesture is ⌘E on any page. Pressing it opens a small note over the page you are reading, where you write your task or question. Rill finds your projects in your Claude Code and Codex history, and there is nothing to set up — no project list to maintain, no configuration to write. In the demonstrations shown on the site, a task written over an arXiv paper, "Try this method on my data.", is routed to the project longitudinal-study. A task written over the Polars 2.0 release post, "Try this on one lesson.", goes to lessons. A task that carries the page and a single row of a table you pointed at, "Chart this against last year.", goes to newsroom-charts. A task over a type foundry page that carries the page and a paragraph you pointed at, "Make my project pages like this.", goes to portfolio. When the request is not code at all, it goes to the web instead: a note over Wikipedia's article about New York City, "Find a nonstop from SF to NYC, Nov 12 to 16.", is sent on the web, and your agent goes looking in a tab behind yours.
You never have to go and check on the work. While you read, agents at work are shown with their model, and tasks in a project are listed where you can see them. When an agent needs something from you, it asks in the corner rather than making you open a terminal to find out. In the site's demonstration, a task on the web for a nonstop flight sends a bubble over the essay being read: "Nonstop from SF to NYC. Needs your answer. Morning or afternoon departure?" with Morning and Afternoon buttons and a Reply box. You can answer it or keep scrolling; once answered, the agent carries on in the same tab. It reports back when it is done — the sample result for the chart task reads "Done · 2 files changed".
Alongside the agent work, Rill tidies the parts of browsing that accumulate. Your tabs are sorted by AI into themes, each with a one-line summary — the screenshots show groups such as Music videos, Land and climate, Art collection and Space imagery, and on the start page, Art collection and Understanding music. Your history reads like a journal rather than a list: it shows where you went, what you asked for, and what got done, summed up in a sentence with a ribbon of the day. One example reads "History for Sunday, September 27: 64 pages in six stretches". After a few weeks, every project your agents have touched appears on one map — 38 projects in the demonstration, named by AI into areas such as Research and data, Writing and publishing, Design, Teaching, Home and life, and Tools and code, with the finished ones lit as Done. Talking is also available in beta: hold Fn and say the task instead of typing it, after setting it up once in Settings › Talking.
Rill's approach is to make the browser the interface for the agent, on the reasoning that the best interface for agents is just the browser. Setup is three steps. You download Rill and drag it to Applications; you sign in to Claude Code or Codex, using either or both, with Rill walking you through it; and then you press ⌘E on any page. The AI features run the Claude Code or Codex on your Mac, under your own account, so Rill runs on the plan you already have — no new subscription and no API keys. Everything the agent needs about your projects and your context is already present in the browser window you are looking at.
The benefit is that the gap between noticing something and acting on it closes. You do not copy a URL, re-describe a table row in words, or try to remember which project a thought belonged to; the page, the selection and the destination travel with the request. You keep reading while the work happens, and you are told — in a bubble beside the page — when you are needed and when the task is finished. Because your tabs are grouped and your history is summarised by day, the browsing you did around the work is legible afterwards rather than lost. And because Rill presents the result in the same window, checking on the agent no longer means leaving what you were doing.
The scenarios on the site show the range. You are reading a paper on changepoint methods and send "Try this method on my data." to a project called longitudinal-study; while you browsed the page, the chart got made — a chart titled "July surface water temperature: one step, not a slope" for three lakes. You read a release note worth testing and send it to your lessons project. You point at one row of a table of consumer prices and ask for it to be charted against last year, for a newsroom project. You find a page whose look you like and send it to portfolio with "Make my project pages like this." You ask the same way for something that is not code at all — a nonstop flight from SF to NYC in November — and your agent goes looking in a tab behind yours. Or, holding Fn, you say "Add a dark mode to the customer portal that follows the system setting." and the agent gets to work in the customer-portal project.
Rill is for Mac users who already run Claude Code, Codex, or both, and who want to point those agents at things they find while browsing; browsing itself works without either, and Rill also works as a browser without an agent. Without an agent you can ask about a page and get the answer beside it from the agent you already use, compare up to six tabs in a table that quotes each page, and let agents in a project read the web in tabs of their own, without your logins, which you can take over when you want. The basics are covered too: passwords in your Keychain, private windows, and sign-ins brought over from Chrome, Arc or Safari. Privacy is local by design — your history and passwords live on your Mac, history is kept as files for as long as you choose, passwords sit in the Keychain unlocked with Touch ID, and tab sorting and day summaries can be turned off in Settings. 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. Rill is free, in beta, and runs on Macs with Apple silicon on macOS 14 or later.
Rill's proposition is simple: your browsing and your agents in one window. It is a free Mac browser that runs on the Claude Code or Codex plan you already have, turns any page into a task with ⌘E, routes that task to the right project automatically, and lets you keep browsing while the agent works beside you.