Browser Use
Browser UseOpen-source library that lets an agent drive a real browser through the DOM.
Agents that run recurring multi-step jobs over email and calendars.
Recurring operational work with a stable shape — scheduling, intake, follow-ups
One-off tasks — the setup cost dominates
A platform for building agents that watch an inbox or a calendar and run multi-step jobs. It targets the operational work that repeats weekly: intake, follow-up, rescheduling. The boundary to set first is what the agent may send, because an email agent that can send unreviewed is a liability.
Open-source library that lets an agent drive a real browser through the DOM.
Open-source automation with a visual builder you can self-host.
Visual automation with real branching, cheaper than the alternative.
3 alternatives overlap with this one. Compare them →
Reads Cal.com event types and bookings through the API. It is the self-hosted scheduling equivalent of Calendly: availability and bookings as data. The same boundary…
Reads Calendly event types and scheduled events, and can create a booking link. It is a small server with a clear boundary: reading availability is useful, and chang…
Reads beehiiv publications, subscribers, and post metrics. For a writer it answers the context question: how did the last three issues perform, and what does the aud…
Sorts an inbox into reply-now, reply-later, and ignore.
Anti-laziness: splits a task N layers deep before answering.
Tree-of-thought exploration with explicit pruning before any code is written.