thepasswordapp

7 ms·

1.
by thepasswordapp 9mo ago
Thanks! We went with a Bauhaus-inspired design - bold geometric shapes, primary colors, hard shadows. Felt like the right aesthetic for a security tool that's meant to feel solid and trustworthy rather than the typical "sleek dark
2.
by thepasswordapp 10mo ago
Good question - and yes, this should probably be a library. The core approach: browser-use's Agent class accepts a `credentials` parameter that gets passed to custom action functions but never included in the LLM prompt. So when the ag
3.
by thepasswordapp 10mo ago
Fair skepticism - I'd be suspicious too. Two clarifications: 1. We don't ask for your current passwords. The app imports your CSV from your existing password manager (1Password, Bitwarden, etc.), which you already trust with your
4.
by thepasswordapp 10mo ago
The credential stuffing angle here is worth highlighting - the breach happened because users reused passwords from other breached sites. What's frustrating is that even security-conscious users face a massive burden after any breach: c
5.
by thepasswordapp 10mo ago
The cat-and-mouse game between AI agents and bot detection is getting more sophisticated every month. What's interesting is that legitimate use cases (accessibility tools, testing automation, research crawlers) get caught in the same n
6.
by thepasswordapp 10mo ago
This is a really important area of research. Building AI agents that interact with external systems (browsers, APIs, CI/CD) requires a fundamentally different security model than traditional software. The attack surface is interesting
7.
by thepasswordapp 10mo ago
The browser automation point is key. We've been using browser-use (the Python library) to automate password changes across websites for thepassword.app - turns out this is a surprisingly hard non-coding automation task. Every site has
8.
by thepasswordapp 10mo ago
Been "vibe coding" for 8 months building thepassword.app - AI browser automation that changes passwords across websites. The enjoyment factor is real. The iteration speed with Claude Code is insane. But the model's suggestion
9.
by thepasswordapp 10mo ago
The car data collection story is concerning, but it's part of a broader pattern: credentials and personal data are scattered across dozens of services we interact with daily. The automotive example shows how even "non-tech" p
10.
by thepasswordapp 10mo ago
We've been using browser-use as the foundation for our macOS app that automates password changes. The framework's LLM loop approach handles dynamic sites much better than traditional selectors - sites change their DOM constantly b
11.
Show HN: AI agent that rotates your passwords (browser-use and zero-knowledge)(thepassword.app)
4 points by thepasswordapp 10mo ago|2 comments
12.
by thepasswordapp 10mo ago
The credential harvesting aspect is what concerns me most for the average developer. If you've ever run `npm install` on an affected package, your environment variables, .npmrc tokens, and potentially other cached credentials may have
13.
by thepasswordapp 10mo ago
This is a good example of "your vendor is your attack surface" becoming the security lesson of 2025. The pattern keeps repeating: Trust vendor → Vendor gets breached → Your users' data exposed. And the cascading effect here i