The Safari agent that waits for the page
An AGPL sidebar that calls a WebMCP tool a page already exposed, and shows no button when the page has none.
- Category
- Developer tools
- Who it is for
- Someone who wants a model to use tools a site already published, inside Safari.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Safari browser agent · Safari browser agent
- Original launch
- Watch the launch · Nov 19, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Nov 20, 2026. How we read a launch.
The startup idea
Nart posted a Safari browser agent on November 19. He said WebKit opposes WebMCP, so he built an open-source agent that supports it anyway. The repository is nartmadi/safari-browser-agent. The license is AGPL-3.0. Install is a temporary extension: Safari's Develop menu, Add Temporary Extension, this folder. Unsigned extensions have to be allowed. Open a page that already speaks WebMCP, click WebMCP Agent, and grant that site. A CPU icon picks the model. The providers in the readme are Ollama, OpenAI, Anthropic, Gemini, and Amazon Bedrock. The sidebar can discover and run tools that page exposes through the WebMCP polyfill. It is marked an experimental developer preview. A tool call can change the current site. If a request times out, look at the page before you retry. A consequential tool asks Allow or Cancel. A read-only hint and an untrusted-content hint are respected. The tools button appears only when the page exposes tools. A normal site shows nothing to press. The post says he built a Safari agent that supports WebMCP. The button still waits for the page. This page did not click one.
The opportunity is the sidebar that can only use a tool the site published. A smaller product is one exposed tool, one Allow, and the line that other pages have no button. An agent that clicks any Safari tab is not this readme.
Do not retry a timed-out call without looking. Do not hide the Allow.
The problem
A browser agent that clicks anything is a different product from one that can only use tools the site published.
Who would pay for this?
- Primary
- Someone who wants a model to use tools a site already published, inside Safari.
- Secondary
- A person who will notice that a normal page has no tools button.
- Early adopter
- One WebMCP page, one Allow, the missing-button line.
How could it make money?
Possible models. Nothing here is a claim about what Safari browser agent charges.
- No price. AGPL-3.0.
- A hosted model is still your key.
- The post names no fee.
What would the MVP look like?
- A temporary Safari extension.
- One page that exposes a tool.
- Allow or Cancel.
- The sentence that other pages have no button.
How to validate the idea
- Ask five people what the agent can do on a site that publishes no tools.
- If they say it browses anyway, the line failed.
- Do not add a general clicker to make the post broader.
How to differentiate
- The published tool is the product.
- The button can be absent.
- AGPL-3.0.
- Do not become the browser.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Safari browser agent did not write it.
- Product
- Safari browser agent
- Source
- Safari browser agent
- Film
- Safari browser agent, the button waits for the page
- Posted
- Nov 19, 2026 · 0:46
Product that inspired this idea
Nart's post says WebKit opposes WebMCP, so he built an open-source Safari agent that supports it. The repository is nartmadi/safari-browser-agent. The license is AGPL-3.0. You add the folder as a temporary unsigned extension. A sidebar can call tools a page exposes through the WebMCP polyfill. The model can be local Ollama, or a key for OpenAI, Anthropic, Gemini, or Bedrock. The readme calls it an experimental preview. A tool call can change the site. If a request times out, look at the page before you try again. A consequential tool asks Allow or Cancel. A read-only hint is respected. The tools button shows up only when that page exposes tools. A normal site has no button. This page did not click one.
Posted by @nartmadi. Watch the original launch. No separate product site is listed unless the post itself is the source.
- browser
- agents
Related startup ideas
- A browser inside the coding agent’s terminal
Open a real browser from the agent session so the agent can see the page it just changed.
- A coding agent that runs a small model in the browser
A coding assistant that runs locally in the browser on a small model, for people who will not send the repo out.
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A visible team of agents in a world you can walk into
Use a shared world, not a log file, when several agents need a person to come over and decide.
- An Android remote for coding agents
A phone client for checking projects and steering agents when the laptop is closed.
- An inbox so the agents stay quiet
Collapse every coding-agent thread into one list, and only interrupt when one of them is stuck.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026