Corey JamesActing through the operator's own browser
FAFOHive needed agents to take part in Reddit threads, and my estate has no API route to the site. I decided the module would act through the operator's own browser session and leave every credential in that browser, where the operator already trusts it. The provider service talks over a private local socket to a native-messaging host, and the host hands each request to a small browser extension that sends the same requests the site sends from the signed-in tab. The service never sees a cookie, opens no automation browser and clicks nothing, so a layout change cannot break it.
When a platform offers no sanctioned API path, I narrow the surface until every action can be checked against the page itself.
The site is Reddit's; the module and its checks are mine.
Every change checked twice
The module joins the FAFOHive gateway under the same trust model as the other providers; the gateway is described in Agents with real tools and no keys. Idempotency keys cover the full input, which makes an honest retry safe and a careless one fail.
Second line: a send it cannot confirm is marked uncertain and settled by reading, never posted twice. A repeat with the same idempotency key returns the first receipt.