Launching today
Open Comet
The autonomous AI browser agent for deep research & tasks
96 followers
The autonomous AI browser agent for deep research & tasks
96 followers
Open Comet is a high-fidelity AI agent that lives in your browser’s sidepanel. Unlike basic assistants, it autonomously browses, researches, and executes multi-step workflows across any website. Built on a "Zero-Data" architecture, it keeps your history local while providing enterprise-grade reasoning. Features include high-fidelity execution guards, STORM-inspired research loops, and full support for both Cloud (BYOK) and Local (Ollama) models.
Open Comet
Hi Product Hunt! 👋 I’m Prince, the creator of Open Comet.
Most AI agents today feel 'trapped' behind a chat box, forcing you to copy-paste data back and forth. I built Open Comet to bridge that gap—an agent that actually lives where you work.
My goal was to combine the power of autonomous research with a strict privacy-first architecture. Whether you're a researcher needing deep link exploration or a developer automating repetitive web tasks, Open Comet is designed to stay out of your data and in your flow.
Excited to hear your feedback and answer any questions!
Lovely! Can this browse my logged in pages like linkedin ? And take actions on my behalf. Some UX flows especially linkedin is sub-optimal and this can help save me lot time. Thanks.
Open Comet
@raj_peko Great question, Rajesh 👍
Yes — Open Comet is designed to work on real, logged-in pages (like LinkedIn) and can assist with actions on your behalf.
However, there are a couple of important points:
It can interact with UI elements (clicking, typing, navigating flows) within your active browser session
Since you’re already logged in, it operates within your session context
For sensitive or high-impact actions, it follows a human-in-the-loop approach (asks for confirmation before executing)
So for cases like LinkedIn workflows (posting, navigating profiles, repetitive actions), it can definitely help reduce friction and save time—especially where UX feels sub-optimal.
That said, some flows may vary depending on site restrictions and dynamic UI behavior, but improving reliability across such platforms is an ongoing focus.
Would love to hear your experience once you try it 🙌
Does this work only on Perplexity's Comet browser? Is there an affiliation with them as Open Comet's branding, name and logo is almost 100% on par with Perplexity's - most specifically, their Comet product.
Open Comet
@jacklyn_i Hey Jacklyn, great question—totally fair to ask 👍
No, Open Comet does not work only on Perplexity’s Comet browser, and there’s no affiliation with them.
Tools like Perplexity’s Comet and OpenAI’s Atlas are actually separate AI browsers built from scratch with AI deeply integrated into them. Open Comet takes a different approach—it’s designed to work inside your existing browser (via extension), so there’s no need to switch browsers.
Regarding the naming/branding—yes, it’s inspired by the same emerging category of AI browser agents, but Open Comet is an independent project focused on being more open, flexible, and privacy-first.
Also, one key difference is the approach to data: many AI browsers process and interact with user data at a deeper level to enable automation, whereas Open Comet is designed with a local-first mindset (no data storage/access).
Happy to clarify anything else if you’re curious 🙌
love that you went with local history storage. too many AI tools are black boxes with your data. curious about the STORM research loops - does it actually follow citation trails and cross-reference sources, or is it more like iterative searching?
Open Comet
@piotreksedzik Appreciate that, Piotr 🙌
Great question — the current implementation is closer to iterative research loops rather than a full academic-style citation graph like STORM.
It can:
Perform multi-step searches
Refine queries based on previous results
Aggregate and summarize findings across steps
Cross-referencing does happen to an extent (by comparing results across iterations), but it’s not yet doing deep citation trail tracking or source graph traversal in a strict sense.
That said, moving toward more structured source tracking and citation-aware reasoning is definitely something I’m exploring for future versions.
Would love to hear your thoughts once you try it 👍
Tried a few browser agents before and the scariest moment is always when it hovers over a "Submit Order" button. Does this one ask before doing something irreversible or do you just trust it and hope?
Open Comet
@dklymentiev That’s a very real concern, Dmytro 😄 totally get that “hover over submit” moment.
Open Comet is designed to not blindly execute irreversible actions. It follows a human-in-the-loop approach, where:
It asks for confirmation before any high-impact or irreversible action (like submissions, payments, etc.)
You can see what it’s about to do before it happens
All actions are transparent and trackable, not hidden
So the idea is—you’re always in control, and the agent assists rather than takes risky decisions on its own.
Building that trust layer is a big priority, especially for real-world use cases 👍
@princechouhan06 That's great to hear! Happy to test it!
every autonomous browser agent I've tried hits the same wall eventually - persistent auth sessions and bot detection. curious where this one breaks.
Open Comet
That’s a very real observation, Mykola—completely agree 👍
Persistent auth sessions and bot detection are definitely the hard boundary for most browser agents, and Open Comet isn’t magically bypassing those.
Right now, it works within your existing browser session, so it leverages your active login state rather than trying to handle auth itself. That avoids a lot of friction, but:
It doesn’t try to bypass bot detection systems
Performance can vary on platforms with aggressive anti-automation measures
Some flows may break when sites heavily rely on dynamic tokens or strict interaction patterns
So the current approach is more about assisted interaction within real user context, not full autonomous control across all sites.
Long term, I’m exploring ways to make it more robust around session handling and reliability, but staying within safe and compliant boundaries is important here.
Would be really interested to hear where it breaks for you if you try it—that feedback is gold 🙌
working within your existing session is the smart call - fingerprint spoofing just kicks off an arms race you can’t win
autonomous is doing a lot of work here - the distinction that matters for real adoption is whether it blocks before acting or just does things and logs it.
Open Comet
@mykola_kondratiuk That’s a very fair point, Mykola—completely agree 👍
Right now, Open Comet is designed with a controlled autonomy approach. It doesn’t just execute actions blindly—instead, it pauses for confirmation on sensitive or high-impact actions, while allowing smoother flow for low-risk steps.
So it’s more of a human-in-the-loop system rather than fully autonomous execution. Everything is also transparent and logged, so you can see what it’s doing at each step.
I think this balance is important for real-world adoption—full autonomy without control can break trust pretty quickly.
Would be great to hear your take after you try it 🙌