HI version is available. Content is displayed in original English for accuracy.
Customers primarily use the Intuned AI agent to automate websites that don't expose APIs. Common use-cases include scraping data, pulling reports, and submitting forms. As the website changes, our agent also helps automatically heal the automation.
On Intuned, browser automations are created by an AI agent and run as code. Our infra captures the context of every run, allowing our agent to debug and maintain the underlying code - to keep the automations working over time. This way, we’re able to offer the predictability, speed, and cost of code, without the painful parts of writing and maintaining it.
Here’s a demo of building a scraper on Intuned: https://youtu.be/ruZP73bK4FU
Here’s a demo of using AI to maintain a project: https://youtu.be/e4R4hLdHBro
Backstory: we were accepted into YC for a completely different idea. During the batch, because of Faisal's background at UiPath, several batchmates asked us whether RPA tools could fill API gaps in their products by automating websites without APIs. When it was time to pivot, we went back to those founders to dig deeper. (RPA in this context is referring to using UI automation to do complete non-testing tasks)
We discovered that the actual hard problem in browser automation is maintenance. Websites change, selectors break, and failures can be painful to reproduce and fix. So in early 2024, we decided to take a crack at this problem with a handful of customers. It needed a fair number of iterations before we landed on our current code-first approach.
How it works: Intuned is infra + agent, deeply integrated.
On the infrastructure side, Intuned is a managed runtime for browser automation code. Projects are usually Playwright-based TypeScript or Python. Users can write them directly in our online IDE, or hand the work off to the agent. Either way, once deployed, the platform runs each project in its own isolated machine and handles auth/session reuse, scheduling, batch execution, concurrency, observability, and the other plumbing around running browser code.
On the agent side, it took us a few iterations to get to the current approach. Our initial attempts were rigid pipelines: collect requirements, inspect the site, generate code, then try to patch whatever broke. It looked reasonable on paper, but real websites are too messy for fixed paths. Late last year, we were planning to ship that version when stronger models landed and harnesses like Claude Code and Codex showed what a more open-ended coding agent could do. We built a prototype on the Claude Agent SDK, it felt much better than what we had, and we scrapped the release and decided to rebuild the agent.
The rebuild came down to three pieces around the SDK: an execution environment for running long agent sessions reliably, a CLI that exposes the platform to the agent so it operates Intuned the way engineers do, and a custom plugin (skills + MCP) built around what we've learned building browser automations.
The infra-agent integration is where the product gets more interesting. The runtime doesn't just run the automation; it captures the context needed to debug it when it fails: params, results, traces, logs. That enables features like Fix with AI, where you can open a failed run and have the agent investigate and prepare a fix.
The same integration powers a feature called self-healing. For configured projects, the platform detects failures, starts an agent session with the relevant context, and either proposes a fix for review or deploys it automatically. Demo: https://youtu.be/IVHIXw0lYMs
We recently also packaged the infra and agent as an API called Web Task API, here is a demo: https://youtu.be/1olRn3l95vw
We strongly believe that browser automations can and should be faster, cheaper and more predictable. Check us out at https://app.intuned.io/, we have a free tier with trial credits for your first few automations. Excited to hear your thoughts, questions, and feedback!

Discussion (53 Comments)Read Original on HackerNews
Not only could this help them keep up with the new security features and redesigns, but they are more than willing to pay for a product that meaningfully improves overall success rate. You should look on twitter/discord for these kinds of groups, they are "reseller"-type communities.
I was reading the blog post about bot detection with browsers. The first layer being the IP address of the browser.
One rather unique scenario I've been trying to work out for a scraper is eliminating network latency. My use of the site is enhanced by the request from the browser having the lowest RTT latency to the webserver as possible. This means being in the same cloud provider.
To do this right now I manually navigate to the site and have a browser extension that clicks at just the right time.
I'd really like to eliminate that manual navigation but every time I've tried adding browser automation outside of the single click from the extension, I'm immediately met with bot detection.
Obviously adding a residential proxy step completely defeats the purpose of the RTT latency optimization.
Do modified browsers drive the overall bot detection heuristic low enough that the cloud IP address itself isn't a red flag? I've seen Camoufox and will try it at some point. What other options are available to drive down the overall "score" so I can still automate the browser but keep the latency low?
> I've tried adding browser automation outside of the single click from the extension, and I'm immediately met with bot detection.
Can you explain how you write your automation? How do you do the click from the extension? Do you use CDP input commands to perform the click (`Input.dispatchMouseEvent`), or do you execute JS code and click the button using `element.click`? using CDP will give you much better score than Executing JS to click a captcha button. JS Execution can be easily detected by any bot detection provider. On the other hand, using CDP to click can mimic actual mouse movement and will make it much harder to detect abnormalities. and the click event will have `isTrusted=true` and handle detection methods related to monitoring JS executions on page.
> Do modified browsers drive the overall bot detection heuristic low enough that the cloud IP address itself isn't a red flag? I've seen Camoufox and will try it at some point. What other options are available to drive down the overall "score" so I can still automate the browser but keep the latency low?
Modified browsers reduce your bot score a lot, and Camoufox is a great option to test out. Will it work? It depends on how the website has set up their bot detection. using modified browser is a must for use case.
At Intuned, we use our own internal forked Chrome to hide the most popular signals, and a lot of the time, the browser alone without a residential proxy can help us bypass most websites, but not all of them(IP reputation has very high heuristic value).
I can't give exact recommendation on what will work with you for sure since each website has it's own ways to handle bot detection , one recommendation I can give is to try to use packages like patchright they can help alot and hide alot of popular signals.
Another recommendation I can make is to try using intuned agent and ask it to help you find a way to bypass bot detection on that website. If you can handle it using network interception or some other scraping technique, the agent is really good in these cases and knows most of the used scraping techniques.
While I understand that not every business wants automation on their site, I know some businesses are totally open to it. But from a technical perspective, it's very difficult to allow well-behaved browser automation while still blocking abusive bots. Web Bot Auth gives website owners / security vendors a lightweight way to allow providers like Intuned.
(I work on the Web Bot Auth implementation for Stytch, now a part of Twilio: https://stytch.com/blog/stytch-supports-web-bot-auth/ )
For lower RTT you’ll need an instance and proxy close to upstream but a real browser will help with scraping detection.
Also, one of our engineers did a write up on bot detection systems and how they work - https://intunedhq.com/blog/how-bot-detection-works
p.s. I've added this comment to https://news.ycombinator.com/highlights. I mention this so more people might learn that it exists and hopefully send us nominations!
On your automation, your tool fed back to me as follows after 3 submissions:
> The CAPTCHA is persistently blocking now — Prosopo's widget appears to have flagged the session/IP due to the repeated submissions. The checkbox won't reset this time. This is expected behavior from their bot protection product. To submit again, you'd likely need to wait a while for the rate limit to clear, or submit manually from your own browser.
Based on your YC page, you went through a couple of pivots over the last years:
- 4 years ago: Intuned - The data assistant for engineering leaders [0]
- 2 years ago: Intuned - The browser automation platform for developers and product teams [1]
- 1 year ago: Intuned Auth Sessions - Build authenticated scrapers and RPA [2]
What was kind of the evolution from YC S22 4 years ago till you arrived at today's launch? How did you find your differentiation in a highly commoditized space? Even within YC, there are many competitors like Firecrawl, Reworkd, BrowserUse, NotteLabs, Browserbase, etc.
Another thing that might interest HN: AI crawlers come with negative side effects for website owners (costs, downtime, etc.), as repeatedly reported here on HN (and experienced myself).
Does Intuned respect robots.txt directives and do you disclose the identity of your crawlers via user-agent header?
[0] https://www.ycombinator.com/launches/Gqr-intuned-the-data-as...
[1]https://www.ycombinator.com/launches/LGE-intuned-the-browser...
[2] https://www.ycombinator.com/launches/Lpq-intuned-auth-sessio...
For your question about how is this different - I think if you dig into those product you will see that our focus is different, many of the companies mentioned are focused on powering agents via APIs, some are focused on enabling users to use AI at runtime, we do feel that our product is somewhat differentiated - the closest one is possibly Reworkd and I would still say the product is somewhat different. Now, the hardest part is actually commenting this with customers and the market in general - and there, we have a lot to figure out!
For robots.txt and user-agents question, we think of ourselves as providing infrastructure and flexibility for our customers to do what they want - we do encourage in our docs that they respect robots.txt but we don't enforce it on a platform level.
Appreciate you taking the time to leave this comment - very thoughtful
I feel that you'll end up being an automation agency (you mentioned UiPath), companies who have the skills and capacity to build, will not need your service. But those who want the full service, you might fill a gap.
I wish you all the best.
What do you think of just reverse engineering the network requests and writing scripts to hit the underlying APIs that the browser is making instead of tackling at the browser automation layer?
Our Intuned agent and Web Task API always use reverse engineering when possible — the underlying agents have access to the network layer and can reverse engineer APIs when needed. At the end of the day, this comes down to what the user needs. We have seen cases where users need data from the network, and in these cases we skip the browser layer. In some other cases, we saw that users need to authenticate via the browser but then all the automation can be done via the network. We have also seen customers who want to get markdown of the pages in addition to hitting the APIs so a browser layer is a must.
Also, imagine that you have a case where you want to scrape 10,000 records from a website, why have AI navigate to every page to do this? why not write the code, run it, and get consistent and fast result? its also predictable, if it messes up, you know what happened and you can trace it to the exact line of code.
Generalized computer use is what will ultimately solve this, but I think there’s real intermediate value in optimizing browser workflows specifically, as a medley of remote browser automation and multi-modal browser use.
We are actually working on open sourcing a plugin that you can use with any coding harness!
If a customer, doesn't want to use playwright, they don't have to given CDP but we most of our templates use playwright.
Intuned as a platform to deploy browser automation adds a lot - anti-bot detection, jobs, observability and more.
for jobs/durability/obs i have sqlite and had codex generate an ugly but functional dashboard
im just curious to know what intune does that is different