Moli by Lexmount - The fastest headless browser for agents and harnesses
by•
Moli by Lexmount is our browser engine built from scratch for AI agents. It starts faster and uses less memory than Chrome.
Use Moli through Lexmount Browser, our cloud browser platform. Run multiple isolated browser sessions with proxy support while we handle the infrastructure. Let your agents browse, fill out forms, and extract data. Try it in our Playground or connect through our SDK.


Replies
Hi everyone! I’m Wangli, one of the makers of Moli by Lexmount and the first engineer hired for the Lexmount cloud platform.
I’d love to share how we think about the platform’s evolution.
As AI moves from generating answers to taking action, growing token usage is accompanied by another need: more agents reading websites, clicking through workflows, and completing tasks in parallel. Those agents need browsers they can rely on.
That’s where we started: reliable cloud browser infrastructure that scales with demand, supports many concurrent sessions, and lets developers pay for what they use.
As browser capacity becomes easier to scale, the next challenge moves up to the agents driving those browsers. Developers also need somewhere to run their agents and automation code. That led us to cloud browser agents and a hosted JavaScript runtime, extending the platform from browser sessions to the work happening around them.
Another direction I’m particularly excited about is connecting cloud execution with local resources.
On the broader Lexmount platform, our SDK already supports a local proxy tunnel for standard cloud browser sessions. With authorization, a cloud browser can reach an internal company portal or a VPN-accessible website through a machine on that network. The browser still runs in the cloud; the local machine provides the network connection. We explain how it works in this post.
That small capability opened up a much bigger question for us: what else could a local client make available to an agent, with the user’s explicit permission? Selected files? A camera? Other local tools?
We’re exploring how agents and browsers could work across cloud and local environments, combining cloud capacity with access to local resources while keeping users in control of what is exposed and where work runs.
That’s the future I’m excited to help build. What would you want your agents to do across your local and cloud environments?
@freelw Love this vision, Wangli! Connecting cloud browsers with local resources could open up so many possibilities for AI agents. Excited to see where we take this next!
Does Moli support modern web standards?
Can I run multiple cloud browsers at the same time?
@jojo_li Hi JoJo! Yes—you can run multiple cloud browser sessions at the same time. Each session is isolated, so you can run separate workflows without mixing cookies or login states. The number of simultaneous sessions depends on your plan; our Pro plan includes up to 25 concurrent sessions.
What kind of workflows are you looking to run in parallel?
How complex network tasks can I automate with the Lexmount browser?
Can I take over a browser session manually if my agent gets stuck?
Is it easy to migrate an existing browser automation workflow to Moli by Lexmount?
How does it handle websites with heavy JS or dynamic content compared with the regular chrome session ?
Hey Product Hunt 👋 I’m Nico, one of the makers of Moli by Lexmount.
I wanted to share how our new Cloud Browser Agent fits alongside Moli and the Lexmount cloud platform:
Moli is the browser engine. It’s open source and built for AI agents, providing page structure, interaction, and rendering on demand.
Lexmount is the cloud platform. We provide managed browsers and web access APIs. Bring your own agent or automation code, and we handle the browser infrastructure.
Cloud Browser Agent carries out the task, using our CAE protocol to understand and interact with web pages. Give it a goal and an optional starting URL. For recurring tasks, save your instructions and output format as an Agent, then create a Run for each execution.
CAE — Content, Action, Effect — connects page content, available operations, and browser-observed changes, using incremental updates to reuse stable page context. For a closer look at how CAE works and the reasoning behind its design, here’s our technical write-up: CAE Protocol.
For developers, this means decisions grounded in browser feedback, less redundant input and token overhead, and an execution trace you can inspect.
What browser task would you want to hand off first?
@xiaoxia_zheng Exactly! Moli is the open-source engine, and Lexmount Browser makes it easy for developers to use that power in the cloud without managing browser infrastructure.
Building agent automation systems, resource efficiency is everything. The 1/7 memory footprint vs Chrome is a real win - running thousands of headless instances becomes viable. Love that it's open-source too, gives more control over the execution layer.