Herdr · the Browser
A browser for engineers and marketers. 350 KB.
It sits in Herdr beside your terminals and your agents, one press from App. Your dev server, the open web and your agents' work, in the window you already have open.
Not in the public install yet. It is running at ONE today.
The numbers
It draws pages with Safari's engine, which every Mac already has. No Chrome to download (Chrome takes 1.5 GB on disk), no Electron to run.
It took 155 to 236 ms before. Scrolling keeps up with your scroll: 25 of 30 steps a second.
A tab you are not looking at sleeps, WebKit included (the median across 5 runs). A still page on show uses 1.6%.
Measured 18 November 2026 on the viewer running at ONE (the one on dev, installed that day): the median of 5 runs
of its own bench (packages/herdr/one-view/bench.py) on a busy Apple Silicon Mac, and
stat for the size. CPU counts the viewer and the WebKit processes it started.
Memory, next to Chrome
A little lighter for one page. Heavier at five. We measured both, so we show both.
Chrome used 436 MB for the same page.
Chrome used 1,098 MB, less than this. Each tab here is its own small viewer with its own WebKit helpers, about 90 MB before the page, so Chrome pulls ahead as tabs add up.
The same tab used 599 MB on show. Hiding a tab stops it using the processor. It does not give the memory back.
Measured 18 November 2026 on the viewer running at ONE and Google Chrome 157, one after the other: Chrome from a fresh profile each time, ONE from its own scratch profile. We added up every process each one started: for ONE the viewer and its WebKit page, graphics and network processes; for Chrome the browser and all its helpers, its built-in extensions included. The number is the one Activity Monitor shows as Memory. One tab is one.ie. Five tabs add Wikipedia's page on web browsers, Hacker News, The Verge and ONE on GitHub, at about 960 by 680, read 28 seconds after opening. The median of 8 runs of ONE and 7 of Chrome for one tab, and 3 each for five, on a busy Mac (load 7 to 26). Chrome's numbers swing more from run to run than ONE's. Safari was not measured: it cannot start from a clean profile, so its number would carry whatever else is open in it.
For engineers
Your dev server, one press from your terminal.
- Running at ONE today localhost first. One press opens :4321. A port with nothing on it says so in the bar, never a blank pane.
- Running at ONE today Phone and tablet. One press puts the page in a 390 or 820 wide window beside the full one.
- Running at ONE today Tabs, back, forward, reload and pop-out windows. Each Herdr space keeps its own tabs.
- Coming A console (errors first) and a network list, both readable by your agent, so it can debug the page it is looking at.
- Coming Point and copy: an element's selector, its text or a picture of it. The whole page as markdown for an agent.
For marketers
Show it a job on a site once, and it repeats the job after that without asking an AI. None of this is built yet; the design is written.
- Coming An AI works a site out once: where the price is, where the search box is. The steps that worked are kept and repeated with no AI, so the next visit costs a page load, not a model call.
- Coming Scrape at a polite pace. What it reads goes into your graph, and the next read comes from there before the network.
- Coming Compare prices and pages across sites from the stored results.
- Coming Buy through your spend limit. It names the amount, the payee and the item first. Over your limit, it asks for your Touch ID.
For agents
The same browser, driven by a command instead of a mouse.
- Running at ONE today An agent in Herdr opens a tab, sends it to an address and closes it with one command each: herdr-app do tabs-one.browser:new, go:<url>, close:<n>.
- Coming One door with read, click, type, a picture, the console and the network, all in JSON: one browse.
- Coming Its own session per agent, cookies kept apart, signed in only by you.
- Running at ONE today It does not pretend to be a person. No faked fingerprints, no CAPTCHA solving.
What it defends, and what it accepts
A browser that only lists its defences is hiding the rest.
- The address
Defends. The bar shows the host as the connection sees it, with a lock for https and "Not secure" for http. A lookalike with foreign letters stays in punycode, in red: xn--pple-43d.com, not apple.com.
Accepts. A misleading name spelled in plain letters shows as it is. The bar does not judge it.
- Herdr itself
Defends. A page in the Browser cannot run a Herdr command or open an agent. A link you press loads in the same pane.
Accepts. The page runs its own scripts, as it would in Safari.
- Sign-ins
Defends. No sign-in window and no passkey hand-off from the Browser. Your Touch ID stays yours.
Accepts. Sign in to a site that needs a passkey in your usual browser.
- Cookies
Defends. Nothing yet: a separate jar per agent is in security review.
Accepts. Today every Browser tab shares one set of cookies, the same set the App panel uses.
- The engine
Defends. Safari's WebKit, updated with macOS.
Accepts. What Safari cannot render, this cannot either.
Get Herdr with ONE
Not in the public install yet. The pack on GitHub is an earlier version, without the Browser. It comes to the public install after a security review, when we publish it.
What it installs today: Herdr if you do not have it, ONE's layout and its panels, each checked. Run it again any time: it replaces only what changed and keeps a backup of anything it replaces.
git clone https://github.com/one-ie/one.git
cd one
bash packages/herdr/install.sh
Needs an Apple Silicon Mac (M1 or newer) and node. Take it out with
bash packages/herdr/install.sh --remove. The pack on GitHub