HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
browseros-ai
BrowserOS
Rust2025–2026
browseros-ai / BrowserOS

BrowserOS

🌐 The open-source Agentic browser; alternative to ChatGPT Atlas, Perplexity Comet, Dia.

4Distinct people
19Mentions
0Explicit recommenders
14.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🌐 The open-source Agentic browser; alternative to ChatGPT Atlas, Perplexity Comet, Dia.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month19 dated mentions

Observed mentions: 2025-06-20 16:35:55 UTC to 2026-03-16 18:46:20 UTC.

0123452025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJun 20252025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 commentsOct 20252025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC211
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC110
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC413
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC514
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC413
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC211
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC101

What Hacker News says

4 sources
Just dumping the raw DOM into the LLM context is brutal on token usage. We've seen pages that eat up 60-70k tokens when you include the full DOM plus screenshots, which basically maxes out your context window before you even start doing anything useful. We've been working on this exact problem at https://github.com/browseros-ai/BrowserOS. Instead of throwing the entire DOM at the model, we hook into Chromium's rendering engine to extract a cleaner representation of what's actually on the page. Our browser agents work with this cleaned-up data, which makes the whole interaction much more efficient.
In Claude for Chrome
felarof¡Aug 22, 2025Submission

Show HN: BrowserOS -- browser agents with GPT-OSS, local llms

Hi HN – we're the founders of BrowserOS.com (YC S24), and we're building an open-source agentic web browser. We're a fork of Chromium and our goal is to let non-developers create and run useful agents locally on their browser. --- When we launched a month ago, we thought we had the right approach: a "one-shot" agent where you give it a high-level task like "order toothpaste from Amazon," and it would figure out the plan and execute it. But we quickly ran into a problem that we've been struggling with ever since: the user experience was completely hit-or-miss. Sometimes agent worked like magic, but other times the agent would get stuck, generate a wrong plan, or just wander off course. It wasn't reliable enough for anyone to trust it. This forced us to go back to the drawing board and question the UX. We spent the last few weeks experiment
Read the rest
ing with three different ways a user could build an agent: A) Drag-and-drop workflows: Similar to tools like n8n. This approach creates very reliable agents, but we found that the interface felt complex and intimidating for new users. One tester (my wife) said: "This is more work than just doing the task myself." Building a simple workflow took 20+ minutes of configuration. B) The "one-shot" agents: This was our starting point. You give the agent a high-level goal and it does the rest. It feels magical when it works, but it's brittle, and smaller local models really struggle to create good plans on their own. C) Plan-follower agents: A middle ground where a human provides a simple, high-level plan in natural language, and the LLM executes each step. The LLM doesn't have to plan; it just has to follow instructions, like a junior employee. --- After building and trying all three, we've landed on C) as the best trade-off between reliability and ease of use. Here's the demo https://youtu.be/ulTjRMCGJzQ For example, instead of just saying "order toothpaste," the user provides a simple plan: 1. Navigate to Amazon 2. Search for Sensodyne toothpaste 3. Select 1 pack of Sensodyne toothpaste from the results 4. Add the selected toothpaste to the cart 5. Proceed to checkout 6. Verify that there is only one item in the cart. If there is more than one item, alert me 7. Finally place the order With this guidance, our success rate jumped from 30% to ~80%, even with local models. The trade-off: users spend 30 seconds writing a plan instead of just stating a goal. But they get reliability in return. Note that our agent builder gives a good starting plan, and then the user has to just edit/customize it. --- You can try out our agent builder and let us know what you think. We're big proponents of privacy, so we have first-class support for local LLMs. You can try GPT-OSS via Ollama or LMStudio and it works great! I'll be hanging around here most of the day, happy to answer any questions!
12 points ¡ Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.