This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Hands free: you never take the screenshot. Your agent asks over a local MCP server and gets one fresh capture plus the on-screen text, mid-task, without you cropping or pasting anything. Playwright already covers the DOM. Noru covers what it can't: native apps, simulators, system UI, final rendered pixels, and work spanning several apps. Nothing is uploaded. Captures stay on your Mac, Noru observes only, and every observation is acknowledged on screen first.
I built Noru because I was tired of the screenshot loop. Every time my coding agent needed to see a native app, a simulator, or a layout bug that doesn't exist in the DOM, I'd stop, screenshot, crop, paste, and re-explain. The agent was capable. It just couldn't see.
Two things worth knowing up front.
It's hands free. You don't take the screenshot. Your agent asks over a local MCP server, mid-task, and Noru hands back one fresh capture plus the on-screen text. You aren't in the loop at all.
It fills a gap rather than replacing anything. If your agent is working on a web page, Playwright's structured browser state is the better tool, and Noru's own docs say exactly that. Noru is for what the DOM can't describe: native apps, simulators, system UI, final rendered pixels, and workflows that span several apps at once.
Nothing is uploaded. Captures stay on your Mac, Noru observes only (it never clicks or types), and every observation is acknowledged on screen (pop up) before the agent receives it.
No comment highlights available yet. Please check back later!
About Noru Flow on Product Hunt
“Let your coding agent see what's on your screen”
Noru Flow was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #69 on the daily leaderboard. Hands free: you never take the screenshot. Your agent asks over a local MCP server and gets one fresh capture plus the on-screen text, mid-task, without you cropping or pasting anything. Playwright already covers the DOM. Noru covers what it can't: native apps, simulators, system UI, final rendered pixels, and work spanning several apps. Nothing is uploaded. Captures stay on your Mac, Noru observes only, and every observation is acknowledged on screen first.
Noru Flow was featured in Mac (103.7k followers), Developer Tools (519.8k followers), Artificial Intelligence (479.1k followers) and OpenAI Day (39 followers) on Product Hunt. Together, these topics include over 218.2k products, making this a competitive space to launch in.
Who hunted Noru Flow?
Noru Flow was hunted by Glendon Chin. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Noru Flow stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Glendon Chin
Hey Product Hunt, Glendon here.
I built Noru because I was tired of the screenshot loop. Every time my coding agent needed to see a native app, a simulator, or a layout bug that doesn't exist in the DOM, I'd stop, screenshot, crop, paste, and re-explain. The agent was capable. It just couldn't see.
Two things worth knowing up front.
It's hands free. You don't take the screenshot. Your agent asks over a local MCP server, mid-task, and Noru hands back one fresh capture plus the on-screen text. You aren't in the loop at all.
It fills a gap rather than replacing anything. If your agent is working on a web page, Playwright's structured browser state is the better tool, and Noru's own docs say exactly that. Noru is for what the DOM can't describe: native apps, simulators, system UI, final rendered pixels, and workflows that span several apps at once.
Nothing is uploaded. Captures stay on your Mac, Noru observes only (it never clicks or types), and every observation is acknowledged on screen (pop up) before the agent receives it.