Pluno

Hey makers! Here’s what Claude & other browser agents got wrong: They use software like humans. They wait for pages. They stare at screenshots. They click buttons. They get stuck in dropdowns. You’ve probably seen this - impressive for a demo, painful when you actually need work done. So we built Pluno. Pluno skips the UI entirely and talks directly to the APIs underneath your web apps. You tell it the outcome, and it gets the task done in the background. No clicks. No dropdowns. No babysitting. Just: Done ✅ You can use Pluno as a browser extension to update records, extract data, fill forms, run bulk actions, create dashboards, and handle annoying SaaS tasks that normally eat up your day. We benchmarked Pluno across 312 real-world tasks in 24 tools (incl. HubSpot, Notion, Stripe, Linear), and the results speak for themselves: 34% higher success rate than Claude’s browser extension, at ~14x the speed. Why we’ve built it? Because we loved the idea of Claude’s browser extension, but in reality it was way too slow to be useful. For founders, operators, and tiny teams doing the work of ten people: This one is for you 💜 What I’d love to know: Which browser task would you use to test Pluno’s limits? P.S. Get 50$ in free credits, today only. Show more

Hi @chatabhishek - it can't bypass CAPTCHAs currently. But it will use your user session, so you can login once and then let Pluno handle the tasks inside. Which use case did you have in mind where you need the CAPTCHA bypass?

@syed_ali319 Seems interesting, will it be able to bypass CAPTCHAs?

Been using it internally a lot for creating dashboards on @PostHog, debugging issues with my queries on @Retool, drafting @LinkedIn comments, and exporting data from @leadfeederapp. What's the most complex task in browser apps you're still doing manually today?

Korbi here - Technical Co-Founder of Pluno. Here's why we've built Pluno, and what browser agents got wrong: Imagine an AI voice agent talking to another voice AI to schedule a barber appointment. Instead of a 3 second interaction of checking which appointments are available and picking one, they'll converse back and forth for 10 minutes. Same is happening for browser agents using the browser. They download the UI, make screenshots to see what's visible, and try to reason about clicking the right button. Instead, they should do what agents do best: Use code, and skip the UI. Pluno learns the API for each tool you use it on, and can talk directly to the API. It's like having a perfectly designed MCP server for every web app you use. Try it on the hardest task you can imagine, and let me know if you find one Pluno can't handle - I'll make sure to hook you up with some extra credits in exchange ;)