alanjm23

Makes sense, how do you manage sites with Akamai / DataDome / other vendors? Would love to learn more

Hi! We have our tools try to confirm every write before they end. This can be quite difficult in reality, so we do have a "can't tell" state as well that we're trying to cut down on.

Hi! We don't recommend using this on LinkedIn, we're confident in our tech but don't want anyone to get banned. You could try Ploid?

Hi! I was an ex-agent / digital strategy consultant at McKinsey. Before that I studied math and did classical ML research

Thanks! When a browser action fails or times out, the repair agent should step in to fix the integration and prevent retries from looping. There are also a few conditions where we automatically kick off a repair without a failing job, such as a streak of rejected inputs or site errors. This is to try and prevent silent failures.

Thanks! We self-heal integrations on-the-fly. So when an execution fails or identifies a large site change, we have a repair agent that steps in and fixes the deterministic tool.

Yep, I think the primary difference between us and WebMCP is that Pomerado doesn't require participation from the website owner. So for WebMCP the site has to opt in, while Pomerado works on any site.

For our hosted version, the session runs in our hosted browser. For the open source, it runs on a local browser.

In the hosted version, users can choose to pass logins at runtime or store them in our vault. Once a user logs in, we keep their session as a Chrome profile and attach it to a sticky IP, so that they stay logged in for longer.

Deterministic tools return only the structured fields, and don't parse the whole browser DOM. Since tools are deterministic, we also reduce the risk of prompt injections.

Great that you're building as well, we think it's a really interesting space.

We don't have a maintenance-specific dashboard. We do maintenance at execution time, so the dashboard paradigm doesn't apply as well. Instead of proactively checking for site changes, we check at execution time and repair integrations on-the-fly, when necessary.

Hi! Unlike traditional scrapers we don't parse the entire DOM on every tool call. Because we build custom integrations for every site, we can be more targeted in our approach, like only checking specific fields.

We don't edge-cache or deduplicate calls, to give users live data.

For session isolation, we give each worker its own browser, cookies, and IP to isolate user sessions and prevent rate limiting.