Pluno

Awesome idea excited to try it out and use my own benchmarks. I've found large tasks eat up token limits on Claude relatively quickly

that's really awesome
since this is launched may I know how will you manage the response fast through the API when the users grow

Very cool, Claude has been annoyingly slow on browser tasks, cant wait to fully test pluno!

Wow I'm amazed - this is a legitimately helpful Clippy! Finally something to help me get through the endless nonsense of random burocratic websites to find that one form I need to fill out. Also great for finding a nice holiday spot without having to manually sift through all the options and bookmarking a well curated list. Seems to work like a breeze for quick web deving tasks and checks, too. Overall, very impressive!

Very cool approach to solving computer use, without the huge latency and quality penalty you get from using screenshots and clicking on buttons!

That makes sense for apps where the request-building lives in readable bundle code. Where I'd expect it to get hairy is when the signing isn't static, like a token minted at call-time inside a web worker or a wasm blob, so you can't lift the recipe once and replay it. Do you keep the page's own JS context alive per session to mint each call, or pull the logic out ahead of time?

Skipping the UI and going straight to the API feels like the real shift here - not just a speed improvement, but a completely different way of getting work done.Curious how you handle actions that aren’t easily reversible though. Is there some kind of confirmation or preview layer, or does it just execute once the intent is clear?Either way, this is a really interesting direction - congrats on the launch!

Just installed the chrome extension and I am already a huge fan! Handled an error-case on a website much faster with pluno instead of taking screenshots and uploading them to Claude. Talking directly to the API makes much more sense. Thanks team pluno for the launch and the increase of efficiency you bring with it

The talk-to-the-API-directly bet is the right one for speed, but the wall we keep hitting is that a lot of modern web apps don't expose a callable API in any stable sense. The one I automate safelists its persisted GraphQL queries and 500s anything that isn't on the list, so we're forced back to driving real DOM clicks. How does Pluno handle apps where the underlying calls are signed per-session or the operation set is locked to a safelist?

For browser agents, speed only matters if the failure state is inspectable. The handoff should leave behind what it clicked, what it inferred, where it got stuck, and what still needs human approval; otherwise a fast agent just creates faster uncertainty.

huge fan of the browser plugin. i have a 2nd chrome instance always running where it's doing all my chores. surprised at how good it is!

Is Pluno mainly focused on faster prompting and responses, or does the workflow automation / AI agents side mean it can also take actions across tools?

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 ;)

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?

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.