Launch HN: Pomerado (YC F26) – Turn any website into an MCP for agents

Re:Launch HN: Pomerado (YC F26) – Turn any website into an M... by bshafiq on Wednesday November 11, 2026 @02:28PM (#50457395)

Congrats on the launch! The approach of turning unstructured sites into deterministic MCPs is really interesting, especially the self-healing maintenance jobs.

Curious about the failure mode: what happens when a browser action fails or times out? The agent will often just blindly retry the exact same MCP tool call with the exact same arguments. Since the tool call itself returns a 200 OK, standard retry counters miss it, and you just burn tokens while the browser keeps timing out in the background.

Are you doing any payload/state validation at the runtime layer to hard-stop those cyclic failures before the next call, or does the Guardian model handle that?

[ Parent | on HN ]

Re:Launch HN: Pomerado (YC F26) – Turn any website into an M... by alanjm23 on Wednesday November 11, 2026 @02:44PM (#50457606)

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.

[ Parent | on HN ]

Re:Launch HN: Pomerado (YC F26) – Turn any website into an M... by bshafiq on Thursday November 12, 2026 @06:02AM (#50465546)

Makes sense. But what happens if the repair agent itself gets stuck looping?

If the MCP call returns a 200 OK while the underlying browser times out silently, you're just burning tokens. Are you using a deterministic state hash to hard-kill the run, or relying entirely on the repair agent?

[ Parent | on HN ]