Viewing profile — pitiflautico
pitiflautico
HN member- Joined
- Fri, Aug 14, 2026, 9:28 AM UTC
- HN karma
- 7
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About pitiflautico
No profile information was provided.
Recent public activity
-
comment
Comment #49376308
[flagged]
-
comment
Comment #49376113
[flagged]
-
comment
Comment #49376025
[flagged]
-
comment
Comment #49351094
Domain allowlist is in: NEOBROWSER_DOMAIN_ALLOWLIST=github.com, .docs.rs — navigate rejects anything not listed with an error that names the allowed hosts. Exact hosts or .suffix, …
-
comment
Comment #49350517
[dead]
-
comment
Comment #49348318
[flagged]
-
comment
Comment #49348292
[dead]
-
comment
Comment #49348151
[dead]
-
comment
Comment #49348005
[dead]
-
comment
Comment #49346505
Fair challenge. The README's claims are the verifiable kind, though: CI installs real Chrome and runs the stealth checks on every push, the bot.sannysoft run is one cargo test away…
-
comment
Comment #49346491
[dead]
-
comment
Comment #49346484
Not quite — the usual browser/computer-use options launch a fresh, cookie-less Chromium, so you hit login walls and bot checks constantly. NeoBrowser drives the real Chrome binary …
-
comment
Comment #49346474
[flagged]
-
comment
Comment #49346461
That's supported as a first-class mode: NEOBROWSER_ATTACH_PORT=9222 attaches to your running Chrome and never patches or kills it. The cookie-import path exists for when you'd rath…
-
comment
Comment #49346453
[dead]
-
comment
Comment #49346445
[dead]
-
comment
Comment #49345367
I built NeoBrowser because every browser MCP I tried had the same failure mode: it launches a fresh, fingerprintable headless browser with no cookies, so the model hits login walls…
- story
-
comment
Comment #49327543
[flagged]
-
comment
Comment #49317742
[flagged]
-
comment
Comment #49308543
[flagged]
-
comment
Comment #49297869
[flagged]